Bug #56741 | mysqld Crashes with Signal 11 | ||
---|---|---|---|
Submitted: | 13 Sep 2010 6:08 | Modified: | 19 Dec 2010 19:28 |
Reporter: | Siddeshwar Borkar | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S2 (Serious) |
Version: | mysql-5.0.89-linux-i686 | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[13 Sep 2010 6:08]
Siddeshwar Borkar
[13 Sep 2010 6:11]
Siddeshwar Borkar
Error.log
Attachment: MySQL_StackDump (application/octet-stream, text), 1.48 KiB.
[13 Sep 2010 6:12]
Siddeshwar Borkar
MySQL_StackDump
Attachment: MySQL_StackDump (application/octet-stream, text), 1.48 KiB.
[13 Sep 2010 6:18]
Siddeshwar Borkar
my.cnf
Attachment: my.cnf (application/octet-stream, text), 9.93 KiB.
[13 Sep 2010 6:20]
Valeriy Kravchuk
Based on stack trace this looks like a duplicate of bug #51650. Please, check.
[13 Oct 2010 23: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".
[3 Nov 2010 13:14]
Siddeshwar Borkar
Hi, The DB seemed stable for many days and we did not update this support case. But the problem has reappeared. We did checked Bug #51650 but were not able to figure out the exact changes that need to be made. Please guide us on this. Regards, Siddeshwar Borkar
[19 Nov 2010 19:28]
Sveta Smirnova
Thank you for the feedback. You need to update to latest 5.1 version which is currently 5.1.52
[20 Dec 2010 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".