* Michael P. Soulier ([EMAIL PROTECTED]) wrote: > At times this seems to cause mongrel to become unresponsive, and all > requests to the site then fail with a proxy error until mongrel is > restarted. > > I'm not sure of how to troubleshoot this issue. Help appreciated.
Try using gdb to get a backtrace: % gdb `which ruby` <pid of mongrel> Then "bt" to get a list of the functions it's calling. You may need to recompile Ruby with debugging symbols if it's mostly "???". On FreeBSD this is as simple as "portupgrade -fm '-DWITH_DEBUG' ruby" http://eigenclass.org/hiki/ruby+live+process+introspection may be of use. Other options are ktrace, strace and truss (depending on what system you're on) to get an idea of the syscalls it's performing, but this may not be very useful depending on how it's hung. -- Thomas 'Freaky' Hurst http://hur.st/
pgppUOWFF5qu9.pgp
Description: PGP signature
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
