I did up the wait_timeout and that is not the issue, in my.cnf we had
max_user_connections=300 but no gobal max_connections setting.
In my.cnf:
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
old_passwords=1
set-variable=max_connections=300
[mysql.server]
user=mysql
basedir=/var/lib
set-variable = max_user_connections = 300
set-variable = table_cache=1200
set-variable = max_allowed_packet=1M
set-variable = max_connect_errors=999999
set-variable = log-warnings=2
Were waiting for a failure now.
-----Original Message-----
From: Filoo GmbH - Christopher Kunz [mailto:[EMAIL PROTECTED]
Sent: Monday, July 24, 2006 4:35 PM
To: [email protected]
Subject: Re: [vchkpw] vmysql: sql error[3]: Lost connection to MySQL server
during query - once again
Michael Bellears schrieb:
>>> Just how busy is MySQL?
>>>
>>>
>> Not very. The server is kinda big and the "lost connection"
>> is almost instant.
>> The reconnect, though, takes a couple seconds.
>
> Does restarting MySQL "resolve" the problem for a period?
>
>
Not at all. I see the connections coming in, and when they're killed off by
mysql after 5 minutes (our wait_timeout), the issues start again.
Upping wait_timeout is not an option, since the server *can* get very busy
with
lots of other persistent connections.
Regards,
--ck
--
php development | hosting | housing | professional game server hosting
http://www.de-punkt.de [ [EMAIL PROTECTED] ] http://www.stormix.de
Hotline: 07000-3378658 (12 Ct/min) | Fax: 01805-963951172 (12 Ct/min)
"PHP-Sicherheit" - jetzt vorbestellen! http://www.php-sicherheit.de/
