MySQL Bugs: #52779: Mysql server crashes with "mysqld got signal 11", "Cannot determine thread"

Bug #52779	Mysql server crashes with "mysqld got signal 11", "Cannot determine thread"
Submitted:	13 Apr 2010 9:56	Modified:	28 Sep 2010 14:07
Reporter:	Vitaly Karasik	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.90, 5.0.91	OS:	Linux (RHEL 5.1)
Assigned to:		CPU Architecture:	Any
Tags:	crash

Description:
Server crashes every few hours. See errlog below.

100412 12:22:56 - 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=78
max_connections=300
threads_connected=62
It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 660985 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.

thd=0x2aab101e32f0
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=0x461ccfc0, 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 0x6efb5c0 = XA COMMIT 
thd->0x312d613030363430633a393561343a34626332653765653a323264613162,0x61
thd->3030363430633a393561343a34626332653765653a323264613164,0x20003
thd->thread_id=343
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
100412 12:22:57  mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 65 3108354177
100412 12:22:57  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...
InnoDB: Doing recovery: scanned up to log sequence number 65 3108695743
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 0 1966140928
100412 12:22:58  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 79156470, file name /data/logs/mysql-binlog/mysql-binlog.002760
InnoDB: Starting in background the rollback of uncommitted transactions
100412 12:22:59  InnoDB: Rolling back trx with id 0 1966138500, 2 rows to undo
100412 12:22:59  InnoDB: Started; log sequence number 65 3108695743
100412 12:22:59 [Note] Recovering after a crash using /data/logs/mysql-binlog/mysql-binlog

InnoDB: Rolling back of trx id 0 1966138500 completed
100412 12:22:59  InnoDB: Rollback of non-prepared transactions completed
100412 12:22:59 [Note] Starting crash recovery...
100412 12:22:59 [Note] Crash recovery finished.
100412 12:23:00 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.90-community-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition (GPL)

How to repeat:
Unfortunately, I don't know.

my.cnf

Attachment: my.cnf.txt (text/plain), 659 bytes.

It is possible that you have

SET autocommit=1

executed somewhere in your applications? I wonder if this is a duplicate of Bug #51342.

Yes, we use "autocommit=1" and distributed transaction.

I reviewed bug ##51342 and I noticed that this problem is fixed in 5.0.91.
What is current status of 5.0.91?  Do you have any estimation when it will be available?

Thank you for your answer!
Vitaly

So this is really a duplicate of Bug #51342.

As for 5.0.91 official release, I do not see any specific date planned any time soon. It is under extended support, so we do not have any definite plans. I'd expect one more release of 5.0.x this year. 

If some serious security related bug will be found, we may be forced to release 5.0.91 with the fix ASAP.

thank you!

and the same question for 5.1.46?

Usually we release 5.1.x every month (check http://dev.mysql.com/doc/refman/5.1/en/news-5-1-x.html). 5.1.45 was released on March 1, 2010. So, 5.1.46 is coming soon :)

thank you!

>It is possible that you have
>SET autocommit=1
>executed somewhere in your applications

Is any "SET autocommit=1" may cause crash or only when it was used in the same session as distributed transaction started?
In other words, is following may lead to crash? (from full query log):

                   4658 Query       XA START .....
                   5143 Query       SET autocommit=1
                   4658 Query       XA END  ......

Upgrading to 5.0.91 didn't fix this problem. It even seems that situation is worse - 3 crashes during last day.

It would be useful to know if this is repeatable with recent 5.1.49.

I'm wondering what kind of server and CPU do you have?

>[23 Jul 20:15] Valeriy Kravchuk 
>It would be useful to know if this is repeatable with recent 5.1.49.

We didn't upgraded to 5.1, our developers just re-writed code w/o commits.

>[23 Jul 20:20] Charlton Kao 
>I'm wondering what kind of server and CPU do you have?
Dell PE 1950 - Gen III with  Intel(R) Xeon(R) CPU E5405 @ 2.00G

Can be duplicate of bug #51855 as well.

Is your problem solved?

Susanne, 
As I wrote, we just re-write our code - so our server doesn't crash.

We upgraded our gentoo kernel to 2.6.34 and mysql to 5.1.50 and the problem went away.  Never really found out the source of our problem, maybe some incompatibility between the versions of mysql and linux.