[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20030515: LDM-6.0.11 won't run under RedHat 8.0 Linux

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20030515: LDM-6.0.11 won't run under RedHat 8.0 Linux
  • Date: Thu, 15 May 2003 07:55:08 -0600
>From: "Mike Dross" <address@hidden>
>Organization: Wright Weather
>Keywords: 200305150534.h4F5YtLd004038 LDM-6.0.11

Hi Mike,

>I have installed Red Hat 8 on a new computer and tried to install the latest
>LDM 6.11 I belive. Everthing goes ok until I try and start the ldm, the log
>file says:
>
>May 15 05:04:36 wxserver3 rpc.ldmd[5760]: Starting Up (version: 6.0.11;
>built: May 15 2003 04:53:06)
>May 15 05:04:36 wxserver3 rpc.ldmd[5760]: Version 6 LDM already running on
>local host
>May 15 05:04:36 wxserver3 rpc.ldmd[5760]: Version 5 LDM already running on
>local host
>May 15 05:04:36 wxserver3 rpc.ldmd[5760]: Terminating process group
>
>Then stops.  Is there something I have done wrong?

LDM-6.0.11 is almost identical to LDM-6.0.10 (a one line change related
to tenacity with which an rpc.ldmd will try to connect to a host that
doesn't respond), and LDM-6.0.10 has been running on Gilbert's RedHat
8.0 machine for quite some time.

Is it possible that you did not stop the previously running LDM:

ldmadmin stop

The error you are seeing is coming from there already being a program
registered with program number 300029 for port 388.  To see if this
may be the case, run:

rpcinfo -p

If you see entries like:

    300029    6   tcp    388  ldmd
    300029    5   tcp    388  ldmd

Then a previous LDM invocation has not released needed resources.
If this is the case, you will need to use rpcinfo to free up
the resource:

rpcinfo -d 300029 6
rpcinfo -d 300029 5

If there was no LDM running previously, I would guess that there is
some subtle file permission problem.

>Michael Dross
>Wright-Weather, LLC
>address@hidden
>704-947-9369

Tom