Description:
When try `insert DELAYED...' mysql crush with signal 11
I'am try tar.gz(static and non static) and try compile from source
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=12
max_connections=100
threads_connected=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0xa5a6628
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=0x5a5618, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8192742
0xd04420
0x81cb588
0x81cb588
0x81ebe36
0x81a5ef2
0x81aaf0d
0x81a2b26
0x81a23c3
0x81a1904
0x117bd4
0xa5c4fe
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa614888 = INSERT DELAYED INTO logs2 VALUES (NOW(),'146092','146092','3947','363268',"Accept photo","Photos")
thd->thread_id=1080
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: 0
060719 19:14:12 mysqld restarted
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=12
max_connections=100
threads_connected=13
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x93623c8
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=0x238618, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8192742
0xd82420
0x81cb588
0x81cb588
0x81ebe36
0x81a5ef2
0x81aaf0d
0x81a2b26
0x81a23c3
0x81a1904
0xedebd4
0x72e4fe
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x936d8c8 = INSERT DELAYED INTO logs2 VALUES (NOW(),'146092','146092','-1','363268',"Error! Accept. File not found","Photos")
thd->thread_id=202
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: 0
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=10
max_connections=100
threads_connected=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0xa6e8800
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=0x315618, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8192742
0xfdb420
0x81cb588
0x81cb588
0x81ebe36
0x81a5ef2
0x81aaf0d
0x81a2b26
0x81a23c3
0x81a1904
0xf28bd4
0x46e4fe
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa649070 = INSERT DELAYED INTO logs2 VALUES (NOW(),'146092','146092','-1','363268',"Error! Accept. File not found","Photos")
thd->thread_id=185
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.
How to repeat:
CREATE TABLE `logs2` (
`date` datetime NOT NULL default '0000-00-00 00:00:00',
`logid` int(16) default NULL,
`user1` int(16) default NULL,
`user2` int(16) default NULL,
`objid` int(16) default NULL,
`msg` blob,
`type` varchar(32) default NULL,
KEY `logid` (`logid`),
KEY `user1` (`user1`),
KEY `user2` (`user2`),
KEY `type` (`type`),
KEY `date` (`date`),
KEY `objid` (`objid`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1
mysql> show global variables like '%del%';
+----------------------------+-------+
| Variable_name | Value |
+----------------------------+-------+
| delay_key_write | ON |
| delayed_insert_limit | 100 |
| delayed_insert_timeout | 300 |
| delayed_queue_size | 1000 |
| innodb_thread_sleep_delay | 10000 |
| max_delayed_threads | 20 |
| max_insert_delayed_threads | 20 |
+----------------------------+-------+
