Vbb crash my MYSQL Servers....

[yasunari]

My servers admin have report that my Vbb make the MYSQL crash and make the servers down...

I have get this message:
1: mysql error: Lost connection to MySQL server during query
2: mysql error: MySQL server has gone away
3: mysql error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

after this 3 error, my web down ... i got total around 157 mail and servers goes down..
I have pconnect OFF and no-cache headers ON.

[George L]

http://www.mysql.com/doc/G/o/Gone_away.html
http://www.mysql.com/doc/C/o/Common_errors.html
http://www.mysql.com/doc/S/e/Server_parameters.html
http://www.mysql.com/doc/O/p/Option_files.html
http://www.mysql.com/doc/S/H/SHOW_VARIABLES.html

The most common reason for the MySQL server has gone away error

1. Is that the server timed out and closed the connection. By default, the server closes the connection after 8 hours or 28800 seconds if nothing has happened. You can change the time limit by setting the wait_timeout variable when you start mysqld via your server's /etc/my.cnf as well.

2. Another common reason to receive the MySQL server has gone away error is because you have issued a ``close'' on your MySQL connection and then tried to run a query on the closed connection. You can check that the MySQL hasn't died by executing mysqladmin version and examining the uptime.

i.e. to check mysql uptime, in shell as root user type:

mysqladmin -u root -p version

3. You can also get these errors if you send a query to the server that is incorrect or too large. If mysqld gets a packet that is too large or out of order, it assumes that something has gone wrong with the client and closes the connection. If you need big queries (for example, if you are working with big BLOB columns), you can increase the query limit by starting mysqld with the -O max_allowed_packet=# option (default 1M) or via max_allowed_packet variable in your /etc/my.cnf file and restarting mysql after you edited your /etc/my.cnf file. The extra memory is allocated on demand, so mysqld will use more memory only when you issue a big query or when mysqld must return a big result row

4. or simply your host restarted mysql.. i'd contact your web host

seems like your host's mysql server is either not configured properly to handle the load or it's overloaded already

[yasunari]

My servers admin have check the log today:

the result I get in /var/log/message
is
May 9 18:31:05 hkspace kernel: Out of Memory: Killed process 25367 (mysqld).
May 9 18:31:36 hkspace kernel: Out of Memory: Killed process 3283 (mysqld).
May 9 18:37:14 hkspace kernel: Out of Memory: Killed process 3503 (mysqld).
May 9 18:38:15 hkspace kernel: Out of Memory: Killed process 3658 (mysqld).
May 9 18:38:28 hkspace kernel: Out of Memory: Killed process 3680 (mysqld).
May 9 18:38:39 hkspace kernel: Out of Memory: Killed process 3681 (mysqld).
May 9 18:38:40 hkspace kernel: Out of Memory: Killed process 3685 (mysqld).

then the server die.

[George L]

what are the server specs ? cpu ? memory ? hdd? and how many sites are sharing the server ?

[yasunari]

Redhat linux
CPU: 766 * 2CPU
Memory: 768MB
sites: around 5-10

Only my site is using MYSQL..

[George L]

Originally posted by yasunari
Redhat linux
CPU: 766 * 2CPU
Memory: 768MB
sites: around 5-10

Only my site is using MYSQL..

what version of redhat linux and what kernel version are you using ?

[yasunari]

redhat 7.2
kernel: 2.4.2-2smp