Re: two nodes see each other as "down", no job migration

I've seen this a few times in my setup.  My usual solution is to have one of 
the nodes do a openmosix restart. this usually fixes things. Occasionally if 
it doesn't check your dmesg.

Jason coutu

On Sunday 19 February 2006 06:46 am, Michal Szymanski wrote:
> Hello,
>
> I want to setup a cluster of 5-10 machines, using OM. To make some tests
> and gain experience, I started with a mini-cluster at home, on two
> laptops connected via switch acting as a DHCP server, too.
>
> When I boot ClusterKnoppix (ver. 3.6, kernel 2.4.27-om) on both
> machines, the clustering works fine, jobs do migrate, openmosixview
> shows everything perfectly.
>
> As a next step, I tried to install OM stuff (RPMS from OM home pages,
> kernel 2.4.26-openmosix1 - there is no 2.4.27 there, plus OM tools plus
> openmosixview) on one of the laptops which still has Fedora Core 1
> hard-installed. Installation worked fine, the services seem to run (in
> autodiscovery mode - I did not do any changes in the configuration that
> was autoinstalled with the RPMs) The other laptop has FC3 installed, so
> I stayed with LiveCD ClusterKnoppix on it.
>
> Sadly, in this configuration OM does not work. Both machines see the
> other node as "down", see below. Obviously, there is no job migration etc.
>
> Any ideas? Browsing the mailing list archive I have found hints
> suggesting that *all* of the nodes *must* run the very same version of
> the kernel/modules - could that be the reason? Would the OM be that
> self-incompatible?
>
> BTW, it is a pity that "mosctl" does not recognize hex format (as output
> by showmap)
>
> regards, Michal.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBD+IUPQFlY6q2RJnkRAnKaAJoDdmFqZBMal6/dp1eBQIXbOzVpIQCgjWj1
JNiKpxJiEBWyYAm3fsy7EF8=
=le3j
-----END PGP SIGNATURE-----