Comment 7 for bug 1306675

Revision history for this message
Jason Stephenson (jstephenson) wrote :

We have been using the above change in our production server for almost a week now with no negative repercussions. The error messages are definitely gone.

We never could pin the problem down to a single PID. Just before applying the above change we added an extra log definition to log the PIDs of the Apache children, and these errors actually seemed to come from different PIDs at relatively the same time. It seems we'd bet spurts of it within a few minutes of each other, and then silence for a while before it would happen again.

Anyway, since we've been using this in production, I'd like to push it to master. However, we've not added the pullrequest tag. Also, I wonder if this should be targeted at 2.6.1 or other milestones as well? We installed master from a branch created on 4/16, so we're basically running 2.6.0 with a couple of bug fix patches thrown in. It seems to me this ought to target 2.6 and 2.6.1.