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

Re: 20050525: "Broken pipe" error message

Aha!  The file

/home/ldm/gempak-5.6/gempak/tables/pack/msfc.pack
was missing. That 'pack' directory was entirely empty. So I copied over the 'pack' files from another machine we have, and I'll see what happens. 

Carl

Unidata Support wrote:


Carl,

Your dcmsfc.log file shows a problem reading your $GEMTBL/pack/msfc.pack
file. In your pqact.conf file, you are setting GEMTBL to be
/home/ldm/gempak-5.6/gempak/tables.

Is the /home/ldm/gempak-5.6/gempak/tables/msfc.pack file readable by the ldm 
user
(asking here since if it was installed by a different user with umask not 
allowing
the ldm user, that would be a problem). If readable, double check to make sure
it wasn't modified.

Steve Chiswell
Unidata User Support







From: Carl Drews <address@hidden>
Organization: UCAR/Unidata
Keywords: 200505252131.j4PLVmP3025354



This is a multi-part message in MIME format.
--------------090503020506000101070807
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Steve -
Thanks for the information. When logged in as 'ldm' I can make little test files in those two directories. 


Is your expected GEMPAK data directory ~ldm/data/ldm/gempak?<

Close.  It's actually ~/data/ldm/gempak

Here is my environment:

mds-ingest1:ldm> whoami
ldm
mds-ingest1:ldm> env
USER=ldm
LOGNAME=ldm
HOME=/home/ldm
PATH=.:/bin:/usr/bin:/usr/ucb:/local/bin:/usr/X11R6/bin:/home/4dwx/bin:/home/l
dm/bin:/home/ldm/sh:/home/ldm/runtime/bin:/home/ldm/decoders:/home/ldm/exe
MAIL=/var/mail/ldm
SHELL=/bin/csh
SSH_CLIENT=128.117.194.68 37016 22
SSH_TTY=/dev/pts/0
TERM=xterm
HOSTTYPE=i386-linux
VENDOR=intel
OSTYPE=linux
MACHTYPE=i386
SHLVL=1
PWD=/home/4dwx/logs
GROUP=ldm
HOST=mds-ingest1
REMOTEHOST=simon.rap.ucar.edu
LDMHOME=/home/ldm
mds-ingest1:ldm>

I have attached the dcmsfc.log file.

Carl



Carl,

The pqact.log  file you provided shows several sets of errors.
Besides the dcmsfc errors, you have numerous other perl decoders with
permission denied. This seems to say that the LDM user running
pqact can not write to $LDMHOME/data/ldm/gempak/ship and/or $LDMHOME/data/ldm

/gempak/logs.

If you do have data/ldm/gempak/logs/dcmsfc.log, then that file might give
some additional clues since you say that the logs directory is writable.

Is your expected GEMPAK data directory ~ldm/data/ldm/gempak?
Your pqact.conf patterns are relative to the LDMHOME directory
and that is the location you are using.

Steve Chiswell
Unidata User Support







From: Carl Drews <address@hidden>
Organization: UCAR/Unidata
Keywords: 200505252040.j4PKeAP3017567




This is a multi-part message in MIME format.
--------------000804000206040007040500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Unidata -
Can you help me figure out what this "Broken pipe" error means in the pqact.log file? 

^@May 25 20:15:12 pqact[15507]: pbuf_flush (8) write: Broken pipe
^@May 25 20:15:12 pqact[15507]: pipe_dbufput: decoders/dcmsfc-b9-a10000-ddata/ldm/gempak/logs/dcmsfc.log-eGEMTBL=/home/ldm 
/g
empak-5.6/gempak/tablesdata/ldm/gempak/ship/YYYYMMDD_sb.gem write error 
^@May 25 20:15:12 pqact[15507]: pipe_prodput: trying again
I have checked that the dcmsfc decoder is installed and executable in the decoders sub-directory. The log directories are writeable by ldm. 

I have attached the relevant files to this message.

Carl