One of our servers which is configured primarily for InnoDB has crashed
in the same fashion three times in the past 48 hours. I've been going
over the error log, and I would like to know if anyone else has seen
similar errors, or can give me some pointers to work out this problem.
Here are the server's settings...
Dual Xeon 2.8 4G RAM, RAID 5 disks
Linux 2.4.20-6smp
MySQL-server-4.1.14-0.glibc23 (RPM)
----------------------------
my.cnf, edited for relevance
----------------------------
skip-locking
max_allowed_packet = 1M
sort_buffer_size = 2M
read_buffer_size = 2M
myisam_sort_buffer_size = 64M
key_buffer_size = 8M # used only for MyISAM
thread_concurrency = 4 # was 8
thread_cache = 8
skip-name-resolve
max_allowed_packet = 8M
query_cache_size = 32M
query_cache_limit = 1M
table_cache = 512
innodb_log_buffer_size = 16M
innodb_log_file_size = 128M
innodb_log_files_in_group = 3
innodb_additional_mem_pool_size = 128M
innodb_buffer_pool_size = 1G
innodb_flush_log_at_trx_commit = 0
innodb_lock_wait_timeout = 30
-----------------------------
Within the InnoDB Monitor output, just before the crash, I see roughly
200 transactions in "waiting", and exactly 8 that look like this
---TRANSACTION 0 1856439353, ACTIVE 913 sec, process no 25698, OS thread
id 2448796736 inserting, thread declared inside InnoDB 410
mysql tables in use 1, locked 1
1 lock struct(s), heap size 320, undo log entries 592
MySQL thread id 1036, query id 368385 192.168.1.37 webserver update
INSERT INTO emails_history_30_18 ....
There is also this message in there
Main thread process no. 25698, id 2434898496, state: doing insert buffer
merge
Then, I get this long message in the .err file:
------------------------------
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.
051005 6:54:17InnoDB: Assertion failure in thread 2426510016 in file
srv0srv.c line 1893
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/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 2401344576 stopped in file ibuf0ibuf.c line 1335
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.
InnoDB: Thread 2434898496 stopped in file ../include/sync0sync.ic line 111
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=8388608
read_buffer_size=2093056
max_used_connections=301
max_connections=300
threads_connected=297
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 1235789 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x90a1936c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8125d30
0x40049568
(nil)
0x420de1b7
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and
follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
-------------------------------
Any one have a suggestion? I've already tried running "CHECK TABLE
emails_history_30_18 EXTENDED", that came back saying everything was fine.
While I was writing this email, the server has crashed two more times in
this same way.
Any help would be appreciated!
Thanks in advance,
Devananda vdv
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
