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

[LDM #UHC-293816]: EOF on socket 1 - what does this mean?

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 #UHC-293816]: EOF on socket 1 - what does this mean?
  • Date: Mon, 20 Apr 2009 15:11:55 -0600
Mike,

> I've tracked it down, but I still don't know if I should ignore the errors.
> There's a cron job that checks ldm's status every 5 minutes, so if the
> status is bad, we can kill it and restart it.  Part of how it checks the
> status is to do an ldmping.  This is what generates the error, but it
> looks like ldmping's working.  Here's the ldmping command and output:
> 
> ldmping -i 0 localhost
> Apr 20 21:00:07 INFO:      State    Elapsed Port   Remote_Host           
> rpc_stat
> Apr 20 21:00:07 INFO: Resolving localhost to 127.0.0.1 took 0.000191 seconds
> Apr 20 21:00:07 INFO: RESPONDING   0.000737  388   localhost

The ldmping(1) program only tries to connect to the LDM server.  If it 
succeeds, then it immediately closes the connection, so the LDM server never 
has a chance to determine what the other process wanted.

Consequently, you may safely ignore these informational messages.

> We run this same cron job on about 20 other servers, running earlier versions
> of ldm, and don't get this behavior.

I added those messages some time ago.  They probably didn't show up until you 
updated the LDM.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UHC-293816
Department: Support LDM
Priority: Normal
Status: Closed