Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Walker, Bruce J <bruce.walker@hp...> - 2004-04-27 15:16:12
On node 2, type cluster -V and see what state it thinks node 1 is in.
One semantic in OpenSSI is that you can't rejoin until you have been
completely "cleaned up" after having gone down. There may be a problem
in the cleanup (something stuck), which is preventing the rejoing. The
output from cluster -V would be revealing if it said the state was
KCLEANUP (Kernel cleanup) or UCLEANUP (user mode cleanup). If it is
DOWN, then the cleanup went ok but there is some other problem
P.s. You might also want to try the cluster -V after node 1 goes down
and before you try to rejoin it.
> -----Original Message-----
> From: ssic-linux-devel-admin@...=20
> [mailto:ssic-linux-devel-admin@...] On=20
> Behalf Of Andreas
> Sent: Tuesday, April 27, 2004 7:27 AM
> To: ssic-linux-devel@...
> Subject: [SSI-devel] Problem with rejoining the cluster
> In my configuration I have two node (potentiell initnodes)=20
> Node 1 is the=20
> initnode. node 2 comes up. After that node 1 is powered off=20
> and node 1=20
> mounts the root fs and takes over the vip. Everything works fine. But=20
> after that I restart node 1 and it is not able to rejoin the=20
> cluster. At=20
> boottime it says
> Found node 2 as the root node.
> Waiting to join the cluster...
> Do anybody have an idea what the problem is? Maybe a service=20
> that isn't=20
> restarted an node 2 after the failover?
> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
> For a limited time only, get FREE Ground shipping on all orders of $35
> or more. Hurry up and shop folks, this offer expires April 30th!
> ssic-linux-devel mailing list