search for: verification_timeout

...ound the following: "Thu Nov 16 09:21:00 PST 2006: Reaping 1 threads for slow workers because of ''shutdown'' Thread #<Thread:0x8d54f50 run> is too old, killing. Waiting for 1 requests to finish, could take 60 seconds." 4) I tried adding "ActiveRecord::Base.verification_timeout = "14400" to my rails environment.rb file, as per the FAQ, this had no effect. MOVING FORWARD I''m not really sure where to go from here. Like I said, I have a strong suspicion that MySql is the culprit, but I''m not sure how to fix the problem. If anyone could give...

...#39;'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 closes, but the MySQL *client* doesn''t detect this and just sits there. What you have to do is set: ActiveRecord::Base.verification_timeout = 14400 Or to any value that is lower than the MySQL server''s *interactive_timeout*setting. This will make sure that ActiveRecord checks the connection often enough to reset the connection.. Could anybody please tell me in which file I have to update this "ActiveRecord::Base.verifi...

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

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

My app consists of receiving emails with image attachments from its users so I have been employing the MMS2R gem and Fetcher. Every 60 seconds the app goes to the email server to fetch emails. Under Rails 2.1.1 things worked fine - when I received an email, the email was fetched, parsed and saved to the database. However I needed to upgrade to Rails 2.2.2 for unrelated reasons and now I get the

...countered 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 ActiveRecord::Base.verification_timeout value less than the MySQL interactive_timeout value. My mysql server interactive_timeout is set to the default 28800 seconds (8 hours) and I''ve tried setting the active record verification_timeout to something small like 1800 (30 mins). My understanding is that after the verification_...

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 the same error, only for this line instead. Thanks, and sorry for t...

...led me to the mongrel faq: http://mongrel.rubyforge.org/faq.html specifically the questions "Mongrel stops working if it''s left alone for a long time.", and "Why do I get MySQL ''lost connection to database'' errors?". Setting "ActiveRecord::Base.verification_timeout = 14400" did not have any benifit (even tried going as low as 300). However if I''m understanding correctly this appears to tell verify_active_connections that it only has to check a connection for timeouts once every so many seconds. It might be useful to be able to configure this in...

Hi, in a production environment we are running into "MySQL server has gone away" errors (see below) when we call rebuild_index in aaf. This happens sporadically. Any suggestions for what might be wrong or workarounds? I guess we try a reconnect before we call rebuild_index? Matthew ActiveRecord::StatementInvalid (Mysql::Error: MySQL server has gone away: SELECT count(*) AS

...y set up. Cent OS 4.3 Apache 2.0 Fast CGI 2.4.0 Rails 1.1 Mysql 5.0 The app starts up fine, but every morning it refuses to start and gives me the dreaded Application error untill I reload Apache. I thought my database was timing out so I added this line to my environment.rb ActiveRecord::Base.verification_timeout = 3000 My database is set to drop inactive connections after 2 hours, so my database should keep the connection open. I can watch the processes on mysql and the rails connection is dropped after about 10 minutes. If I try to access the web page after this timeout, the app re-connects perfectly....

...available, any time my code tries to query the remote database it hangs for a few minutes until it times-out. I would very much like to change the timeout value to something lower so my rails app can continue to operate at least semi-normally while the remote db is unavailable. i tried using verification_timeout, not sure if i did something wrong but it didn''t work.. tried Mysql::OPT_CONNECT_TIMEOUT (or something like that) and that didn''t seem to do much either, again not sure if i used it right (both have slim to none documentation).. lastly i tried wrapping different stuff in a Tim...

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

Would anyone happen to have some advise for this? I have a script that runs for months at a time. On one box, I can do this without issue, on another it disconnects after a day. I''ve been trying various solutions, but since it takes a day to test any idea, it''s been very slow going. I''ve tried Issuing a reconnect command, after any ActiveRecord error. Which

...ng at the mysql process list revealed that all of the processes had received the "sleep" command but one of the processes is still working properly. I''ve played with connection timeouts other than to set the timeout in my application''s environment (ActiveRecord::Base.verification_timeout = 14400) as well as the mysql interactive_timeout variable but it seems that all the mongrels should work or they shouldn''t. The fact that 1 out of 4 always works is rather puzzling to me. Trying a ''killall -USR1 mongrel_rails" to turn debug on simply killed the 4 th...

This isnt totally a rails question; I am using ActiveRecord for storing some simple values into a database. My problem; I keep gettign MySQL Errors. On the Win32 machine it was off and on. Now on the linux machine (ubuntu) I can'' t connect at all. I have all the password settings correct. My only thought, I am working with Threads and thought that might cause the issue, but I

Hi! I got a class named EinsatzFilter which I serialized to session. Before saving to session it works afterwards I keep getting the message: "undefined method `to_s'' for #<Person:0x38c6ab8>". "Person" is a from ActiveRecord::Base inherited class. Code: class EinsatzFilter include ApplicationHelper attr_reader :personen, :monat, :projekte, :kunde

...olves the problem until the next time it happens. I have done a lot of reading about this issue online and a number of sources -- including the Mongrel FAQ -- point to being able to fix a ''hanging mongrel'' situation by setting this value in environment.rb: ActiveRecord::Base.verification_timeout = 14400 This make the ActiveRecord timeout value less than the MySQL default of 28800. I have made this change and it doesn''t appear to make a difference. Can anyone advise me on what to try next to diagnose this issue? I''m quickly running out of ideas and I''d appreci...

...olves the problem until the next time it happens. I have done a lot of reading about this issue online and a number of sources -- including the Mongrel FAQ -- point to being able to fix a ''hanging mongrel'' situation by setting this value in environment.rb: ActiveRecord::Base.verification_timeout = 14400 This make the ActiveRecord timeout value less than the MySQL default of 28800. I have made this change and it doesn''t appear to make a difference. Can anyone advise me on what to try next to diagnose this issue? I''m quickly running out of ideas and I''d appreci...

...1.1.5-5) on a ubuntu box with apache2 2.2.12-1ubuntu2.1 I have 4 different apps on the same box and each app has two mongrel instances. After a short period of time ( < 2 hours ) some of the 8 mongrel instances just stop responding. I read the mongrel FAQ and tried to set ActiveRecord::Base.verification_timeout = 14400 (the mysql parameter is set to the default 28800) in myapp/config/environments/ production.rb The problem kept happening. I decided to lower that number, making it 60. No more success. I installed gdb and the ruby macros to make sure i was in the mysql driver while hanging and sure enou...

...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 several hours (28800 minutes most likely) of inactivity. I''ve added "ActiveRecord::Base.verification_timeout = 14400" to the end of my ''config/environment.rb'' file to no avail. I''ve also attempted to set the timeout to a lower value, also to no avail. I''ve switched between Development and Production with no change. I''m not sure where to proceed. I can'...