I got this error,
You seem to be running 32-bit Linux and have 308 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and built the binary
yourself, LinuxThreads is quite likely to steal a part of the global
heap for
the thread stack. Please read http://www.mysql.com/doc/en/Linux.html
What is the meaning?
I use i386.rpm from mysql.com with 4 Gbytes RAM (dedicated for MySQL)
============= cut here ==================
060125 15:17:01 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: '5.0.15-max' socket: '/var/lib/mysql/mysql.sock' port: 3306
MySQL Community Edition - Experimental (GPL)
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=402653184
read_buffer_size=12578816
max_used_connections=489
max_connections=910
threads_connected=308
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 1782208 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
You seem to be running 32-bit Linux and have 308 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and built the binary
yourself, LinuxThreads is quite likely to steal a part of the global
heap for
the thread stack. Please read http://www.mysql.com/doc/en/Linux.html
thd=0xb111c5c8
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=0x8e79defc, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x816add7
0x4004a618
0x83bf301
0x8348ad1
0x83463ff
0x83394df
0x8319677
0x831bb9b
0x820cd08
0x820ce05
0x81bb036
0x81ba240
0x81b9f30
0x81aae65
0x81ac129
0x81a8b61
0x817d030
0x81837aa
0x817b5e3
0x817aeb4
0x817a3d4
0x400452b6
0x420de407
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 trac
e. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xae81ea78 is invalid pointer
thd->thread_id=23942
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.
pure virtual method called
pure virtual method called
Fatal signal 6 while backtracing
pure virtual method called
Number of processes running now: 0
060126 19:03:02 mysqld restarted
060126 19:03:02 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060126 19:03:03 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 49 2685434817.
InnoDB: Doing recovery: scanned up to log sequence number 49 2690677248
InnoDB: Doing recovery: scanned up to log sequence number 49 2695920128
InnoDB: Doing recovery: scanned up to log sequence number 49 2701163008
InnoDB: Doing recovery: scanned up to log sequence number 49 2706405888
InnoDB: Doing recovery: scanned up to log sequence number 49 2711648768
InnoDB: Doing recovery: scanned up to log sequence number 49 2716891648
InnoDB: Doing recovery: scanned up to log sequence number 49 2722134528
InnoDB: Doing recovery: scanned up to log sequence number 49 2727377408
InnoDB: Doing recovery: scanned up to log sequence number 49 2732620288
InnoDB: Doing recovery: scanned up to log sequence number 49 2737863168
InnoDB: Doing recovery: scanned up to log sequence number 49 2743106048
InnoDB: Doing recovery: scanned up to log sequence number 49 2748348928
InnoDB: Doing recovery: scanned up to log sequence number 49 2753591808
InnoDB: Doing recovery: scanned up to log sequence number 49 2758834688
InnoDB: Doing recovery: scanned up to log sequence number 49 2764077568
InnoDB: Doing recovery: scanned up to log sequence number 49 2769320448
InnoDB: Doing recovery: scanned up to log sequence number 49 2774563328
============= cut here ==================
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
