Either that, or the gdb did not show the stack for the frozen processes.

my kenrel version is   : 2.6.26-bpo.1-amd64.

my apache version is : 2.2.9-10

libapr version is         : 1.2.12-5+lenny1



Graham Dumpleton wrote:

> Most odd.
>
> All the mod_wsgi daemon processes are waiting for a request to arrive.
> They aren't actively handling any.
>
> All the Apache server child processes are waiting for initial
> handshaking response from mod_wsgi daemon processes after having just
> sent a request to them.
>
> To me this looks a bit like the epoll() implementation on your system
> is broken which is causing a failure of mod_wsgi daemon processes to
> detect a new request has been sent.
>
> I would be suggesting that you rebuild Apache/APR such that use of
> epoll() is disabled and it instead fallbacks to either poll() or select
> (). Unfortunately, not exactly sure how you can override 'configure'
> for Apache/APR to stop it using epoll() if it exists.
>
> That is about the only pointer I can give.
>
> What versions of Apache/APR are you using?
>
> Graham
>
> On Oct 5, 12:48 am, Omry Yadan <[email protected]> wrote:
>   
>> apache backtraces attached.
>>
>>
>>
>>     
>>> I will configure monit to use this command before it restarts apache in
>>> the next time it hangs:
>>>       
>>> pgrep apache2 | xargs -i bash -c "gdb -ex \"set height 0\" -ex \"thread
>>> apply all bt\" --batch -p {}"  > apache.backtrace.txt
>>>       
>>> it's supposed to dump the backtrace of all apache processes to a file.
>>> hopefully it will contain something useful.
>>>       
>>  apache.backtrace.zip
>> 9KViewDownload
>>     
> >
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to