[LDM #UHO-873587]: Possible bug with 6.13.7 (and previous)

Mike,

> I already have a couple of questions.  First, what does this error mean?
> I'm seeing these on my downstream sever (v6.13.6), and they seem fairly
> common:
> 
> pqact[66069] ERROR filel.c:3032:reap() Child 39808 exited with status 255
> The Child number will vary, but the rest is always the same.

That message means that pqact(1) noticed that a child process that it create 
exited with a non-zero status. I believe 255 means that the child program 
couldn't be found. There should be other messages nearby that indicate what the 
child program was.

> Similarly, what does "ldmd.c:cleanup() NOTE  Exiting" mean?  I'm seeing
> this on my upstream server (v6.13.7) associated with a few different
> IPs/hostnames, also pretty common.  A couple of those IPs are also mine,
> and I've already made sure to limit redundant requests to no more than two
> on both of those.

That message means that the upstream LDM process was terminating. An upstream 
LDM process will terminate if its connection to its associated downstream LDM 
process is broken -- such as when the downstream LDM process decides to switch 
transfer modes (the downstream LDM must, necessarily, disconnect and reconnect 
to do this).

> And yes, I do plan on updating everything to v6.13.8 soon, just figured I'd
> start with some initial adjustments to my requests lines first.

Wait for 6.13.9, which has the ldmping(1) bug fixed.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UHO-873587
Department: Support LDM
Priority: High
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.