Below follows what our DBA did to solve the problem. Also, an article at http://www.webyog.com/blog/2009/09/02/“mysql-server-has-gone-away”-part-2-session-timeout/ explains what MySQL server settings matter. Marina On 26/01/2011 15:32, Karen Ambrose wrote:
Hi Marina,
Here is the solution to the problem.
Checked the global.wait_timeout and session.wait_timeout parameters:
mysql> select @@global.wait_timeout; +-----------------------+ | @@global.wait_timeout | +-----------------------+ | 30 | +-----------------------+ 1 row in set (0.00 sec)
mysql> select @@session.wait_timeout; +------------------------+ | @@session.wait_timeout | +------------------------+ | 28800 | +------------------------+ 1 row in set (0.00 sec)
Once the global wait_timeout was set to 28800 then this worked.
mysql> select @@global.wait_timeout; +-----------------------+ | @@global.wait_timeout | +-----------------------+ | 28800 | +-----------------------+ 1 row in set (0.00 sec)
Regards
Karen
__________________________________________
Karen Ambrose (kva@sanger.ac.uk) Senior Database Administrator Team 106: Database Administration Team
-- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.