I've got a reproducable signal 11 death in mysqld using Innobase tables and
range queries (at least reproducable on my machine, Redhat 6.2, mysql
3.23.35).
Here's how it manifests itself: Create a table with at least 32 columns.
Then load a row or two into the table and try to do any query using a range
(>, <, between, in) on the primary key and i get this:
mysql> select * from foo where id > 1 limit 1;
ERROR 2013: Lost connection to MySQL server during query
mysql>
Number of processes running now: 0
010325 22:34:39 mysqld restarted
mysql>
Looking at the error log i get this:
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
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...
Stack range sanity check OK, backtrace follows:
0x4007f552
0x81b1a11
0x81b0cbe
0x81ae75c
0x8118c61
0x810c186
0x810cf83
0x81092d7
0x80ebc50
0x80e9f9c
0x80d00a7
0x80d4073
0x80cf489
0x80ce9b6
Stack trace successful, trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8322640 = select * from foo where id > 1 limit 1
thd->thread_id = 1
Successfully dumped variables, if you ran with --log,
take a look at the details of what thread 1 did to cause the crash.
In some cases of really bad corruption, this value may be invalid
Please use the information above to create a repeatable
test case for the crash, and send it to [EMAIL PROTECTED]
Number of processes running now: 0
010325 22:34:39 mysqld restarted
Innobase: Database was not shut down normally.
Innobase: Starting recovery from log files...
Innobase: Starting log scan based on checkpoint at
Innobase: log sequence number 0 875931369
Innobase: Started
/usr/local/libexec/mysqld: ready for connections
When creating the table, i first encountered this with just a ugly wide
table.. I then tried to create a test table to reproduce this. If you create
a table of 32 int's it doesn't happen, but a single int as the primary id
and then 31 varchar(100)'s does it reliably.. I'm not saying that's a good
schema, but it shouldn't happen regardless.
Let me know if anyone can reproduce this, as it's quite the nuisance...
thanks,
arne
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
