similar to: Firewall closes database connections resulting in hung mongrel processes

Dear ALL, I saw this in article from mongrel faq, Q: Mongrel stops working if it''s left alone for a long time. If you find that Mongrel stops working after a long idle time and you''re using MySQL then you''re hitting a bug in the MySQL driver that doesn''t properly timeout connections. What happens is the MySQL *server* side of the connection times out and

Hi, I have had trouble with mongrel freezing after a period of inactivity. Following the advice from the mongrel FAQ, I added: ActiveRecord::Base.verification_timeout = 14400 to my environment.rb file. Unfortunately, that registered a mongrel error: "uninitialized constant ActiveRecord (NameError)" How do I overcome this one? I tried: require ActiveRecord::Base but that registered

Hello everyone, I have developed several ruby apps which are currently live in production. Recently I have encountered a problem where my apps stop responding after a long period of inactivity. I am using Webrick as the server with Rails 1.1.2 and mysql 5.0.21. I have dug up other issues people have had with mysql dropping connections after 8 hours, and the supposed fix of adding an

Hi I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are detected by Rails (at least nothing is in the Rails log). Nothing untoward is in the Mongrel log. If you try and visit the application, the request times out

How do I setup a sweeper to restart stale or hung mongrel servers? -- Jared Brown jaredbrown at gmail.com (765) 409-0875 7001 Central Ave Indianapolis, IN 46220 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060907/0994017f/attachment.html

I have a rails app serving up XML on an infrequent basis. This is being run with mongrel and mysql. I''ve found that if the app does not get exercised for longer than a few hours it goes dead ("Lost Connection to MySQL") and starts throwing Errno::EPIPE errors. It seems that the mysql connection gets timed out for inactivity or something like that. It can be restarted with

Greetings, I need some help... please be gentle :-) MY SETUP: Solaris-X86, ruby-1.8.4, Apache-2.2.0, Mongrel-0.3.13.4, MySql-4.1.10a I am using the typical setup with apache proxying request to mongrel with mod_proxy_balancer. Currently, I am only running a single instance of mongrel behind the proxy. I am also using the following gems with this app: capistrano (1.2.0) daemons (1.0.2)

As a follow up from my previous post, I am pondering some changes to my env. I read that with AR I should change the verification timeout to be lower than the MySQL db Interactive_timeout. Now, I have done some performancing tuning to mysql in LAMP env''s but not RoR. MySQL typical set the default interactive_timeout to 8hrs (28800) this has bitten me a few times with sleeping processess

Hi, I have a ruby on rails website. Server configuration is: 1. Nginx 2. 4 mongrel clusters running on different ports. After a long idle time few of the mongrel clusters stops responding. I have set "ActiveRecord::Base.verification_timeout = 14400" in environment.rb file, but still it''s not working. On executing "lsof -i -P | grep CLOSE_WAIT" command, I usually

i am using the following comman to fire up mongrel: [sergio@vb_workstation chatlogger]$ mongrel_rails start -d -p 8088 ** You have sendfile installed, will use that to serve files. and everything works fine until some point at night.. i think it is pooping out some time in the middle of the night.. if i try to hit the app in the morning, it just stalls out.. if i restart it, it''s

Here is my first major problem with dovecot. I am running rc15 on FreeBSD 6.1. I run dovecot supervised by DJB's daemontools. I run only the pop3 service. A colleague informed me that pop3 service was simply not responding. They could not rcv mail. When I checked the server, tail-ing dovecot.log, here is what was scrolling: [wash at nbi ~]$ tail -f /var/log/dovecot.log dovecot: Nov 23

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

Hi, I have Apache (2.2) setup to proxy requests through to Mongrel (0.3.12.4) for a Rails (1.1.2) application (on ruby 1.8.4). The setup is great, but I''m experiencing some nightly failures. I thought I''d post here before digging in too deeply, but it looks like Rails is going into lala land and Mongrel can''t recover... Seems like everything gets all backed up in

Hi. I have mongrel 1.0.1 running a really simple application and found to lock up (rarely, but still). There''s nothing in the logs, it just stops responding. When I mongrel_rails stop it, I get lots of entries like: Waiting for 3 requests to finish, could take 60 seconds /usr/lib64/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:675:in `process''

A bit about my environment. Fedora Core 6 httpd 2.2.2 ruby (compiled) 1.8.5 gem 0.9.4 rails 1.2.3 ruby/mysql C library 0.2.6 mysql 5.0.27 interactive_timeout = 28800 wait_timeout = 28800 mongrel 1.0.1 I''ve had this experience in other environments with different versions but this configuration is the most recent attempt I''ve made. I get the "Broken Pipe" error after

A few weeks ago I updated my development computer to Snow Leopard (finally). I put it off because I was in the middle of a project, and it seems its a good thing I did. Last week I started something new and it seems that any rails related ruby process will get ... stuck, I guess is the best word. I''ve seen it happen as soon as a minute, or take as long as an hour. It happens for

Hi I posted this to the Ruby on Rails Talk group but I thought I''d post it here too as it''s probably a more appropriate group. Hope this is ok. I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are

I have the very same problem with samba 3.0.14a running on Debian Sarge and have found no solution yet. Has anyone found a solution in the meanwhile? Could it perhaps be due to a failure in our networking hardware? > We've seen Samba crash and burn twice in the last 48 hours - it just > started happening, and we have no idea what might be causing it. I'm > hoping that

Running samba 2.06 on Solaris 2.6 and CIFS/9000 on HPUX11. Accessing from NT 4.0 Terminal server. We are seeing the following symptoms. Can anyone offer any diagnostic advice... Users will connect to samba servers and be working along ok. Without warning, the connection starts to act flaky. e.g. can't save documents, file system browsing becomes very erratic. A quick "ps | grep

For the past three weeks (this is really a guess as I just noticed it last week) I have been seeing many processes started in terminal windows that are no longer in existence. They were started using something like: gnome-terminal -x weather.pl -wr where weather.pl is a simple Perl script that prints a text file and periodically updates it by clearing the screen and re-writing the file to get the