20030515: LDM-6.0.11 won't run under RedHat 8.0 Linux (cont.)

>From: "Mike Dross" <address@hidden>
>Organization: Wright Weather
>Keywords: 200305150534.h4F5YtLd004038 LDM-6.0.11

Hi Mike,

>Thanks for your response. Here is what I am seeing.
>
>[root@wxserver3 root]# rpcinfo -p
>   program vers proto   port
>    100000    2   tcp    111  portmapper
>    100000    2   udp    111  portmapper
>    100024    1   udp  32768  status
>    100024    1   tcp  32768  status
>    391002    2   tcp  32769  sgi_fam
>    100011    1   udp    941  rquotad
>    100011    2   udp    941  rquotad
>    100011    1   tcp    944  rquotad
>    100011    2   tcp    944  rquotad
>    100003    2   udp   2049  nfs
>    100003    3   udp   2049  nfs
>    100021    1   udp  32770  nlockmgr
>    100021    3   udp  32770  nlockmgr
>    100021    4   udp  32770  nlockmgr
>    100005    1   udp  32771  mountd
>    100005    1   tcp  32770  mountd
>    100005    2   udp  32771  mountd
>    100005    2   tcp  32770  mountd
>    100005    3   udp  32771  mountd
>    100005    3   tcp  32770  mountd
>[root@wxserver3 root]#

OK, so there is no previous LDM invocation registered with the portmapper
on your machine.

>No conflict there. I actually rebooted the computer to make sure there were
>no errant programs running that would be interfering with the LDM but still
>no luck.

OK.

>Any ideas????

See below.

>I tried installing the LDM 5.2.2.tar, but it would not make, it gave
>me errors.
>
>Should I try ldm-6.0.10??

No, there is no difference between 6.0.10 and 6.0.11 that could cause
what you are seeing.

Here is what the LDM does on startup:

- does a gethostname call

- tries to connect to an LDM running on the machine name returned
  in the gethostname call

- if the LDM _can_ connect to an LDM running on the name returned
  by the gethostname call, it spits back the error that you are
  reporting:

  Version 6 LDM already running on local host

  and then

  Version 5 LDM already running on local host

What this implies is either:

- there is an LDM running already on your machine

- the name returned by gethostname is that of a different machine that
  is running an LDM

Since you say that this is a new machine, I would guess that you copied
over some configuration files from an existing host -- that is running
an LDM.  One of the files you may have copied is /etc/hosts.  If
this file does not have the entry:

127.0.0.1       localhost loopback

you could be in big trouble.  However, in the setup for Linux, you
would have had to say what this machine's name is.  This value would be
set so that it would be returned by the 'hostname' command, which, by
the way, just returns the value returned by gethostname.  Here is a
snippit from the man page for hostname on RedHat Linux:

HOSTNAME(1)                                                 Linux Programmer's 
Manual                                                HOSTNAME(1)

NAME
       hostname - show or set the system's host name
 ...

SYNOPSIS
       hostname [-v] [-a] [--alias] [-d] [--domain] [-f] [--fqdn] [-i] 
[--ip-address] [--long] [-s] [--short] [-y] [--yp] [--nis] [-n] [--node]
 ...

       hostname will print the name of the system as returned by the 
gethostname(2) function.


So, what is the value returned back when you run 'hostname' from the 'ldm'
login to your new machine?  If it is the name of a different machine, and
if that different machine is running an LDM, then your problem is that
the hostname of this new machine has been set incorrectly.

If 'hostname' returns the correct hostname for this system and there
is no LDM running, then you have a big mystery that we could only
help solve by logging onto your machine.

>Thanks for your help, it's much appreciated!

We are very curious about what is going on your machine!

Tom