Re: [ldm-users] LDM not binding client source address?

  • To: Kyle Schaffrick <kyle@xxxxxxxx>
  • Subject: Re: [ldm-users] LDM not binding client source address?
  • From: Gerry Creager <gerry.creager@xxxxxxxx>
  • Date: Fri, 29 Aug 2008 19:03:15 -0500
Following up on Steve's comments, and your later ones, let's hit an obvious question: Did you leave SELinux enabled or set it to either off or permissive? If it's still there in all its glory, it can be doing some interesting and problemmatical things to you.

We run a number of machines with CentOS 4 and 5 with no problems here.


Kyle Schaffrick wrote:

I'm attempting to set up an LDM instance for the first time and have run
into some issues. The machine is CentOS Linux; I'm using LDM 6.6.5.

When I start the LDM daemon, it fails to receive any products (according
to 'ldmadmin watch'), and logs messages of the form (host names redacted
at operators' request):

  Aug 29 04:20:51 ldm-server[28268] NOTE: LDM-6 desired
    product-class: 20080829032051.817 TS_ENDT {{WMO, ".*"}}
  Aug 29 04:20:51 ldm-server[28268] ERROR: Disconnecting
    due to LDM failure; nullproc_6 failure to; RPC:
    Unable to receive; errno = Connection reset by peer

at "pseudo-random" intervals, about 1 or 2 per second. 'ldmping' also
reports "Connection reset by peer".

The machine I'm running it on has a number of IP addresses set up on its
interface, and according to the upstream provider, their server is
rejecting our requests because the connections are coming from one of
the other IPs on the interface, i.e., not the one they ALLOWed.

I've set $ip_addr to the correct address in ldmadmin-pl.conf, LDM emits
a log message during startup that it is listening on that address, and
'netstat -l' also corroborates this. However, all signs seem to point to
the client code somehow failing to bind it's *outgoing* socket to that

I'm not sure where to go from here as far as troubleshooting this. It
bears mentioning that I'm also getting an error message during startup
regarding a nonexistent file /etc/killall (which past traffic on this
list indicated was a problem with the configure script), but this
in itself doesn't seem to be causing any immediate problems.

Any pointers on investigating this would be greatly appreciated.

ldm-users mailing list
For list information or to unsubscribe, visit:

Gerry Creager -- gerry.creager@xxxxxxxx
Texas Mesonet -- AATLT, Texas A&M University        
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983
Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843

  • 2008 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: