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

RE: 20030127: pqact hangup

OK.  My ldm is now writing surface data and upper air data to files using
the stdiofile command.  When I try to do a pqactHUP I still get a hang up
but if I start and stop ldm it takes the changes to the pqact.conf file.
However, when I try to write to my gempak decoders I get a problem.

Here are the applicable lines form pqact.conf:

#
WMO     ^S[AP].* .... ([0-3][0-9])([0-2][0-9])
        STDIOFILE       data/surface/(\1:yyyy)(\1:mm)\1\2_sao.mwo
#
WMO     ^U..... .... (..)(..)
        STDIOFILE       data/upperair/(\1:yyyy)(\1:mm)\1\2_upa.wmo
#
#
#GEMPAK
###
#
# US and Canadian sfc obs and specials
#
WMO     ^S[AP].* .... ([0-3][0-9])([0-2][0-9])
        PIPE    decoders/dcmetr -v 2 -a 500 -m 72 -s sfmetar_sa.tbl
        -d data/gempak/logs/dcmetr.log
        -e GEMTBL=/Nawips/gempak5.6/gempak/tables/stns/
        data/gempak/surface/YYYYMMDD_sao.gem

Here are the messages form the ldmd.log file:

Jan 27 19:35:31 sml0 pqact[6477]: pbuf_flush (5) write: Broken pipe
Jan 27 19:35:31 sml0 pqact[6477]: pipe_dbufput:
decoders/dcmetr-v2-a500-m72-ssfmetar_sa.tbl-ddata/gempak/l
ogs/dcmetr.log-eGEMTBL=/N
Jan 27 19:35:31 sml0 pqact[6477]: pipe_prodput: trying again
Jan 27 19:35:31 sml0 pqact[6477]: pbuf_flush (5) write: Broken pipe
Jan 27 19:35:31 sml0 pqact[6477]: pipe_dbufput:
decoders/dcmetr-v2-a500-m72-ssfmetar_sa.tbl-ddata/gempak/l
ogs/dcmetr.log-eGEMTBL=/N
Jan 27 19:35:31 sml0 pqact[6477]: child 6526 terminated by signal 9

Here is my directory structure for Gempak:

/Nawips/gempak5.6/gempak/tables/.   sfmetar_sa.tbl is in
/Nawips/gempak5.6/gempak/tables/stns/  (I have tried using both
/Nawips/gempak5.6/gempak/tables/ and /Nawips/gempak5.6/gempak/tables/stns/
in the pipe command line but I get the same answer..

I copied dcmetr into the /usr/local/ldm/decoders directory.

Any idea as to what I am doing wrong?

Jim


*************************************************
*  Dr.  James C. St. John
*  School of Earth and Atmospheric Sciences
*  Georgia Institute of Technology
*  1254 Ford Motor Co. ES&T Building
*  Atlanta GA 30332-0340
*  Phone:    404-894-1754
*  Fax:        404-894-5638
*  E-Mail:   address@hidden

-----Original Message-----
From: Tom Yoksas [mailto:address@hidden]
Sent: Monday, January 27, 2003 1:26 PM
To: Jim St. John
Cc: address@hidden
Subject: 20030127: pqact hangup

>From:  "Jim St. John" <address@hidden>
>Organization:  Georgia Tech
>Keywords:  200301271700.h0RH0U602736 LDM pqact ldmadmin

Jim,

>Thanks to all who helped me last week.  I've now got data coming in but I
>can't get it to write to files.  When I use ldmadmin pqactHUP I get a
>"hangup" error and nothing is being written to the log file. I researched
>the archives at Unidata and found that lack of tabs in the files in /etc
>(e.g. services, rps, etc.) will cause this problem, but I double-checked
>mine and they are all right.   Has anyone else had a problem like this?

Before sending a HUP signal to pqact, you should _always_ run
'ldmadmin pqactcheck'.  This performs a sanity check on your pqact.conf
file and spots most syntax problems.

You can independently test if you setup /etc/syslog.conf correctly by
using the 'logger' application.  Here is a simple 'logger' invocation,
run as 'ldm', that will test to see if syslogd is setup to log to your
LDM log file:

% logger -p local0.debug "Test of syslogd output to LDM log file"

If you do not get the test message written to your ~ldm/logs/ldmd.log
file, then you either have not setup /etc/syslog.conf correctly;
you did not send a HUP to syslogd after setting up /etc/syslog.conf;
or syslogd is hung and needs to be stopped and restarted by 'root'.

Tom
--
+---------------------------------------------------------------------------
--+
* Tom Yoksas                                             UCAR Unidata
Program *
* (303) 497-8642 (last resort)                                  P.O. Box
3000 *
* address@hidden                                   Boulder, CO
80307 *
* Unidata WWW Service
http://www.unidata.ucar.edu/*
+---------------------------------------------------------------------------
--+