search for: wait_timeout

Hi, I''m lost and my mysql connection as well... I got this error in my production.log: ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL server during query: SET NAMES ''utf8''): Config: Debian Sarge (last updated), Rails 1.1.2, Webrick, mysqld Ver 4.1.11-Debian_4sarge2 for pc-linux-gnu on i386 apache2 with mod_rewrite and webrick as proxy on 8080.

I have an application that creates quite a few threads. I keep getting the "mysql too many connections" error. ActiveRecord does not close the connection once a thread had died out. To make things worse mysql has a wait_timeout variable that would basically kill off these connections for me, but there is a bug and I can not change the value of it. I have tried at least 10 different ways to change the variable and it simply won''t change. It''s defaulted to 8 hours, and I wanted to change it to 4 minute...

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

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)

...= http_client_init_private(&http_set); ? ? ? ? } ? ? ? ? *conn_r = conn; /usr gets changed to ${LOCALBASE} in post-patch:, so we cheat and set xpdf's path to /usr/lib. --- src/plugins/fts/decode2text.sh.orig 2017-10-28 12:21:20 UTC +++ src/plugins/fts/decode2text.sh @@ -79,16 +79,20 @@ wait_timeout() { ?LANG=en_US.UTF-8 ?export LANG ?if [ $fmt = "pdf" ]; then -? /usr/bin/pdftotext $path - 2>/dev/null& +? if [ -x /usr/lib/xpdf/pdftotext ]; then +? ? /usr/lib/xpdf/pdftotext $path - 2>/dev/null& +? else +? ? /usr/local/bin/pdftotext $path - 2>/dev/null& +? fi ? ?wa...

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'

...o. But I have new info and need some help. Basically in my background process I am creating new threads. Each thread get''s it''s own database connection. The problem is that when the thread is finished or killed it doesn''t close the connection. What mysql has is a wait_timeout variable. This is set to 8 hours and max_connections is set to 100. I could easily set max_connections to 500 and wait_timeout to 60 seconds or something. This would solve my problem, but as well all know this is a hack. Is there a way to close the db connection when the thread is finished...

...erver has gone away</b> I looked in the MySql docs and, by default, after 8 hours of inactivity, the Mysql server closes the connection with the client (and it's probably this that causes the error above). So, I know that I can change the <code class="literal"><i>wait_timeout</i> option in MySql but is there a way to specify an unlimited time connection only from Dovecot to MySql? And by the way, what's exactly the purpose of Dovecot's <i>db_client_flags</i> option? Would it be possible to specify the timeout via this option? Thanks for you...

...k_given_p()){ rb_yield(klass); } return INT2NUM(dwWait - WAIT_OBJECT_0 + 1); // signalled } if((dwWait >= WAIT_ABANDONED_0) && (dwWait < WAIT_ABANDONED_0 + len)){ return INT2NUM(-(dwWait - WAIT_ABANDONED_0 + 1)); // an abandoned mutex } if(dwWait == WAIT_TIMEOUT){ return INT2NUM(0); // Timed out } return Qnil; } static VALUE ipc_wait_any(int argc, VALUE* argv, VALUE klass) { VALUE rbObject, rbTimeout; DWORD dwTimeout = INFINITE; rb_scan_args(argc,argv,"11",&rbObject,&rbTimeout); if(TYPE(rbObject)!=T_ARRAY) {...

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

Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info at domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info at

...in: waiting for stop completed event\n")); + } + // Stop the service. SetTheServiceStatus(SERVICE_STOPPED, NO_ERROR, 0, 0); } @@ -97,10 +91,10 @@ return result; } -VALUE Ruby_Service_Ctrl() +VALUE Ruby_Service_Ctrl(VALUE self) { while (WaitForSingleObject(hStopEvent,0) == WAIT_TIMEOUT) - { + { __try { EnterCriticalSection(&csControlCode); @@ -108,20 +102,22 @@ // Check to see if anything interesting has been signaled if (waiting_control_code != IDLE_CONTROL_CODE) { - // if there is a code, create a rub...

..._master_enabled=1 ;rpl_semi_sync_master_timeout=10 ;rpl_semi_sync_slave_enabled=1 ;performance_schema query_cache_size = 8MB innodb_buffer_pool_size = 199M 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 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-r...

...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.0) mongrel (1.0.1) mongrel_cluster (1.0.2) Apache/2.2.4 (Unix) Mongrel Cluster Config: port: "8000" envir...

We also spotted these sql connections getting aborted, upon upgrading MySQL from 5.6 to 5.7. (Going back to 5.6 we don't see them!) Turning on mysql general query logging we can see it is Dovecot's mysql connections that inquire about or update quota usage in particular: *** /logs//mysql.log *** 2019-10-30T10:52:22.624690-07:00 2 Connect dovecot at localhost on npomail using

...ut=10 > ;rpl_semi_sync_slave_enabled=1 > ;performance_schema > query_cache_size = 8MB > innodb_buffer_pool_size = 199M > 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 > 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...

...e hosts defined in my auth userdb 'connect'. This is Debian Lenny 32-bit and I'm seeing the same thing with 2.0.16 on Debian Squeeze 64-bit. E.g.: Jan 12 20:30:33 auth-worker: Error: mysql: Query failed, retrying: MySQL server has gone away Our mail mysql servers are busy enough that wait_timeout is set to a whopping 30 seconds. On my regular boxes, I see a good deal of these in the logs. I've been doing a lot of mucking with doveadm/dsync (working on maildir->mdbox migration finally, yay!) on test boxes (same dovecot package & version) and when I get this error, despite the log...

...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.0) mongrel (1.0.1) mongrel_cluster (1.0.2) Apache/2.2.4 (Unix) Mongrel Cluster Config: port: "8000" envir...

...; (Got an error reading communication packets) > > 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