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

[LDM #VVJ-331218]: LDM 6.11.7 Errors - exit LDM Not starting



Russ,

> Steve,
> 
> I think I see the problem...jsut not sure how to fix it.
> 
> On Geoprod4 where ldm cannot conect to either FOS server, rpcinfo does
> not show port 388, although netstat shows it as listening.
> address@hidden ldm]# rpcinfo -p
> program vers proto   port  service
> 100000    4   tcp    111  portmapper
> 100000    3   tcp    111  portmapper
> 100000    2   tcp    111  portmapper
> 100000    4   udp    111  portmapper
> 100000    3   udp    111  portmapper
> 100000    2   udp    111  portmapper
> address@hidden ldm]# netstat -an |grep 388
> tcp        0      0 0.0.0.0:388 0.0.0.0:*                   LISTEN

While it's good that the LDM server on Geoprod4 is listening on its well-known 
port (388), that's not relevant to a downstream LDM on Geoprod4 not being able 
to connect to the FOS server's LDM.

> On another server whicLDM is working, even though rpcinfo shows it on
> port 59771.  netstat shows it on port 59771, but ps -ef shows port
> 3889.  How do I change that?
> rpc.ldmd -P 388 -q /home/ldm/data/ldm.pq /home/ldm/etc/ldmd.conf

If rpcinfo(1) shows that an LDM server is registered on any port other than 
388, then it's likely that the LDM server program (bin/ldmd) on that host is 
not owned by root, doesn't have the setuid bit turned on, or is on a partition 
for which the operating system doesn't honor the setuid bit for programs owned 
by root. In any case, the situation would need to be corrected.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VVJ-331218
Department: Support LDM
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.