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

Re: 20000509: LDM dumping core (fwd)

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: Re: 20000509: LDM dumping core (fwd)
  • Date: Thu, 18 May 2000 14:32:41 -0600
"Jason J. Levit" wrote:

> > Try these and see if you can fix the 'child exited with status 127" 
> > problem, then see if the other problems
> > go away.  We're here if you still have problems.  Good luck.
>
>   Hi Anne,
>
>   I attempted to figure out the problem with our LDM system today, using
> the suggestions in your last e-mail; basically, I tried to put "pqact"
> into verbose and debug mode.  Unfortunately, doing that didn't offer up
> any new information in the log file.  I'm not sure why I'm seeing so
> many processes receive a "127" problem, and I'm hoping there is
> something else I can do to further diagnose the problem?  Do you have
> any further suggestions?  Thanks for any help!
>
>   Jason
>
> --
> ----------------------------------------------------------------------------
> Jason J. Levit, N9MLA                         Research Scientist,
> address@hidden                   Center for Analysis and Prediction of
> Storms
> Room 1014                                   University of Oklahoma
> 405/325-3503                               http://www.caps.ou.edu/

Hi Jason,

We know the problem stems from something pqact is trying to do based on an 
entry in your pqact.conf file.  I
suggest trying to isolate the problem further.

First, log in as 'ldm'.  (This should put you in ~ldm.)  Start up the ldm from 
the command line:
    rpc.ldmd -vxl - -q data/ldm.pq etc/ldmd.conf

This will cause output messages to be displayed to your screen.  Presumably 
you'll get the same results.  After
that, start commenting out lines in your pqact.conf file until you can find the 
entry that's causing the crash.
Were any changes made to pqact.conf recently?  Those would be the first to 
suspect.

Let me know how this turns out.

Anne
--
***************************************************
Anne Wilson                     UCAR Unidata Program
address@hidden                  P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************