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

Re: pbuf_flush (3) write: Broken pipe



Alan,

I can find no reason for the pqact(1) process to misbehave in this
manner.

Would you please put the pqact(1) in question into VERBOSE logging mode
and send me a typical log-file excerpt showing the problem.

Regards,
Steve Emmerson

------- Original Message

Date:    Mon, 22 Aug 2005 15:44:08 -0400
From:    "Alan Hall" <address@hidden>To:      Steve Emmerson <address@hidden
          .ucar.edu>
Subject: Re: pbuf_flush (3) write: Broken pipe

This is a multi-part message in MIME format.
--------------010200060905070806090809
Content-Type: multipart/alternative;
 boundary="------------060402000306080005080705"


--------------060402000306080005080705
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The output of the decompress process (from Harry Edmond) is very basic 
and really doesn't give too many messages, error or other wise.  The odd 
thing is it was working on Friday thru to Saturday and then started 
having problems.  Nothing on the server had changed.  When I recycled 
the ldm daemon, it started writing again with no problems. 

Very odd situation. 

Alan.

Steve Emmerson wrote:

>Alan,
>
>  
>
>>Date: Mon, 22 Aug 2005 13:36:36 -0400
>>From: "Alan Hall" <address@hidden>
>>To: address@hidden
>>Subject: pbuf_flush (3) write: Broken pipe
>>    
>>
>
>The above message contained the following:
>
>  
>
>>I just upgraded to ldm-6.4.1 and I am suddenly getting alot of 
>>"pbuf_flush (3) write: Broken pipe" on the NEXRAD Level II decompress 
>>software. 
>>
>>The pqact.conf entry is:
>>
>>NEXRD2<tab>^L2-BZIP2/((....)/(........)(......).*)<tab>PIPE<tab>-close<tab>/h
ome/ldm/nexradII/bin/nr2_decomp 
>>nr2_\2\3_\4 \1
>>    
>>
>
>The "Broken pipe" message means that the pqact(1) process couldn't
>write the NEXRAD2 data-product to the "nr2_decomp" decoder-process
>because the pipe to that process was closed.  This could occur
>because the decoder-process closed its end of the pipe or because the
>decoder-process terminated.
>
>Does the error-output of the decoder-process indicate any problem?
>
>Regards,
>Steve Emmerson
>  
>

--------------060402000306080005080705
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The output of the decompress process (from Harry Edmond) is very basic
and really doesn't give too many messages, error or other wise.&nbsp; The
odd thing is it was working on Friday thru to Saturday and then started
having problems.&nbsp; Nothing on the server had changed.&nbsp; When I recycled
the ldm daemon, it started writing again with no problems.&nbsp; <br>
<br>
Very odd situation.&nbsp; <br>
<br>
Alan. <br>
<br>
Steve Emmerson wrote:
<blockquote cite="address@hidden"
 type="cite">
  <pre wrap="">Alan,

  </pre>
  <blockquote type="cite">
    <pre wrap="">Date: Mon, 22 Aug 2005 13:36:36 -0400
From: "Alan Hall" <a class="moz-txt-link-rfc2396E" href="mailto:address@hidden
gov">&lt;address@hidden&gt;</a>
To: <a class="moz-txt-link-abbreviated" href="mailto:address@hidden
">address@hidden</a>
Subject: pbuf_flush (3) write: Broken pipe
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The above message contained the following:

  </pre>
  <blockquote type="cite">
    <pre wrap="">I just upgraded to ldm-6.4.1 and I am suddenly getting alot of
 
"pbuf_flush (3) write: Broken pipe" on the NEXRAD Level II decompress 
software. 

The pqact.conf entry is:

NEXRD2&lt;tab&gt;^L2-BZIP2/((....)/(........)(......).*)&lt;tab&gt;PIPE&lt;tab&
gt;-close&lt;tab&gt;/home/ldm/nexradII/bin/nr2_decomp 
nr2_\2\3_\4 \1
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The "Broken pipe" message means that the pqact(1) process couldn't
write the NEXRAD2 data-product to the "nr2_decomp" decoder-process
because the pipe to that process was closed.  This could occur
because the decoder-process closed its end of the pipe or because the
decoder-process terminated.

Does the error-output of the decoder-process indicate any problem?

Regards,
Steve Emmerson
  </pre>
</blockquote>
</body>
</html>

--------------060402000306080005080705--

--------------010200060905070806090809
Content-Type: text/x-vcard; charset=utf-8;
 name="alan.hall.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="alan.hall.vcf"

begin:vcard
fn:Alan Hall
n:Hall;Alan
org:(828)271-4071;NOAA's National Climatic Data Center
adr;dom:;;151 Patton Ave;Asheville;NC;28801-5001
email;internet:address@hidden
title:IT Team Leader
tel;work:(828)271-4071
tel;fax:(828)271-4022
x-mozilla-html:TRUE
version:2.1
end:vcard


--------------010200060905070806090809--

------- End of Original Message


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.