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

Re: 20000406: LDM 5.0.9 (fwd)

> >To: address@hidden
> >From: Eirh-Yu Hsie <address@hidden>
> >Subject: LDM 5.0.9
> >Organization: .
> >Keywords: 200004061755.LAA16243
>
> Hello:
>
> After install LDM 5.0.9 in a SUN Ultra1 (OS 7), I keep getting:
>
> Apr 06 17:41:05 stratus rpc.ldmd[280]: Starting Up (built: Apr  6 2000 
> 10:11:23)
> Apr 06 17:41:06 stratus cirrus[285]: run_requester: Starting Up: 
> cirrus.al.noaa.
> gov
> Apr 06 17:41:06 stratus cirrus[285]: run_requester: 20000406173734.397 
> TS_ENDT {
> {FSL2|UNIDATA,  ".*"}}
> Apr 06 17:41:06 stratus cirrus[285]: FEEDME(cirrus.al.noaa.gov): OK
> Apr 06 17:41:07 stratus pqexpire[282]: Starting Up
> Apr 06 17:41:07 stratus pqbinstats[283]: Starting Up (280)
> Apr 06 17:41:07 stratus pqact[284]: Starting Up
> Apr 06 17:41:08 stratus localhost[301]: Connection from localhost
> Apr 06 17:41:08 stratus localhost[301]: Connection reset by peer
> Apr 06 17:41:08 stratus localhost[301]: Exiting
> Apr 06 17:41:12 stratus pqact[284]: pbuf_flush 4: time elapsed   3.959643
> Apr 06 17:41:16 stratus pqact[284]: child 353 exited with status 2
> Apr 06 17:41:20 stratus pqact[284]: child 360 exited with status 2
> Apr 06 17:41:23 stratus pqact[284]: child 368 exited with status 2
> Apr 06 17:41:28 stratus pqact[284]: child 378 exited with status 2
> Apr 06 17:41:30 stratus pqact[284]: child 401 exited with status 2
> Apr 06 17:41:35 stratus pqact[284]: child 419 exited with status 2
> Apr 06 17:41:42 stratus pqact[284]: child 435 exited with status 2
> Apr 06 17:41:54 stratus pqact[284]: child 473 exited with status 2
> Apr 06 17:42:05 stratus pqact[284]: child 476 exited with status 2
> Apr 06 17:42:08 stratus pqact[284]: child 489 exited with status 2
> Apr 06 17:42:09 stratus pqact[284]: child 492 exited with status 2
> Apr 06 17:42:10 stratus pqact[284]: child 493 exited with status 2
> ...
> ...
>
> The pqact.conf seems fine.
>
> Hsie
>

Hi Hsie,

The most likely reason for a child of pqact exiting with a problem is that one 
of
the decoders is having trouble.

To start debugging this, first log in as user 'ldm' and change to the 'ldm' home
directory so that you have the same environment as the ldm.

Decoder problems often involve conflicts with permissions or ownerships.  For
example, maybe the decoder doesn't have write permission to the required
directory.  Check to see that your directories and files are owned by 'ldm'.
Directories should probably be owner and group writable, so check that as well.

If you don't find anything from this check, then you might try to determine 
which
decoder is having a problem.  You could go about this by simply executing the
commands from the command line that pqact would execute.  That is, take each
command from pqact.conf and try running it yourself on the command line.
Alternatively, you could keep commenting out lines in your pqact.conf file and
rerunning the ldm until you find the line generating the problem.

Anne


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