Re: OM on Debian "sarge"

"Bruce Knox" <[email protected]>
Newsgroups gmane.linux.cluster.openmosix.general
Message-ID <[email protected]>
Yartax, Have you tried booting both nodes from identical copies of the ClusterKnoppix CD?  If you have not tried the two CD cluster, then I suggest you try that and see if the nodes communicate as you would expect.  They should.  This would be a good, quick test of your network and the two nodes and give you a needed success in your testing:)

I think some of the problems you have been experiencing setting up your cluster are due to the fact that openMosix must have the same kernel version and config plus using the same tools version on each node.  Matching a compiled node to a ClusterKnoppix CD version can be difficult.  

First, the openMosix version used in the current ClusterKnoppix is not the official openMosix version.  Also, you would need to use the same config that Wim used in compiling ClusterKnoppix.  (BTW, while not the official openMosix version the openMosix version used in the current ClusterKnoppix is very good.  I would not hesitate to use it.)

The current Quantian and the current ClusterKnoppix will automatically match for the most critical parts of the openMosix setup because Dirk and Wim worked together to make sure that the versions were matching.   You can boot a Quantian node from CD/DVD and a ClusterKnoppix node from CD and have them work together automatically in a cluster.  No special setup is required to do this.

While some of openMoxisview will work between the Quantian and ClusterKnoppix nodes, some of the openMosixview functions will not work unless they share the ssh keys.  (I am pretty sure Dirk and Wim did not share keys on the current versions, but I could be wrong.)  Note that the current Quantian version is a DVD because of the size of the applications included.  

If purpose of your compiled node to have a hard drive and additional applications, then consider installing ClusterKnoppix and/or Quantian on your hard drive.  I have not done this, but I would think you would preserve the needed compatibility perfectly.

Another option would be to use either ClusterKnoppix and/or Quantian with CHAOS nodes.  There is a link to the HowTo for this on the http://openmosix.sourceforge.net/instant_openmosix_clusters.html page in the ClusterKnoppix section.

Good Luck! Bruce

>>> Yartax <[email protected]> 11/28/05 04:07PM >>>
I did some avance!

After reinstalling from scratch debian node, mosmon utility seems to not show
node up again. But once installed openmosixview, it show debian node up and
running.

In the other hand, clusterknoppix (live cd) also is up and running. But is not
paired with debian node. Each node sees each other but seems every node
independent. In the debian node, cannot show knoppix node information 
(in red in omview). And the knoppix node cannot show debian node information
too.

I need the last help to connect both nodes and form a unique cluster!.

Greetings.
Yartax.





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click 
_______________________________________________
openMosix-general mailing list
openMosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
https://lists.sourceforge.net/lists/listinfo/openmosix-general



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
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.