Hi. This is just an update to the thread I started re running Bugzilla on OpenBSD 3.8: Possibly not directly OpenBSD related, but it might help anyone searching the archives of this list for the same problem.

(as posted to  netscape.public.mozilla.webtools)
"An update on this problem that I had - posted here in case anyone has
the same problem and finds this thread. (Recap: OpenBSD 3.8 + MySQL +
Bugzilla 2.20 or 2.18 - Premature end of server headers error every so
often (not reliably reproduced) with no other error information
anywhere at all)

I traced through the bugzilla code with syslog calls until I hit the
offending line of code that caused everything to fail -
Bugzilla/Auth/Login/WWW/CGI/Cookie.pm:        $dbh->do("UPDATE
logincookies SET lastused=NOW() WHERE cookie=?" (etc.)

MySQL didn't complain about the statement - I set all the appropriate
error and tracing flags - but it still silently barfed, so I tried
switching the backend to Postgresql, and everything now works."

Why? No idea - it works now so I'm going to the pub. Hope this helps someone.

Cheers,

Trystan

##############################
Re:
List:       openbsd-misc
Subject: Re: OpenBSD 3.8 & Bugzilla - does anyone have this running ok?
From:       Trystan Negus <trystan.negus () pellenys ! org ! uk>
Date:       2005-11-16 15:56:49
Message-ID: 437B56C1.7080106 () pellenys ! org ! uk
[Download message RAW]

Thanks - that page looks like a good place to start. It'll be useful
stuff to know about anyway - I'll start reading.

Much appreciated

Trystan

Alexander Farber wrote:
> IMHO when you get situations like this:
>
> On 11/16/05, Trystan Negus <[EMAIL PROTECTED]> wrote:
>
>> Symptom: Using a browser, configuration pages occasionally (1 in 5
>> refreshes, more or less) return an error 500 page, coupled with
>> 'Premature end of script headers' error in Apache's error log. No errors >> in /var/log/messages. Refresh the page, and all works fine....until a
>> number of refreshes (or config page links) later.
>>
>
> then you have to ensure that you have just 1 Apache child running
> (httpd -X) before you start further debugging/troubleshooting:
> http://perl.apache.org/docs/1.0/guide/debug.html

Reply via email to