Spawned ruby process by mod_passenger on apache 2 taking 100% CPU
Hi all,
I have installed mod_passenger on my Apache 2 under Debian Squeeze 64 bits. My problem is that, just starting apache with mod_passenger enabled (no site configured to use it) spaws a ruby process that eats all available cpu. I'm pretty sure this is a misconfiguration on my part, but I'm not quite sure where it comes from and how to track down the problem. It used to work perfectly and a some point it went wrong. Any hint on how to identify the problem who be immensely appreciated ! Thanks ! |
I don't know if you should run Passenger w/o site configuration but there's at least one bug listed at http://code.google.com/p/phusion-pas.../detail?id=711 and there's a nice writeup on how to debug Rails processes at http://warwickp.com/2010/06/debuggin...er-with-nginx/ (never mind the Nginx part), the latter may help you ident the problem.
|
Solved
Hi,
Sorry for the slow reply and thanks for your help. Running passenger with or without site config didn't change anything (there used to have a site configured, but I disabled it for testing purposes when I discovered the problem), but in fact, the problem didn't come from there. I suspect it came from the leap second on June 30th that wasn't handled correctly for some reason by Passenger/Ruby. In fact I found this thread describing the same problem I had. The solution was "just" to reboot the server and indeed, it works now. I still don't know where the real problem was though, but at least my server works. Thanks again! |
All times are GMT -5. The time now is 08:31 AM. |