Hi,
MySQL 4.0.16 running on Red Hat Linux release 8.0 with 4 Intel XEON 2.40 GHz with InnoDB tables.
This is the stack trace :
0x81077c6 handle_segfault + 474 0x4002a929 _end + 935891041 0x8272ff8 sync_array_print_long_waits + 580 0x81a7328 srv_error_monitor_thread + 96 0x40024ada _end + 935866898 0x402868c7 _end + 938364927
Error message from log :
InnoDB: Warning: a long semaphore wait:
--Thread 294923 has waited at ../../innobase/include/btr0btr.ic line 28 for 625.00 seconds the semaphore:
X-lock on RW-latch at 40cb26e4 created in file buf0buf.c line 444
a writer (thread id 294923) has reserved it in mode exclusive
number of readers 0, waiters flag 1
Last time read locked in file btr0sea.c line 753
Last time write locked in file buf0buf.c line 1404
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
040812 23:17:29 InnoDB: Assertion failure in thread 98311 in file sync0arr.c line 934
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
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=8388600
read_buffer_size=131072
max_used_connections=53
max_connections=200
threads_connected=17
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 443390 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=0xbedff518, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81077c6
0x4002a929
0x8272ff8
0x81a7328
0x40024ada
0x402868c7
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/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.
Number of processes running now: 2
mysqld process hanging, pid 810 - killed
mysqld process hanging, pid 810 - killed
040812 23:17:29 mysqld restarted
040812 23:17:29 Can't start server: Bind on TCP/IP port: Address already in use
040812 23:17:29 Do you already have another mysqld server running on port: 3306 ?
040812 23:17:29 Aborting
040812 23:17:29 /usr/kasenna/mysql/bin/mysqld: Shutdown Complete
040812 23:17:29 mysqld ended
040816 13:55:44 mysqld started 040816 13:55:44 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 252191979 InnoDB: Doing recovery: scanned up to log sequence number 0 252191979 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 379596032 InnoDB: Starting rollback of uncommitted transactions InnoDB: Rolling back trx with id 0 379591339, 1 rows to undo InnoDB: Rolling back of trx id 0 379591339 completed InnoDB: Rollback of uncommitted transactions completed 040816 13:55:44 InnoDB: Flushing modified pages from the buffer pool... 040816 13:55:44 InnoDB: Started /usr/kasenna/mysql/bin/mysqld: ready for connections. Version: '4.0.16' socket: '/usr/kasenna/mysql/tmp/mysql.sock' port: 3306
Any insight would be most appreciated.
datta Kasenna Inc,
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
