Re: "Broken Pipe" tracebacks...

Hello Michael,

Thanks for the response.

Yes, we are running Apache 1.3. Not mod_python, but just usual cgi.

Your comments do seem to corroborate though with what I am seeing.

I doubt we are moving to Apache 2.0 any time soon...

I will pass your remarks on to our Sysadmin, though, for his information...

Thanks again,

-- 
Sheila King
http://www.thinkspot.net/sheila/
http://www.k12groups.org

--On Sunday, January 09, 2005 2:00 PM -0500 "Michael C. Neel"
<[email protected]> wrote:

Date: Sunday, January 09, 2005 2:00 PM -0500
From: "Michael C. Neel" <[email protected]>
Subject: Re: [albatross-users] "Broken Pipe" tracebacks...
To: Sheila King <[email protected]>, [email protected]



> I can't offer you soild confirmation; but I can say I think you're right. 
> We have seen this mostly on apache 1.3 systems with mod_python that
> approach  a moderate load.  Moving sites to Apache 2.0 and also
> decreasing the traffic  to an Apache 1.3 box has shown to decrease the
> amount of these IOErrors.  Apache 2.0 shows almost none of these errors.
> 
> We've spent a good amount of effort tracking these down, and it looks
> like  more to do with Apache 1.3 with mod_python than anything of
> Albatross.  Our  setup isn't exactly the same as yours, as we use the
> mod_python content  handler to invoke Albatross over cgi, but I'd guess
> it's the same issue, esp  if you are on Apache 1.3.
> 
> Mike
> 
> ----- Original Message ----- 
> From: "Sheila King" <[email protected]>
> To: <[email protected]>
> Sent: Saturday, January 08, 2005 3:36 PM
> Subject: [albatross-users] "Broken Pipe" tracebacks...
> 
> 
>> Hello,
>> 
>> I'm running a project that uses Albatross. Finally released our big 
>> project
>> in December. Only, technically, accessible to our own clients with
>> accounts, though...
>> 
>> http://www.QuestAdmin.net
>> (It's still kind of beta-ish, but good enough that we made it available
>> to our clients so they can view billing statements and such...)
>> 
>> I have the application set up to send me emails of the full Python
>> traceback if there are any "unhandled" exceptions, which I then trap and
>> redirect to an error page.
>> 
>> There is one type of error, however, that I'm seeing off and on...
>> namely the "Broken Pipe" error. Here is a portion of a traceback:
>> 
>> (the last few lines of it...)
>> 
>>  File "albatross/context.py", line 123, in flush_content
>>    self.send_content(data)
>>  File "albatross/app.py", line 107, in send_content
>>    self.request.write_content(data)
>>  File "albatross/cgiapp.py", line 52, in write_content
>>    sys.stdout.flush()
>> IOError: [Errno 32] Broken pipe
>> 
>> 
>> Because we are running this app as CGI, and because I have, in test use,
>> actually caused this error myself but not been redirected to the error 
>> page
>> mentioned above, I think this is just a case of the connection to the
>> browser being closed before the cgiapp was able to completely flush the
>> content?
>> (We are running the latest stable version of albatross... 1.20.)
>> 
>> Was hoping for confirmation on this before I have my email function
>> disregard sending me emails of tracebacks for this particular error...
>> 
>> Thanks for any insights or clues...
>> 
>> -- 
>> Sheila King
>> http://www.thinkspot.net/sheila/
>> http://www.k12groups.org
>> _______________________________________________
>> Albatross-users mailing list
>> [email protected]
>> https://www.object-craft.com.au/cgi-bin/mailman/listinfo/albatross-users
>> 
> 
> _______________________________________________
> Albatross-users mailing list
> [email protected]
> https://www.object-craft.com.au/cgi-bin/mailman/listinfo/albatross-users
>