Bug #40968 | Server hang without any error messages | ||
---|---|---|---|
Submitted: | 24 Nov 2008 8:49 | Modified: | 28 Feb 2009 0:31 |
Reporter: | Kenneth Lee | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.1.28rc, 5.1.30 | OS: | Linux (2.6.18-92.el5 x86_64) |
Assigned to: | CPU Architecture: | Any |
[24 Nov 2008 8:49]
Kenneth Lee
[24 Nov 2008 14:31]
Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 5.1.29. In case of the same problem, please, send the entire results of SHOW INNODB STATUS several minutes after hang.
[8 Dec 2008 7:51]
Kenneth Lee
I updated to version 5.1.30, but still hanging occurs. Luckily frequency of hanging lowered 2-3 times per week in comparison with 7~10 times per week. I attached result of SHOW INNODB STATUS.
[8 Dec 2008 22:49]
Mikhail Izioumtchenko
doesn't necessarily look like Innodb bug. Could you get the process stack of the hanging mysqld, with pstack or gdb?
[30 Jan 2009 0:00]
Bugs System
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".
[30 Jan 2009 0:31]
MySQL Verification Team
Still feedback is needed.
[4 Feb 2009 20:33]
Peter Garmaz
I am also experiencing this issue while running 5.1.30(GA) on Debian Etch. I'm running a 4 server Mulit-Master set replication setup with 1 extra machine as a slave for back up purposes. All 5 servers are running 2.6.18-6 kernels (some 32 bit, some 64 bit) and are running 5.1.30(GA). The problem has only demonstrated itself only on the 4 master servers. The frequency of the issue is intermittent at best. I know my replication cycle works normally as I was running 5.0 for some time previous to upgrading to 5.1 about week. The only difference I have in regards to Kenneth's original bug report is that we are are running about 80 or so MyISAM tables and only 2 innodb tables. The next time one of my servers demonstrates the problem (which is likely to be today) I shall get a pstack dump and attach it. p.
[1 Mar 2009 0:00]
Bugs System
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".
[18 Mar 2009 9:10]
Kelvin Liang
I get a similar issue like this while running with 5.1.32(GA). I can connect with the mysql client but can't query data from table. No error messages were dropped to the logfiles. After restarting, everything works fine till the next hang.
[18 Mar 2009 15:35]
Mikhail Izioumtchenko
we can't say it's an InnoDB bug until we have some evidence. It could be bug#41163, for example