[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.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20051123: LDM 6.4.3 pipe_prodput, pbuf_flush, pipe_put errors (cont.)
  • Date: Mon, 28 Nov 2005 11:50:06 -0700
>From: Mark Seefeldt <address@hidden>
>Organization: CU
>Keywords: 200511212255.jALMtu7s026640 GEMPAK LDM pqact.conf

Hi Mark,

re: your OS is not AIX
>Correct, it is a RedHat Enterprise Linux v4.

Chiz and I logged onto foehn this morning and looked at the ldmd.log
pipe_put errors you are getting.  Chiz commented that some of the
decoders are most likely timing out due to lack of new data and
exiting.

The pqact.gempak entries for processing are sending all of a certain
type of product to the decoder using a PIPE action that does not
close.  What is going on is that the next time that pqact has a product
to send to the decoder, the decoder has exited so the pipe write
fails.  pqact then retries the same action (it will always retry once
for each failed invocatino) and a new invocation of the decoder is
started, and it succeeds.

To test the assertion that the GEMPAK decoders are timing out and
exiting, Chiz added a timeout of 7200 seconds for dcwstm at about 18:45
UTC today (Monday, NOvember 28).  If the timeout assertion is correct
you will not see any more errors from dcwstm while weather rolls across
the country.

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.