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

[LDM #LXP-916564]: ldmping

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: [LDM #LXP-916564]: ldmping
  • Date: Tue, 14 Apr 2009 16:35:50 -0600
Michael,

> Could this be a portmap issue?  I changed the port in ldmadmin-pl.conf to 
> 1388 and did the same on another server.  I could then ldmping the ldm server 
> with no trouble.  Of course the ldm server wasn't receiving any data because 
> nothing else was talking to 1388 so I couldn't rule out too much data for the 
> system to handle as being the problem.  When I changed the port back to 388 
> however, I used a stripped-down ldmd.conf file that had no processes listed 
> in it.  I still had a problem ldmping'ing ldm-11 on 388.  It seems that 388 
> is getting too busy to handle all of the requests.  I wonder if there are a 
> number of ldmd.conf files with too many data requests which ends up flooding 
> port 388?

It shouldn't be a portmapper problem.

Try putting the LDM server into verbose logging mode by sending
it a SIGHUP (e.g., kill -HUP `cat ldmd.pid`).  Then try ldmping(1)ing
it.  The server should log all connection attempts.  To put the server
back into normal logging mode, send it *two* more SIGHUP-s.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: LXP-916564
Department: Support LDM
Priority: Normal
Status: Closed