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

20000330: Product trouble Pt II

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: 20000330: Product trouble Pt II
  • Date: Thu, 30 Mar 2000 13:31:32 -0700
>From: Rahe Peter J Civ AFIT/ENP <address@hidden>
>Organization: .
>Keywords: 200003301804.LAA09915

>Continuing my recently developed troubles with my ldm:
>
>I've also started seeing long strings of the following in ldmd.log:
>
>Mar 30 17:52:41 fujita pqact[14130]: child 14682 exited with status 255
>Mar 30 17:52:42 fujita pqact[14130]: child 14684 exited with status 255
>Mar 30 17:52:42 fujita pqact[14130]: child 14686 exited with status 255
>Mar 30 17:52:42 fujita pqact[14130]: child 14688 exited with status 255
>Mar 30 17:52:42 fujita pqact[14130]: child 14690 exited with status 255
>Mar 30 17:52:42 fujita pqact[14130]: child 14692 exited with status 255
>Mar 30 17:52:42 fujita pqact[14130]: child 14694 exited with status 255
>Mar 30 17:52:43 fujita pqact[14130]: child 14696 exited with status 255
>Mar 30 17:52:43 fujita pqact[14130]: child 14698 exited with status 255
>Mar 30 17:52:43 fujita pqact[14130]: child 14700 exited with status 255
>Mar 30 17:52:43 fujita pqact[14130]: child 14702 exited with status 255
>Mar 30 17:52:43 fujita pqact[14130]: child 14704 exited with status 255
>Mar 30 17:52:44 fujita pqact[14130]: child 14706 exited with status 255
>
>How do I find what processes are at fault?
>Pete Rahe
>Weather Lab Unix System Administrator
>Air Force Institute of Technology
>Wright-Patterson AFB OH
>
>??address@hidden       
> ?  (DSN 785-3636 x4646  COMM (937) 255-3636 x4646
>       Fax:  DSN 785-2921    COMM (937) 255-2921
>
> 
>


Pete,

You can issua a "kill -USR2" to the pqact process id (eg 14130 in the above)
to cycle the log output to verbose, then a second "kill -USR2" to go into 
debug mode. With the log output in copious detail, you can see what product
and action are resulting in a non-zero exit status.

If this is a decoder, then you might find further log information in the
decoder specific log with the "child process" number.

Once you find the error message, issue another "kill -USR2" to pqact to
cycle it back to quite mode.

Steve Chiswell