Has anyone ever experienced this problem? Every 12-24 hours *one of* my mongrel processes gets a TERM signal and quits. There is all I get in my mongrel log.. ** Mongrel available at 0.0.0.0:8003 ** TERM signal received. And my rails-log is silent too. No request starting. Just the end of a successful request and then nothingness. The other processes are doing just fine and stay up for good. Anyone know what''s going on here? Oh yeah, and its lighty-proxy + mongrel on Ubuntu. -hampton. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060702/7b9f3c59/attachment.html
Hi, I''ve not been getting a TERM signal, but I have been getting a random HUP signal. It is still happening and I have no idea why. There''s a thread from mid-June on the mongrel mailing list. Cheers, Bob On Jul 2, 2006, at 9:55 AM, Hampton wrote:> Has anyone ever experienced this problem? Every 12-24 hours *one > of* my mongrel processes gets a TERM signal and quits. > > There is all I get in my mongrel log.. > > ** Mongrel available at 0.0.0.0:8003 > ** TERM signal received. > > And my rails-log is silent too. No request starting. Just the end > of a successful request and then nothingness. > > The other processes are doing just fine and stay up for good. > Anyone know what''s going on here? > > Oh yeah, and its lighty-proxy + mongrel on Ubuntu. > > -hampton. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails---- Bob Hutchison -- blogs at <http://www.recursive.ca/ hutch/> Recursive Design Inc. -- <http://www.recursive.ca/> Raconteur -- <http://www.raconteur.info/> xampl for Ruby -- <http://rubyforge.org/projects/xampl/> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060702/ab0bee4c/attachment-0001.html
On Sun, 2006-07-02 at 09:55 -0400, Hampton wrote:> Has anyone ever experienced this problem? Every 12-24 hours *one of* > my mongrel processes gets a TERM signal and quits. > > There is all I get in my mongrel log.. > > ** Mongrel available at 0.0.0.0:8003 > ** TERM signal received. > > And my rails-log is silent too. No request starting. Just the end of a > successful request and then nothingness. > > The other processes are doing just fine and stay up for good. Anyone > know what''s going on here? > > Oh yeah, and its lighty-proxy + mongrel on Ubuntu.A few people have reported this, and the only time I''ve seen it was when I ran under a Xen VPS and there wasn''t enough ram for the process, so Linux went in and started killing processes at random. I believe it does this if the CPU or memory gets dominated by a process, but I''m not sure how to turn it off. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
> A few people have reported this, and the only time I''ve seen it was when > I ran under a Xen VPS and there wasn''t enough ram for the process, so > Linux went in and started killing processes at random. I believe it > does this if the CPU or memory gets dominated by a process, but I''m not > sure how to turn it off.it''s probably something with ulimit or rlimit. by default, on the two distro ive tried in the past 5 years, there are no limits, which means a script can get in an infinite loop, chew up all RAM, chew up all swap, then make the system entirely unresponsive with nonstop disk-grinding until it is reset..