On Oct 23, 8:15 pm, Graham Dumpleton <[email protected]> wrote: > On 22 October 2010 07:10, Patrick Michael Kane <[email protected]> wrote: > > > Hey Graham: > > > Just had another freeze, this time with flock -- backtraces from two > > of the WSGI processes below. > > > The Apaches are in the same state as with the SysV mutex, blocking on > > this connect: > > > connect(69, {sa_family=AF_FILE, path="/home/actionkit/releases/ > > stable/apache/logs/.2028.61.7.sock"}, 110 > > > Let me know if you need more info! > > If possible, next time can you capture it across all process in the > daemon process group. > > Want to validate that whether they are all stuck on flock() or sysvsem > lock in Thread 2. > > This will tell me whether issue is that no process is getting past > lock, or whether one is getting to do apr_poll() on listener socket, > but not seeing a notification.
Hey Graham: Is there a shortcut to get gdb to do this for me? Or do I need to script something to run the backtrace against each process? -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
