fcgi output inconsistency

[kevin]

When I switch from trac.cgi to trac.fcgi Trac appears to get very unstable. The app works but I get quite a few instances where I click on a link and get a trac/python traceback on the browser rather than the content. Usually clicking 'back' and repeating the action results in the correct response.

[kevin]

The results of clicking on 'Wiki'

[georg]

same happens on my gentoo system with trac 0.9

[kevin]

This is still an issue with 0.9

See new attachment.

[kevin]

Output from trac (0.9) after clicking 'New Ticket'

[mgood]

I think that this is basically the same issue as #2252.

[thomas.jachmann]

I don't think this is a duplicate since the stack trace mentions completely different sections in the code and #2252 doesn't result in errors going back to the browser. They only appear in apache's error log, the browser displays the correct pages.

[rachel@…]

I am seeing this error with Trac 0.9.5 when I run it under fcgid. When I run it with fastcgi, I get the error described in ticket:2252. In both cases I'm using Apache 2.0.54 on CentOS 4.3. In both cases the errors are intermittent and come about every 5-10 page views. I chose to use fastcgi and reduce the timeout value as that provides us with the least annoyance, but neither is really satisfactory.

I am reopening this ticket to flag it, in case this information makes either or both of these behaviors reproducible for anyone at Edgewall. I will be happy to post log files or provide any further info that you may ask for. I haven't heard of this issue on either fcgid or fastcgi in any app other than trac which makes me think it may be trac-related after all. When I have a moment I will install trac 0.9.6 and see if these errors still occur.

[mgood]

It appears this is actually a duplicate of #2783 which has been fixed for 0.10.