Re: MySQL goes away?
On Sun, 31 Aug 2008 04:37:04 + Tzafrir Cohen [EMAIL PROTECTED] wrote: On Sat, Aug 30, 2008 at 09:53:42PM +0200, Rico Secada wrote: On Sat, 30 Aug 2008 09:14:37 -0400 Miles Fidelman [EMAIL PROTECTED] wrote: Rico Secada wrote: I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? well, just a guess, but it looks like your mysql daemon has died take a look at your mysql log files, and then restart the daemon - see what happens That's the problem mysql isn't dead. How can you tell that? Please post here the output of the relevant shell commands you tested with. Tzafrir you can tell that in a number of ways, here are two: # ps aux | grep mysql root 2384 0.0 0.0 10108 1516 ?SAug21 0:00 /bin/sh /usr/bin/mysqld_safe mysql 2421 0.0 0.3 147496 24028 ?Sl Aug21 0:01 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock root 2422 0.0 0.0 2636 532 ?SAug21 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld # /etc/init.d/mysql status /usr/bin/mysqladmin Ver 8.41 Distrib 5.0.32, for pc-linux-gnu on x86_64 Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 5.0.32-Debian_7etch6-log Protocol version10 Connection Localhost via UNIX socket UNIX socket /var/run/mysqld/mysqld.sock Uptime: 9 days 21 hours 4 min 57 sec -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: MySQL goes away?
On Saturday 30 August 2008 12:26:06 Rico Secada wrote: Hi, I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? Best regards. Have a look at the following: http://dev.mysql.com/doc/refman/5.0/en/gone-away.html I have had this issue in the past, although I can't remember what /i did to fix it. You could check the following: - firewall rules - restart mysql and see if it still happens - check how many connections you have: - sudo netstat -tapn | grep mysql - mysqladmin processlist You might have too many clients connected but iirc that would be a different error... HTH -- Thank you, Clifford W. Hansen PHP Developer / Linux Administrator (Cell)+27 82 883 8677 (Fax) +27 86 503 0634 (E-Mail) [EMAIL PROTECTED] (MSN) [EMAIL PROTECTED] (GPG) 0x936D6C19 We have seen strange things today! () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: This is a digitally signed message part.
Re: MySQL goes away?
Rico Secada wrote: Hi, I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? Your program leaves the connection open, and the connection times out. It's a bit like this: mysql show variables like 'wait%'; +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 28800 | +---+---+ 1 row in set (0.00 sec) mysql set wait_timeout = 60; Query OK, 0 rows affected (0.00 sec) mysql show variables like 'wait%'; +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 60| +---+---+ 1 row in set (0.00 sec) and then, after more than a minute: mysql show variables like 'wait%'; ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id:35716 Current database: *** NONE *** +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 28800 | +---+---+ 1 row in set (0.00 sec) Close your connections or set your wait_timeout higher. --kj -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: MySQL goes away?
On Sun, 31 Aug 2008 16:05:39 +0100 kj [EMAIL PROTECTED] wrote: Rico Secada wrote: Hi, I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? Your program leaves the connection open, and the connection times out. It's a bit like this: mysql show variables like 'wait%'; +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 28800 | +---+---+ 1 row in set (0.00 sec) mysql set wait_timeout = 60; Query OK, 0 rows affected (0.00 sec) mysql show variables like 'wait%'; +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 60| +---+---+ 1 row in set (0.00 sec) and then, after more than a minute: mysql show variables like 'wait%'; ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id:35716 Current database: *** NONE *** +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 28800 | +---+---+ 1 row in set (0.00 sec) Close your connections or set your wait_timeout higher. Thanks kj, makes sense! --kj -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
MySQL goes away?
Hi, I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? Best regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: MySQL goes away?
Rico Secada wrote: I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? well, just a guess, but it looks like your mysql daemon has died take a look at your mysql log files, and then restart the daemon - see what happens -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: MySQL goes away?
On Sat, 30 Aug 2008 09:14:37 -0400 Miles Fidelman [EMAIL PROTECTED] wrote: Rico Secada wrote: I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? well, just a guess, but it looks like your mysql daemon has died take a look at your mysql log files, and then restart the daemon - see what happens That's the problem mysql isn't dead. -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: MySQL goes away?
On Sat, Aug 30, 2008 at 09:53:42PM +0200, Rico Secada wrote: On Sat, 30 Aug 2008 09:14:37 -0400 Miles Fidelman [EMAIL PROTECTED] wrote: Rico Secada wrote: I keep getting this from Amavis about MySQL: **Unmatched Entries** NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN27 line 3.: 2 Time(s) NOTICE: reconnecting in response to: err=2006, S1000, DBD::mysql::st execute failed: MySQL server has gone away at (eval 40) line 153, GEN32 line 3.: 2 Time(s) Does anyone know what exactly this means? well, just a guess, but it looks like your mysql daemon has died take a look at your mysql log files, and then restart the daemon - see what happens That's the problem mysql isn't dead. How can you tell that? Please post here the output of the relevant shell commands you tested with. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
