I had posted a thread couple of weeks ago whereby mongrel just mysteriously stops interacting with my application after an idle period...usually less than 8 hours. http://rubyforge.org/pipermail/mongrel-users/2007-February/002908.html I had hoped this would go away after a few upgrades but to know avail. Interestingly, the process does not die...it still accepts HTTP requests but does not respond...just sits there deaf. I do a cluster::stop and start and we''re back in action. There is nothing at the tail of mongrel_log..and when I make new connections..nothing gets appended The answers to the previously asked questions are as follows: 1) We do not rotate logs (yet) so we don''t use ruby to rotate 2) ruby script/about About your application''s environment Ruby version 1.8.5 (i686-linux) RubyGems version 0.9.1 Rails version 1.2.0 Active Record version 1.14.4 Action Pack version 1.12.5 Action Web Service version 1.1.6 Action Mailer version 1.2.5 Active Support version 1.3.1 Edge Rails revision 175 Application root /home/webapp/visualcareers_3_7 Environment development Database adapter mysql Database schema version 44 3) cat config/database.yml development: adapter: mysql database: server_development username: ****** password: ****** host: my.server.com test: adapter: mysql database: server_test username: ****** password: ****** host: localhost production: adapter: mysql database: server_production username: ****** password: ****** host: localhost -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20070310/cf5da20e/attachment.html
On 3/10/07, Eric Dean <eric at maverixsystems.com> wrote:> > I had posted a thread couple of weeks ago whereby mongrel just mysteriously > stops interacting with my application after an idle period...usually less > than 8 hours. >For the record, I''m seeing the same thing. Any site not being hit for a period of time (exact period unknown) will just go deaf and require a cluster::restart Rails 1.2.2 Mongrel 1.0.1 Apache 2.2.3 w/proxy_balancer -- -------------------------------------------------------------------------------- Jack Baty http://jackbaty.com/ (616) 822-5800 Fusionary http://fusionary.com/ (616) 454-2357 820 Monroe N.W. Suite 212 Grand Rapids, MI 49503
This sounds like the mysql timeout bug. Have you seen this thread? http://rubyforge.org/pipermail/mongrel-users/2006-November/002178.html Regards, Steven Eric Dean wrote:> > I had posted a thread couple of weeks ago whereby mongrel just > mysteriously stops interacting with my application after an idle > period...usually less than 8 hours. > http://rubyforge.org/pipermail/mongrel-users/2007-February/002908.html > > I had hoped this would go away after a few upgrades but to know > avail. Interestingly, the process does not die...it still accepts > HTTP requests but does not respond...just sits there deaf. I do a > cluster::stop and start and we''re back in action. > > There is nothing at the tail of mongrel_log..and when I make new > connections..nothing gets appended > > The answers to the previously asked questions are as follows: > 1) We do not rotate logs (yet) so we don''t use ruby to rotate > > 2) ruby script/about > About your application''s environment > Ruby version 1.8.5 (i686-linux) > RubyGems version 0.9.1 > Rails version 1.2.0 > Active Record version 1.14.4 > Action Pack version 1.12.5 > Action Web Service version 1.1.6 > Action Mailer version 1.2.5 > Active Support version 1.3.1 > Edge Rails revision 175 > Application root /home/webapp/visualcareers_3_7 > Environment development > Database adapter mysql > Database schema version 44 > > 3) cat config/database.yml > > development: > adapter: mysql > database: server_development > username: ****** > password: ****** > host: my.server.com > > test: > adapter: mysql > database: server_test > username: ****** > password: ****** > host: localhost > > production: > adapter: mysql > database: server_production > username: ****** > password: ****** > host: localhost > ------------------------------------------------------------------------ > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
I had this exact same problem. I *think* I''ve tracked down the source: a memory-leaking plugin. In any case Mongrel had nothing to do with it, it was my Rails app. Op 10-mrt-2007, om 18:37 heeft Eric Dean het volgende geschreven:> > I had posted a thread couple of weeks ago whereby mongrel just > mysteriously stops interacting with my application after an idle > period...usually less than 8 hours. > http://rubyforge.org/pipermail/mongrel-users/2007-February/002908.html > > I had hoped this would go away after a few upgrades but to know > avail. Interestingly, the process does not die...it still accepts > HTTP requests but does not respond...just sits there deaf. I do a > cluster::stop and start and we''re back in action. > > There is nothing at the tail of mongrel_log..and when I make new > connections..nothing gets appended > > The answers to the previously asked questions are as follows: > 1) We do not rotate logs (yet) so we don''t use ruby to rotate > > 2) ruby script/about > About your application''s environment > Ruby version 1.8.5 (i686-linux) > RubyGems version 0.9.1 > Rails version 1.2.0 > Active Record version 1.14.4 > Action Pack version 1.12.5 > Action Web Service version 1.1.6 > Action Mailer version 1.2.5 > Active Support version 1.3.1 > Edge Rails revision 175 > Application root /home/webapp/visualcareers_3_7 > Environment development > Database adapter mysql > Database schema version 44 > > 3) cat config/database.yml > > development: > adapter: mysql > database: server_development > username: ****** > password: ****** > host: my.server.com > > test: > adapter: mysql > database: server_test > username: ****** > password: ****** > host: localhost > > production: > adapter: mysql > database: server_production > username: ****** > password: ****** > host: localhost > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users-- www.gomagazine.nl +31643904460 pobox 51059 nl-1007eb amsterdam -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2423 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20070310/ec3b479f/attachment-0001.bin
What is the plugin you believe to be leaking memory? On 3/10/07, joost baaij <joost at spacebabies.nl> wrote:> I had this exact same problem. I *think* I''ve tracked down the > source: a memory-leaking plugin. In any case Mongrel had nothing to > do with it, it was my Rails app. > > Op 10-mrt-2007, om 18:37 heeft Eric Dean het volgende geschreven: > > > > > I had posted a thread couple of weeks ago whereby mongrel just > > mysteriously stops interacting with my application after an idle > > period...usually less than 8 hours. > > http://rubyforge.org/pipermail/mongrel-users/2007-February/002908.html > > > > I had hoped this would go away after a few upgrades but to know > > avail. Interestingly, the process does not die...it still accepts > > HTTP requests but does not respond...just sits there deaf. I do a > > cluster::stop and start and we''re back in action. > > > > There is nothing at the tail of mongrel_log..and when I make new > > connections..nothing gets appended > > > > The answers to the previously asked questions are as follows: > > 1) We do not rotate logs (yet) so we don''t use ruby to rotate > > > > 2) ruby script/about > > About your application''s environment > > Ruby version 1.8.5 (i686-linux) > > RubyGems version 0.9.1 > > Rails version 1.2.0 > > Active Record version 1.14.4 > > Action Pack version 1.12.5 > > Action Web Service version 1.1.6 > > Action Mailer version 1.2.5 > > Active Support version 1.3.1 > > Edge Rails revision 175 > > Application root /home/webapp/visualcareers_3_7 > > Environment development > > Database adapter mysql > > Database schema version 44 > > > > 3) cat config/database.yml > > > > development: > > adapter: mysql > > database: server_development > > username: ****** > > password: ****** > > host: my.server.com > > > > test: > > adapter: mysql > > database: server_test > > username: ****** > > password: ****** > > host: localhost > > > > production: > > adapter: mysql > > database: server_production > > username: ****** > > password: ****** > > host: localhost > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > -- > www.gomagazine.nl +31643904460 pobox 51059 nl-1007eb amsterdam > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >
RMagick. Op 10-mrt-2007, om 20:36 heeft Joey Geiger het volgende geschreven:> What is the plugin you believe to be leaking memory? > > On 3/10/07, joost baaij <joost at spacebabies.nl> wrote: >> I had this exact same problem. I *think* I''ve tracked down the >> source: a memory-leaking plugin. In any case Mongrel had nothing to >> do with it, it was my Rails app. >> >> Op 10-mrt-2007, om 18:37 heeft Eric Dean het volgende geschreven: >> >>> >>> I had posted a thread couple of weeks ago whereby mongrel just >>> mysteriously stops interacting with my application after an idle >>> period...usually less than 8 hours. >>> http://rubyforge.org/pipermail/mongrel-users/2007-February/ >>> 002908.html >>> >>> I had hoped this would go away after a few upgrades but to know >>> avail. Interestingly, the process does not die...it still accepts >>> HTTP requests but does not respond...just sits there deaf. I do a >>> cluster::stop and start and we''re back in action. >>> >>> There is nothing at the tail of mongrel_log..and when I make new >>> connections..nothing gets appended >>> >>> The answers to the previously asked questions are as follows: >>> 1) We do not rotate logs (yet) so we don''t use ruby to rotate >>> >>> 2) ruby script/about >>> About your application''s environment >>> Ruby version 1.8.5 (i686-linux) >>> RubyGems version 0.9.1 >>> Rails version 1.2.0 >>> Active Record version 1.14.4 >>> Action Pack version 1.12.5 >>> Action Web Service version 1.1.6 >>> Action Mailer version 1.2.5 >>> Active Support version 1.3.1 >>> Edge Rails revision 175 >>> Application root /home/webapp/visualcareers_3_7 >>> Environment development >>> Database adapter mysql >>> Database schema version 44 >>> >>> 3) cat config/database.yml >>> >>> development: >>> adapter: mysql >>> database: server_development >>> username: ****** >>> password: ****** >>> host: my.server.com >>> >>> test: >>> adapter: mysql >>> database: server_test >>> username: ****** >>> password: ****** >>> host: localhost >>> >>> production: >>> adapter: mysql >>> database: server_production >>> username: ****** >>> password: ****** >>> host: localhost >>> _______________________________________________ >>> Mongrel-users mailing list >>> Mongrel-users at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/mongrel-users >> >> -- >> www.gomagazine.nl +31643904460 pobox 51059 nl-1007eb amsterdam >> >> >> >> _______________________________________________ >> Mongrel-users mailing list >> Mongrel-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-users >> >> > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users-- www.gomagazine.nl +31643904460 pobox 51059 nl-1007eb amsterdam -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2423 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20070311/efc280e8/attachment.bin