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

20010123: 19991201: Download information

>From: "Glenn Rutledge" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200101231808.f0NI8ee16900

>Can someone determine what this error might be?  Thx, Glenn
>
>mpak/tables/pack/metar.pack-s/npfos/noaaport/nawips/gempak/tables/stns/sfmetar
> _sa.tbl/npfos/noaaport/nawipsdata/surface/YYYYMMDD_sao.gem
>write error
>Dec 13 16:08:19 pqact[303]: pipe_prodput: trying again
>Dec 13 16:08:19 pqact[303]: child 11101 terminated by signal 9
>Dec 13 16:08:19 pqact[303]: pbuf_flush (5) write: Broken pipe
>Dec 13 16:08:19 pqact[303]: pipe_dbufput:
>/npfos/noaaport/nawips/bin/sol/dcmetr-v1-b9-m24-d/npraid/noaaport/nawips/logs/
> 20001213_dcmetr.log-p/npfos/noaaport/nawips/ge
>
>mpak/tables/pack/metar.pack-s/npfos/noaaport/nawips/gempak/tables/stns/sfmetar
> _sa.tbl/npfos/noaaport/nawipsdata/surface/YYYYMMDD_sao.gem
>write error
>Dec 13 16:08:19 pqact[303]: pipe_prodput: trying again
>Dec 13 16:08:19 pqact[303]: child 11102 terminated by signal 9
>
>

Glenn,

Make sure that the output data directory exists and is writable by the
LDM process owner:
/npfos/noaaport/nawipsdata/surface/

Also, if you have a file in that directory for today, make sure that the
ownership and permissions of the file are that of the ldm pqact process
(sometimes, if the LDM is mistakenly run as root...and then later as 
a different user...such as ~ldm, then file ownership gets clobbered).
Its common for system administrators to accidentally start the ldm as
themselves and not as the ldm user from time to time.

Since this log message above is for DEC 13, 2000....is it still occurring?

Steve Chiswell