MySQL Bugs: #64265: MySQL crashing itself on long semaphore wait

Bug #64265	MySQL crashing itself on long semaphore wait
Submitted:	8 Feb 2012 13:56	Modified:	28 Dec 2017 15:31
Reporter:	Evan Schmidt	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.1.48, 5.1.62	OS:	Linux (CentOS release 5.4 (Final))
Assigned to:		CPU Architecture:	Any
Tags:	Crash; Error: semaphore wait has lasted > 600 seconds

Description:
MySQL crashed itself with the following from the error log:

InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
120208  5:49:49  InnoDB: Assertion failure in thread 1231649088 in file srv/srv0srv.c line 2293
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120208  5:49:49 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=67108864
read_buffer_size=8388608
max_used_connections=402
max_threads=1024
threads_connected=163

How to repeat:
Unknown

Suggested fix:
Unknown

Please, check if the same problem still happens with a newer version, 5.1.61.

error log showing activity preceding the crash

Attachment: prod-asap-db1.err.just-before-crash (text/plain), 64.47 KiB.

error log with details of activity not including the last INNODB MONITOR OUTPUT

Attachment: prod-asap-db1.err.early-info.gz (application/x-gzip-compressed, text), 215.55 KiB.

Fixed crshing to crashing

Thank you for the additional information. But what about testing with 5.1.61? We do not fix bugs in older versions, so you have to prove that the problem is still repeatable with recent one.

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".

Upgraded to 5.1.62 on 2012-04-14.

Database Instance has crashed three times since then (04-17, 04-18, 04-19).

I am attaching relevant sections of the error log as three seperate files.

Last crash happens when 2 same ALTER TABLE statements are executed on the `attribute_capacities` table. Please, send the output of:

show create table `attribute_capacities`\G
show table status like 'attribute_capacities';

See bug #59047 for possible workarounds. Send your my.cnf file content also.

May be a duplicate of 73890

5.1 isn't more supported (EOL) please check with major version i.e: 5.7. Thanks.

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".