Re: FC3 second node boot hang problem

Jurgen van der Linden <[email protected]>
Newsgroups gmane.linux.cluster.ssic.user
Message-ID <[email protected]>
Jurgen van der Linden <jurgen.vanderlinden <at> quantum.com> writes:

> 
> FC3, rebooted, added a 2-nd node, booted second node using PXE, and
> got on the second node console screen:
> 
>     reop_import_path: no such path: /cluster/node1/dev/console 
> 
> and then a hang.
> 

Well it turns out that the following sequence always fails:
 * turn on node2 (so the MAC addresss of node2 gets into the node1 ARP cache)
 * run ssi_addnode on node1
 * reboot node2 (if PXE boot timed out on node2)
 * node2 will fail, as described above

It can be solved with:
 * turn off node2
 * run ssi-rmnode 2 on node1
 * run ssi-addnode 2 on node1 (MAC address node2 still in arp cache)
 * reboot node1
 * boot node2

So it seems a reboot after the ssi-addnode solves the problem. Awkward, but no
big deal, if you do not add/delete nodes too often.

                     Jurgen.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.