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

20051123: LDM 6.4.3 pipe_prodput, pbuf_flush, pipe_put errors (cont.)



>From: Mark Seefeldt <address@hidden>
>Organization: CU
>Keywords: 200511212255.jALMtu7s026640 GEMPAK LDM pqact.conf

Hi Mark,

>Thank you for the input.

No worries.

>I went through all of the checks which you 
>suggested and they all passed, giving no indications as to the cause of 
>this problem.

>-the decoders programs are executable by ALL

Good.

>-the indicated libraries are present

Good.

>-the data directory is writable by ldm

Good.

>-the GEMPAK tables are readable by ldm, but they appear to be located in 
>a different directory than indicated in your message, the directory is:
>   /home/gempak/GEMPAK5.8.3a/gempak/tables
>This directory does correspond to the entry in the pqact.gempak file.
>ie.  -e GEMTBL=/home/gempak/GEMPAK5.8.3a/gempak/tables

All that matters is that the reference to the tables directory in
pqact.conf actions matches the GEMPAK installation, and that the
files are readable by the user running the LDM.

>Feel free to let this problem sit on the burner until Steve gets back 
>and is able to address it.  This error is not holding back anything 
>critical.

I don't think that this is a GEMPAK problem.  Rather, I think it
is most likely a permissions problem (even given your report above).

>I will also add that this problem seems quite similar to an email post 
>from a 20051114 which was not able to provide an immediate answer.
>http://www.unidata.ucar.edu/support/help/MailArchives/ldm/msg04361.html

Similar, but that exchange is related to a logging problem that showed
up on AIX platforms.  I am under the impression that your system is
not AIX, true?

Would it be possible to get a login to your system as 'ldm' so I
could take a look for myself?

>Thanks

No worries.

>Unidata Support wrote:
>>> From: Mark Seefeldt <address@hidden>
>>> Organization: CU
>>> Keywords: 200511212255.jALMtu7s026640 GEMPAK
>> 
>> Hi Mark,
>> 
>> Chiz is on travel for the week, so the support you get won't be up
>> to its normal standards (i.e., I'll try to help out) :-)
>> 
>>> Recently I installed LDM 6.4.3 and GEMPAK 5.8.3a on a Red Hat Enterprise 
>>> Linux v.4 system.  As a part of the installation process I generated a 
>>> new pqact file using: gen_pqact.csh  I have attached this pqact.gempak file
> .
>> 
>> OK.
>> 
>>> Since restarting the LDM I have been receiving a persistent error in my 
>>> log file.  Once such example is:
>>> Nov 21 07:00:52 foehn pqact[7583] ERROR: pbuf_flush (28) write: Broken pipe
>>> Nov 21 07:00:52 foehn pqact[7583] ERROR: pipe_put: 
>>> decoders/dcidft-v2-eGEMTBL=/home/gempak/GEMPAK5.8.3a/gempak/tablesdata/gemp
> ak/
>>> idft/YYYYMMDDHH.idft 
>>> write error
>>> Nov 21 07:00:52 foehn pqact[7583] ERROR: pipe_prodput: trying again
>>>
>>> I have attached the entire log file as it is a routine error with 
>>> several decoders.
>> 
>> LDM Broken pipe errors indicate that the entire product that pqact is
>> writing to STDOUT is not read by the decoder.  These errors are
>> typically caused by one of two things:
>> 
>> - the decoder is not executable by the system it is installed on
>> 
>> - the directory to which the decoder is trying to write is not writable
>>   by the user running the LDM
>> 
>> - the GEMPAK table(s) that the decoder needs is not readable by
>>   'ldm'
>> 
>>> I came across a similar error while searching the Unidata email archive, 
>>> and found no solution.
>> 
>> First check to make sure that the decoder(s) that are not working
>> (e.g., ~ldm/decoders/dcidft) are executable on your system as the
>> user running the LDM:
>> 
>> <as 'ldm'>
>> cd ~ldm
>> ls -alt decoders/dcidft          <- must be marked as executable
>> ldd decoders/dcidft              <- shows shared libraries that are used
>> 
>> If this shows that one or more shared libraries can't be found, then
>> the decoder execution will fail.
>> 
>> If all shared libraries are found, then make sure that the directory
>> the decoder is trying to write in is writeable by 'ldm'.
>> 
>> Finally, make sure that the 'ldm' user can read the GEMPAK tables that
>> are referenced in the pqact.conf actions (e.g.,
>> /home/gempak/GEMPAK5.8.3a/gempak/tablesdata/gempak/)
>> 
>>> Let me know if there is anything else that you could use to further 
>>> diagnose this error.
>> 
>> Your listing seems to indicate that _no_ GEMPAK decoder is running.
>> If this is the case, I suspect that the problem is either the decoders
>> are not executable or that the 'ldm' user is not allowed to read the
>> GEMPAK tables it needs.
>> 
>>> Thanks
>> 
>> Please let me know if this helped.

Cheers,
 
Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.