Hi all,
I woke up this morning to find that our main database had stopped
responding so I jumped on to see what was going on. MySQL was no
longer running and the error log contained lots of...
<---
InnoDB: Warning: a long semaphore wait:
--Thread 39439068816 has waited at trx0trx.c line 715 for 639.00
seconds the semaphore:
Mutex at 0x809c002a8 created file srv0srv.c line 872, lock var 1
waiters flag 1
--->
...and ended with the following...
<---
InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic
info:
InnoDB: Pending preads 0, pwrites 0
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.
080710 4:34:17InnoDB: Assertion failure in thread 34382814000 in file
srv0srv.c line 2093
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
080710 4:34:17 - mysqld got signal 11;
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=33554432
read_buffer_size=2093056
max_used_connections=502
max_connections=501
threads_connected=501
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 5161000 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
080710 04:34:18 mysqld ended
--->
I don't really have any idea what it was doing at that time, but it
could be related to the mysqldump that runs at 12:45pm but that's
usually done within an hour.
Upon restart it reported that "InnoDB was not shut down normally" and
did it's crash recovery thing without any issues.
The server is running FreeBSD 7.0-RELEASE #0 amd64 with an unchanged
kernel and mysql-server-5.0.45_1 installed from ports.
If anyone has any idea what caused this or steps I should take to
prevent it happening again I'd be eternally grateful.
Thanks.
-Stut
--
http://stut.net/mysql
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
