Bug #21245 MySQL restarts all of a sudden (errno 137)
Submitted: 24 Jul 2006 6:46 Modified: 24 Jul 2006 11:39
Reporter: Peter Romianowski Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.22-standard-log OS:Linux (SuSE Linux 10.1)
Assigned to: CPU Architecture:Any

[24 Jul 2006 6:46] Peter Romianowski
Description:
Hi,

this morning our heavy loaded mysql restarted all of a sudden. The last log lines look really strange (never seen anything like this and did not find anything using my favourite search engine):

060723  1:36:43 [ERROR] Failed to open log (file '/var/log/mysql/mysql-bin.000276', errno 2)
060724  5:24:28 [Warning] Warning: Enabling keys got errno 137, retrying

Number of processes running now: 0
060724 07:39:32  mysqld restarted

The log file "mysql-bin.000276" is indeed not available. I did a "reset master" the day before and the last log file is "mysql-bin.000005" which looks quite normal. The application using the mysql server worked until around 07:23. The server restarted a few days before whithout any notice too. The only message in the log was a "mysql started".

Before the mysql-server restarted today the load and swap usage started to increase dramatically. Nearly all statements got stuck at the same time. It happened all of a sudden - no heavy statement or anything has been sent to the server.

Please help - this is a serious problem for us! 

How to repeat:
I don't know how to repeat this. Sorry!
[24 Jul 2006 11:39] Valeriy Kravchuk
We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug. At least, without a repeatable test case that leads to this error 137, we can not determine if it is a bug that leads to your situation.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/.