search for: interactive_timeout

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

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 or stale connections. What I have done in the past was optimize mysql with the following...

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

Is anyone else using Dovecot (2.3.8) with MySQL (5.7) seeing a lot of these in MySQL logs? 2019-10-28T11:08:20.384428+02:00 58378 [Note] Aborted connection 58378 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication packets) 2019-10-28T11:10:09.821171+02:00 58420 [Note] Aborted connection 58420 to db: 'vmail' user: 'vmail'

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)

...ng 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_timeout has elapsed, active record will verify...

...ns. 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.verification_timeout = 14400" Thanks and regards veeraa -------------- next part -----------...

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

...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 threads running mongrel. So now I''m running t...

...o diagnose this issue? I''m quickly running out of ideas and I''d appreciate a bit of help! Here are the vitals from our Ubuntu 6.0.6 server: MySQL Ver 14.12 Distrib 5.0.22, for pc-linux-gnu (x86_64) using readline 5.1 connect_timeout 5 interactive_timeout 28800 max_connect_errors 10 max_connections 100 max_user_connections 0 wait_timeout 28800 ruby 1.8.6 (2007-03-13 patchlevel 0) [x86_64-linux] cgi_multipart_eof_fix (2.2) fastthread (1...

...o diagnose this issue? I''m quickly running out of ideas and I''d appreciate a bit of help! Here are the vitals from our Ubuntu 6.0.6 server: MySQL Ver 14.12 Distrib 5.0.22, for pc-linux-gnu (x86_64) using readline 5.1 connect_timeout 5 interactive_timeout 28800 max_connect_errors 10 max_connections 100 max_user_connections 0 wait_timeout 28800 ruby 1.8.6 (2007-03-13 patchlevel 0) [x86_64-linux] cgi_multipart_eof_fix (2.2) fastthread (1...

...> > They've plagued my logs for as long as I can remember. Is Dovecot not closing connections to the database properly or something similar? is it possible MySQL closed inactive connections? SHOW VARIABLES LIKE '%timeout%'; mysqlx_wait_timeout = 3600 wait_timeout = 3600 mysqlx_interactive_timeout = 3600 interactive_timeout = 3600 Gerald

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 several hours (28800 minutes most likely) of inactivity. I&...

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''

Hi guys, I''ve been running mongrel for a while now with Ruby 1.8.4, and last week upgraded to 1.8.6. Since upgrading, each morning when I wake up there''s a big problem: 1. Accessing the site returns a "500 Internal Server Error" 2. All the mongrel_rails processes are still running, but none of them are active (when I run top) 3. Lighttpd and pound are still

...t only the server (but not clients) should see # # See the examples of server my.cnf files in /usr/share/mysql/ # # this is read by the standalone daemon and embedded servers [server] # this is only for the mysqld standalone daemon [mysqld] #wait_timeout=28800 #interactive_timeout = 28800 max_allowed_packet=512M #General Query Log general_log_file = /var/log/mysql/mysql_query.log general_log = 1 #Error Log log_error = /var/log/mysql/mysql_error.log #Slow Query Log slow_query_log = 1 slow_query_l...

...ls, calls were going through properly but at around 200-250 calls, mysql (connect ...) statement was taking at least 5-10 sec to connect to the database. I optimized all possible parameters in my.cnf: max_connection=1000 wait_timeout=60 query_cache_type=1 query_cache_limit=4M query_cache_size=512M interactive_timeout=120 connect_timeout=80 table_cache=1024 thread_concurrency=8 long_query_time=10 tmp_table_size=64M join_buffer_size=1M thread_cache_size=200 key_buffer=32M table_cache=1024 sort_buffer_size=2M read_buffer_size=2M read_rnd_buffer_size=4M And I am running on asterisk 1.4.22.1, Quadcore processor 2.4...

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

...default MySQL Conf Detail: ... [mysqld3] lower_case_table_names=1 user=mysql port = 3308 socket = /usr/local/mysql/sock/mysql3.sock pid-file=/usr/local/mysql/sock/mysql3.pid datadir=/data/mysqldata3/mydata tmpdir =/data/mysqldata3/tmpdir skip-locking skip-name-resolve back_log=100 interactive_timeout=172800 default-storage-engine = INNODB default-character-set = utf8 max_connections = 500 max_connect_errors=100000 max_allowed_packet = 4M max_heap_table_size = 1024M max_length_for_sort_data = 4096 net_buffer_length = 8K sort_buffer_size = 8M join_buffer_size = 16M #if lock memory #memlock...

...s=/var/log/mysql/mysql_slow_log wait_timeout = 86400 [mysqld_safe] general_log_file=/var/log/mysql/mysql.log general_log=1 log-error=/var/log/mysql/mysql_error_log log-slow-queries=/var/log/mysql/mysql_slow_log pid-file=/var/run/mysqld/mysqld.pid innodb_buffer_pool_size = 199M wait_timeout = 28800 interactive_timeout = 28800 master-connect-retry=60 So my first question is, why is SSL not enabled in either database? I restarted the service on both machines before taking a look at the variables. The next problem I'm having is that I can't seem to get the replication user to connect. I had to use an acco...