Re: DHCP in openMosix

Murali P <[email protected]>
Newsgroups gmane.linux.cluster.openmosix.general
Message-ID <[email protected]>
On 26 Jan 2006 15:32:22 +0100, Moreno Baricevic <[email protected]> wrote:
>
> Hi Murali,
>
> we need some more info. Could you tell us something about your
> openmosix.map and your openmosix.config? Are you using omdiscd or a
> static oM map? Do you have one or more NICs on your nodes? Are you sure
> you are running the same oM kernel everywhere? Did you start openmosix?
> Any warning or error message when you start the oM service? Does the
> command "setpe -c -f /etc/openmosix.map" say anything useful?
>
> Ciao
>
> Moreno
>
>
>

On 1/26/06, John Floren <[email protected]> wrote:
>
> Okay, let's try to figure this out.  You say you can ping and ssh the
> hosts, but they are not "recognizing" each other?  By that do you mean
> that openMosix isn't finding any other hosts?  Did you configure an
> openmosix.map file?  Or are you trying to do auto-discovery?
> I never had much luck it auto-discovery, but that was two years ago.  A
> little more information would be helpful to get your problem fixed.
> Thanks
>
> John
>

I had used openmosix-kernel-2.4.26-openmosix1.i686.rpm for installing
openMosix.

I dont have access to one of the machines i had used now. this is the
configuration in the second machine.


[root@vader openmosix-downloads]# cat /etc/openmosix/openmosix.config
#
# This file can be used to change the default behaviour of the
# openMosix startup-script.
#

# Force autodiscovery-daemon to start, even with a valid .map-file
# The following line uncommented by Murali to force autodiscovery
AUTODISC=1

# Specify which network interface the autodiscovery-daemon should listen to
# AUTODISCIF=eth1

# Set the values of /proc/hpc/admin/overheads
# OVERHEADS=

# Set the values of /proc/hpc/admin/mfscosts
# MFSCOSTS=

# Set the openMosix node-id of this node
# MYOMID=

# Set maximum number of gateways between openMosix nodes (see man setpe)
# MOSGATES=

# Pass the following value to mosctl setspeed when starting the node
# man mosctl for details
# NODESPEED=10000

# Processes are allowed to migrate to other nodes.
# MIGRATE=yes

# Allow guest processes to arrive.
# BLOCK=no

# Don't use MFS
# MFS=yes

I hav used the same config file on both machines.

First I had tried the defualt settinmg. Then I forced autodiscovery as well.


[root@vader openmosix-downloads]# cat /etc/openmosix.map
# Static openMosix configuration
# ==============================
#
# Each line in this file should contain 3 fields, statically mapping
# IP addresses to openMosix node-numbers:
#
# 1) The first openMosix node-number in this range.
# 2) The IP address of the above node (or node-name from /etc/hosts).
# 3) The number of nodes in this range.
#
# Note: If you don't create a valid IP <-> node-number mapping, the
#       autodiscovery daemon will be started, automatically assigning
#       node-numbers to all visible openMosix machines.
#
# Example: 10 machines with IP addresses 192.168.1.50 - 192.168.1.59
#          which will have openMosix node-numbers 1-10:
#
# 1        192.168.1.50     10
#
# MOSIX-#  IP  number-of-nodes
# ============================
526    192.168.2.14     1

I had tried giving MOSIX-# as 1 first. then i tried 526 as well. IP of vader
is 192.168.4.144. I have tried commenting the last line as well.
network mask is 255.255.255.0

When i deploy finally, ALL the IP addresses of the machins othr than
192.168.2.14 will be got from DHCP only.

All my machines are having one NIC only.

[root@vader root]# service openmosix restart
openMosix: Using map file /etc/openmosix.map
openMosix: WARN: Invalid configuration in map-file /etc/openmosix.map
openMosix: Falling back to autodiscovery mode using /sbin/omdiscd
Stopping openMosix...
openMosix: All remote processes were expelled and no further remote
processes accepted.
Initializing openMosix...
openMosix configuration was successful :)

[root@vader root]# tail -7  /var/log/messages
...
Feb  1 04:32:31 vader kernel: openMosix: All guest processes evacuated and
no further guests allowed in
Feb  1 04:32:31 vader kernel: openMosix configuration disabled
Feb  1 04:32:31 vader omdiscd[1208]: Exiting on SIGINT.
Feb  1 04:32:31 vader kernel: openMosix: guest-processes now accepted again.
Feb  1 04:32:31 vader kernel: openMosix configuration changed: This is
openMosix #1168 (of 1 configured)
Feb  1 04:32:31 vader kernel: openMosix #1168 is at IP address 192.168.4.144
Feb  1 04:32:31 vader omdiscd[1263]: Notified kernel to activate openMosix

Even when the other machine was connected, the /var/log/messages output was
same only.



--
see not what comes to u.
see what comes out of u.
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.