Ok, well there's actually two apache process both spiking.

The first one:
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7bc456b in __read_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x080793e4 in ap_mpm_pod_check ()
#3  0x080773b3 in ap_graceful_stop_signalled ()
#4  0x0807751b in ap_graceful_stop_signalled ()
#5  0x080775e2 in ap_graceful_stop_signalled ()
#6  0x08078094 in ap_mpm_run ()
#7  0x0807ede5 in main ()

And the other one:
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7bc456b in __read_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x080793e4 in ap_mpm_pod_check ()
#3  0x080773b3 in ap_graceful_stop_signalled ()
#4  0x0807751b in ap_graceful_stop_signalled ()
#5  0x0807816c in ap_mpm_run ()
#6  0x0807ede5 in main ()

Does this tell you anything?


On 10/28/06 5:30 AM, "Christian Boos" <[EMAIL PROTECTED]> wrote:

> 
> Christian wrote:
>> Hello Christian,
>> 
>> I did the patch, reinstalled...but the problem persists and we have
>> apache2 spiking again, I did an update of all the packages on ubuntu
>> but still that didn't do it.
>>   
> ok
>> It really only started with 0.10, you mentioned a thread dump, how do
>> we go about doing that?
>>   
> 
> With ps or top, get the pid of the apache process that spikes to 100%
> (say 1234).
> Then, start gdb, and do "attach 1234". You're now attached to that
> process and you can to a 'bt' (backtrace) to see where it is stuck.
> There are additional tricks to get access to the Python stacktrace from
> there [1], but the C stacktrace should already be a good start to
> understand what's going on.
> 
> 
> -- Christian
> 
> [1] http://trac.edgewall.org/ticket/1401#comment:14
> 
> 
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to