MySQL Bugs: #25195: mysqldump occured Error

Bug #25195	mysqldump occured Error
Submitted:	20 Dec 2006 3:56	Modified:	20 Jan 2007 9:05
Reporter:	EUN KEYONG YUN	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Backup	Severity:	S2 (Serious)
Version:	4.1.12-standard-log	OS:	Linux (Red Hat Enterprise Linux AS rele)
Assigned to:		CPU Architecture:	Any

Description:
I use mysqldump program as mysql's backup. 
I dump Whole Database's tables, "Each Other" continuously in shell script.
There are a lot of datas and a lot of tables. 
While that script program was dumpping tables, MySQLdump occured error.
"/data/server/mysql/bin/mysqldump: /data/server/mysql/bin/mysqldump: Couldn't execute 'SET SESSION TRANSACTION ISOLATION LEVEL REPEATABLE READ': MySQL server has gone away (2006)"
"/data/server/mysql/bin/mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) when trying to connect"

After Then, we couldn't connect MySQL Server.
MySQL Server didn't shutdown.

I think that is the connection problem
What is the problem?

YUN

How to repeat:
You can dump Whole Database's tables, "Each Other" continuously in shell script.

Thank you for a problem report. Please, send your my.cnf content and corresponding part of MySQL server's error log.

my.cnf file

Attachment: my.cnf (application/octet-stream, text), 4.83 KiB.

There is no error code in error log

If there is nothing in the error log then the server
process was probably killed by the kernels OutOfMemory
kill mechanism.

Can you find any mysql related OOM kill log entries
in the machines syslog?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".