This looks like the problem -- LAM does not understand IPv6, so it does
not see any localhost entry (because your localhost appears to be IPv6
only).
Two solutions to this:
1. Add an IPv4 address to your localhost entry.
2. Use a non-default hostfile that explicitly lists your IPv4 hostname
/ IP address instead of localhost.
Hope that helps.
On Dec 9, 2004, at 8:01 AM, Marc Vogt wrote:
> Here is the ifconfig output where valid nonlocal IP address, inet6 addr
> and Hwaddr are X'd out by hand.
>
> thanks,
> Marc
>
> eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
> inet addr:XX.XX.XXX.XX Bcast:255.255.255.255
> Mask:255.255.252.0
> inet6 addr: XXXX::XXX:XXXX:XXXX:XXXX/XX Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2201209 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1434776 errors:0 dropped:0 overruns:0 carrier:0
> collisions:222497 txqueuelen:1000
> RX bytes:1094066784 (1.0 GiB) TX bytes:249718642 (238.1 MiB)
>
> lo Link encap:Local Loopback
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:7884 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7884 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:5074792 (4.8 MiB) TX bytes:5074792 (4.8 MiB)
>
> sit0 Link encap:IPv6-in-IPv4
> inet6 addr: ::127.0.0.1/96 Scope:Unknown
> UP RUNNING NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:5766 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
>
>
>>
>> What is happening here is that LAM has somehow determined that
>> "localhost" does not resolve to an IP address that is available on
>> your
>> machine.
>>
>> What is the output of running "ifconfig"?
>>
>>
>> On Dec 9, 2004, at 2:13 AM, Marc Vogt wrote:
>>
>>> Hello
>>>
>>> I am having problems with lamboot and wondered if anyone could help.
>>>
>>> [mtv_at_tamarind ~]$ recon
>>> ---------------------------------------------------------------------
>>> --
>>> ------
>>> The boot SSI rsh module found that your local host is not in the
>>> hostfile "/usr/local/etc/lam-bhost.def".
>>>
>>> The local host name *must* be in the list of hosts in the hostfile.
>>> In other words, you must boot LAM from a node that will be part of
>>> the
>>> universe.
>>>
>>> - If you simply forgot to put the local host in the boot
>>> schema file, add it and re-run The boot SSI rsh module
>>> - If you are trying to boot LAM from a node that will not be
>>> part of the universe, you must login to on of the nodes
>>> that
>>> will be part of the universe (i.e., one of the nodes in the
>>> hostfiles), and re-run The boot SSI rsh module
>>>
>>> Although the local host name is usually the first in the list to
>>> avoid
>>> I/O ambiguities, it can actually appear anywhere in the list.
>>> ---------------------------------------------------------------------
>>> --
>>> ------
>>>
>>> Same message occurs for regular lamboot.
>>>
>>> /usr/local/etc/lam-bhost.def does include localhost
>>>
>>> My version is lam-7.1.1 compiled from source but I tried from
>>> lam-7.1.1-2.i586.rpm and lam-6.5.4-usysv.1.i386.rpm
>>> cleaning up properly in between and got the same message.
>>>
>>> I am trying to set this up on a dual processor machine
>>> running FC3 with 2.6.9-1.667smp kernel that is using dhcp
>>> to obtain host address.
>>>
>>> /etc/hosts has only:
>>>
>>> 127.0.0.1 tamarind localhost.localdomain localhost
>>>
>>>
>>>
>>>
>>> thanks for any help!
>>>
>>> Marc
>>>
>>>
>>>
>>> _______________________________________________
>>> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>>>
>>
>> --
>> {+} Jeff Squyres
>> {+} jsquyres_at_[hidden]
>> {+} http://www.lam-mpi.org/
>>
>> _______________________________________________
>> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
