Bug #42587 mysqld got signal 11 on openSUSE 10.3 (X86-64)
Submitted: 4 Feb 2009 9:26 Modified: 4 Feb 2009 15:47
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: General Severity:S2 (Serious)
Version:5.0.67 OS:Linux (openSUSE 10.3 (X86-64))
Assigned to: CPU Architecture:Any

[4 Feb 2009 9:26] [ name withheld ]
Description:
Hello,

during the query "SELECT * FROM jos_shoutbox WHERE id > 530 ORDER BY id DESC;"
I get always:
090204 10:10:15 - 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=8384512
read_buffer_size=131072
max_used_connections=15
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225787 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x7ffb900008c0
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=0x41cee078, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
Stack trace seems successful - bottom reached
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 0x1bdd290 = SELECT * FROM jos_shoutbox WHERE id > 530 ORDER BY id DESC LIMIT 0, 10
thd->thread_id=283
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
090204 10:10:15  mysqld restarted
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090204 10:10:15  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...
090204 10:10:17  InnoDB: Started; log sequence number 0 55848412
090204 10:10:17 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.67'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
-----------------------------------------------------
I have the problem on three servers with opensuse 10.3, it doesn´t matter whether I use the opensuse-mysql-package or if I install mysql manually.
The hardware cannot be the problem, too.

The most other queries are working, e.g.:
SELECT * FROM jos_shoutbox WHERE id > 530;
SELECT * FROM jos_shoutbox WHERE id > 530 ORDER BY url DESC;
SELECT * FROM jos_shoutbox WHERE id > 530 ORDER BY id;

So there must be something special with "ORDER BY id DESC"

How to repeat:
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;DROP TABLE IF EXISTS `jos_shoutbox`;
SET @saved_cs_client     = @@character_set_client;
SET character_set_client = utf8;
CREATE TABLE `jos_shoutbox` (
  `id` int(11) NOT NULL auto_increment,
  `time` int(11) NOT NULL default '0',
  `name` varchar(25) NOT NULL default '',
  `text` text NOT NULL,
  `url` varchar(225) NOT NULL default '',
  `ip` varchar(255) NOT NULL default '',
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM AUTO_INCREMENT=531 DEFAULT CHARSET=utf8;
SET character_set_client = @saved_cs_client;
/*!40000 ALTER TABLE `jos_shoutbox` ENABLE KEYS */;
UNLOCK TABLES;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
[4 Feb 2009 9:36] Sveta Smirnova
Thank you for the report.

I can not repeat described behavior.

Please provide your configuration file and indicate accurate version of MySQL package you run (file name).
[4 Feb 2009 9:43] [ name withheld ]
At the moment I use this package:
http://dev.mysql.com/get/Downloads/MySQL-5.0/mysql-5.0.67-linux-x86_64-glibc23.tar.gz/from...

My my.cnf:
[mysqld]
set-variable=local-infile=0
port            = 3306
socket          = /var/lib/mysql/mysql.sock
server-id       = 1

[safe_mysqld]
err-log=/var/lib/mysql/mysqld.log

And my process:
/usr/bin/mysqld_safe --mysqld=mysqld --user=mysql --pid-file=/var/lib/mysql/mysqld.pid --socket=/var/lib/mysql/mysql.sock --datadir=/var/lib/mysql
[4 Feb 2009 10:17] Sveta Smirnova
Thank you for the feedback.

I tested with same version of server without success.

Please also send output of EXPLAIN problem query in your environment and, if possible, dump of the table.
[4 Feb 2009 14:44] [ name withheld ]
I updated glibc-2.6.1-18 to 2.6.1-18.3.
It is working now.

(Although yast online update and fou4s told me, I have the newest version, there has been the newer version on the ftp-server.)
[4 Feb 2009 15:47] Susanne Ebrecht
Will close this report now because of last reporter comment.