Omry Yadan wrote: >> Hi all, >> I am starting a second thread with the same name, >> > > Hello Omry, > > I thing we missed round one... > Round one was a about a year ago, see this: http://www.mail-archive.com/search?q=apache+down&l=trac-dev%40googlegroups.com
> In any case, it would help to tell us more about your system information > (i.e. what you see in /about when logged in as a user with TRAC_ADMIN > permissions). In particular the Trac version and the mysql bindings > details (built with multithread support or not). > Trac : 0.11stable-r7763 MySQL: server: "5.0.51a-24+lenny2-log", client: "5.0.51a", thread-safe: 1 MySQLdb: 1.2.2 >> I was supposed to get python stack trace and not python interpreter >> stack trace. >> >> > > Use pystack command for that. Also, dump the stack for all the threads > in the process. > how do I dump stack for all threads? (and btw: how do I even list the threads?) when I typed pystack, I get: (gdb) pystack Current language: auto; currently asm and gdb appears to be stuck in a loop. at least, it takes a very long time to normally return from the call. I ended up ctrl+breaking it. >> any help will be appreciated. >> >> >> > > Looks like an interesting bug ;-) When apache gets "stuck", is the CPU > maxed out? > We somehow have something similar on t.e.o, but with fcgi and postgresql. > t.e.o = trac.edgewell.org ? when I reproduce the problem by sieging the timeline - yes, there is an apache process that uses 100% of the cpu. but I`m not sure I am reproducing the same problem that regularly gets my apache stuck. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
