> --
> You received this message because you are subscribed to the Google Groups
> "Phusion Passenger Discussions" group.
> To post to this group, send email to phusion-...@googlegroups.com.
> To unsubscribe from this group, send email to
> phusion-passen...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/phusion-passenger?hl=en.
--
Phusion | Ruby & Rails deployment, scaling and tuning solutions
Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)
That's not the only way to use crash-watch. Use --dump to immediately
dump the backtrace of a running process.
> It stay at around 2000% CPU for only a few seconds
> and after that it becomes a normal process. And,"kill -s SIGHUP pid" doesn't
> help either as I cannot find any information regarding the SIGHUP process in
> production.log or exception.log.
Look in the web server's global error log. SIGHUP causes the Ruby
backtrace to be written there if Ruby is able to respond to signals.