Re: 'premature end of script headers' error

Tom Ekberg <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.user
Message-ID <[email protected]>
Bernhard,

Thank you for your response. I can find no traceback. None in the log file, nor the apache ssl_error_log which is where I have seen stack traces before. I peppered my systems tracker's roundup.cgi with more log messages - there is no python error at that level.  I made sure to catch any exception. I wrote a wrapper class (snarfed most of the code from http://code.activestate.com/recipes/577555-object-wrapper-class/) to have HTML text go to the log file as well as to sys.stdout. When I'm displaying the issue detail (issue.item.html) I see lots of HMTL in the log file. When I change a simple attribute and press the 'submit' button I see the SQL statements that I saw before, but no HTML text. This is why apache is complaining about the script headers - there aren't any. I'll have to dig deeper in the roundup/cgi/* code to determine where the error is. I'm thinking that something like this happens:

   create DB transaction
   do a lot of selects
   perform update and inserts
   some unknown error happens
   transaction is aborted

I'm pretty certain the database itself isn't the problem. I modified the same issue's attribute with roundup-admin and it works fine. I also did the UPDATE cut/pasted from the log using psql (the postgres command line) while logged as the user I'm using in the tracker. That also works fine.

If you think I'm going down the wrong path (digging into the roundup/cgi/* code) I'd appreciate your input.

Tom Ekberg
Senior Computer Specialist, Lab Medicine
University of Washington Medical Center
1959 NE Pacific St, MS 357110
Seattle WA 98195
cell: (253) 561-2509
email: [email protected]

On Wed, 11 Dec 2013, Bernhard Reiter wrote:

> On Tuesday 10 December 2013 at 23:17:14, Tom Ekberg wrote:
>>   [Sun Dec 08 15:21:34 2013] [error] [client 172.16.6.108] Premature end of
>> script headers: roundup.cgi,
>
> Hmm, no traceback somewhere?
> I'd usually start with adding logging output to roundup to follow the
> the executed code paths.  Start with the cgi script and identify where the
> logging output or stderr/stdout goes.
>
>
> -- 
> www.intevation.de/~bernhard (CEO)    www.fsfe.org (Founding GA Member)
> Intevation GmbH, Osnabrück, Germany; Amtsgericht Osnabrück, HRB 18998
> Owned and run by Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.