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

20050606: Wondering what a SIGCHLD failure is...

Gerry,

> To: Unidata Support <address@hidden>
> From: Gerry Creager N5JXS <address@hidden>
> Subject: Wondering what a SIGCHLD failure is...
> Organization: Texas A&M University -- AATLT
> Keywords: 200506061607.j56G7fZu011988 LDM rpc.ldmd SIGCHLD

The above message contained the following:

> If there's time, could you shed some light on this log and all the 
> errors?  I'm getting the ldmd.conf from Matt soon, I hope; that may 
> answer the question...
> 
> Thanks, Gerry
[snip]

> Jun 06 07:28:11 ldm sura-vims-pe6600-1(feed)[14966]: up6.c:339: Starting 
> Up(6.1.0/6): 20050606062810.250 TS_ENDT {{EXP,  
> "^UAH-NAMAW12-([0-9][0-9][0-1][0-9][0-3][0-9][0-2][0-9])-([0-9][0-9][0-1][0-9][0-3][0-9][0-2][0-9])-ZUNCspec1"}}
>  
> Jun 06 07:28:11 ldm sura-vims-pe6600-1(feed)[14966]: topo:  
> sura-vims-pe6600-1.vims.edu EXP 
> Jun 06 07:28:12 ldm pqact[29831]:  5125938 20050606072810.511     EXP 000  
> UAH-NAMAW12-05060606-05060609-ZUNCspec1 
> Jun 06 07:28:12 ldm pqact[29831]:                exec: /bin/true 
> Jun 06 07:28:12 ldm rpc.ldmd[29828]: RPC buffer sizes for dante2.renci.org: 
> send=16384; recv=87380 
> Jun 06 07:28:12 ldm dante2[14969]: Connection from dante2.renci.org 
> Jun 06 07:28:12 ldm dante2[14969]: Exiting 
> Jun 06 07:28:12 ldm rpc.ldmd[29828]: SIGCHLD 
> Jun 06 07:28:12 ldm rpc.ldmd[29828]: child 14969 exited with status 0 

I deduce the following from the above regarding the SIGCHLD:

    1.  Verbose logging was enabled.

    2.  An LDM process on host dante2.renci.org connected to the
        top-level LDM server on host Ldm and caused a child LDM process
        to execute.

    3.  Within the same second, the child LDM process on host Ldm 
        terminated successfully.

The above is consistent with the LDM process on host dante2.renci.org
inquiring as to whether or not it's upstream (feeding) LDM process on
host Ldm was still alive (via an IS_ALIVE message).

The SIGCHLD log message doesn't indicate a failure.  It indicates 
notification of the top-level LDM server on host Ldm that the
child LDM process has terminated with a successful exit status.

You might consider lowering the logging level from verbose to default.

Are there any other questions about the logfile?

Regards,
Steve Emmerson