Bug #74133 MySQL periodically crashes with message 'mysqld got signal 11'
Submitted: 29 Sep 2014 11:04 Modified: 23 Dec 2017 17:03
Reporter: Isaac Lencoe Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.5.37 OS:Linux (2.6.32-431.17.1.el6.x86_64)
Assigned to: CPU Architecture:Any

[29 Sep 2014 11:04] Isaac Lencoe
Description:
MySQL instance periodically crashes with the following logger in the error log:

11:09:57 UTC - 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=8388608 
read_buffer_size=131072 
max_used_connections=77 
max_threads=151 
thread_count=37 
connection_count=37 
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338554 K bytes of memory 
Hope that's ok; if not, decrease some variables in the equation. 

Thread pointer: 0x20de4d0 
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_bottom = 7fa8b911fd98 thread_stack 0x40000 
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x79256e] 
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x67a9e3] 
/lib64/libpthread.so.0[0x3ef9e0f710] 
/usr/libexec/mysqld[0x7cd3dd] 
/usr/libexec/mysqld[0x7bae49] 
/usr/libexec/mysqld[0x7a5152] 
/usr/libexec/mysqld(_ZN7handler13ha_update_rowEPKhPh+0x76)[0x680066] 
/usr/libexec/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x10f3)[0x5f3853] 
/usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x2384)[0x586ca4] 
/usr/libexec/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x353)[0x599033] 
/usr/libexec/mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0x98)[0x5991b8] 
/usr/libexec/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x12c)[0x599f2c] 
/usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xb2e)[0x58a95e] 
/usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0xda)[0x61f68a] 
/usr/libexec/mysqld(handle_one_connection+0x5b)[0x61f7cb] 
/lib64/libpthread.so.0[0x3ef9e079d1] 
/lib64/libc.so.6(clone+0x6d)[0x3ef9ae8b7d] 

Trying to get some variables. 
Some pointers may be invalid and cause the dump to abort. 
Query (7fa7d4addb08): is an invalid pointer 
Connection ID (thread ID): 54895 
Status: NOT_KILLED 

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. 
140918 13:09:57 mysqld_safe Number of processes running now: 0 
140918 13:09:57 mysqld_safe mysqld restarted 
140918 13:09:57 [Note] libgovernor.so not found 
140918 13:09:57 [Note] Plugin 'FEDERATED' is disabled. 
140918 13:09:57 InnoDB: The InnoDB memory heap is disabled 
140918 13:09:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
140918 13:09:57 InnoDB: Compressed tables use zlib 1.2.3 
140918 13:09:57 InnoDB: Using Linux native AIO 
140918 13:09:57 InnoDB: Initializing buffer pool, size = 128.0M 
140918 13:09:57 InnoDB: Completed initialization of buffer pool 
140918 13:09:57 InnoDB: highest supported file format is Barracuda. 
InnoDB: Log scan progressed past the checkpoint lsn 158198982960 
140918 13:09: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 158198990395 
140918 13:09:57 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 
140918 13:09:57 InnoDB: Waiting for the background threads to start 
140918 13:09:58 InnoDB: 5.5.37 started; log sequence number 158198990395 
140918 13:09:58 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 
140918 13:09:58 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 
140918 13:09:58 [Note] Server socket created on IP: '127.0.0.1'. 
140918 13:09:59 [Note] Event Scheduler: Loaded 0 events 
140918 13:09:59 [Note] /usr/libexec/mysqld: ready for connections. 
Version: '5.5.37-cll-lve' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Atomicorp

OS Info:

-bash-4.1$ uname -a
Linux  2.6.32-431.17.1.el6.x86_64 #1 SMP Wed May 7 23:32:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
-bash-4.1$ free -mt
             total       used       free     shared    buffers     cached
Mem:         32102      31053       1048          0        302      28000
-/+ buffers/cache:       2751      29350
Swap:         3967         33       3934
Total:       36070      31086       4983

MySQL Configuration:

-bash-4.1$ cat /etc/my.cnf
[mysqld]
bind-address=127.0.0.1
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
max_allowed_packet = 64M
wait_timeout = 6000
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
old-passwords = 1

[mysqldump]
max_allowed_packet = 64M

mysql> show variables like '%version%';
+-------------------------+-------------------------------------------+
| Variable_name           | Value                                     |
+-------------------------+-------------------------------------------+
| innodb_version          | 5.5.37                                    |
| protocol_version        | 10                                        |
| slave_type_conversions  |                                           |
| version                 | 5.5.37-cll-lve                            |
| version_comment         | MySQL Community Server (GPL) by Atomicorp |
| version_compile_machine | x86_64                                    |
| version_compile_os      | Linux                                     |
+-------------------------+-------------------------------------------+
7 rows in set (0.00 sec)

MySQL Processes:

-bash-4.1$ ps -ef | grep mysql
root      1780     1  0 Aug28 ?        00:00:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql
mysql    47015  1780 37 Sep18 ?        4-03:23:17 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/log/mysqld.log --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/lib/mysql/mysql.sock

MySQL packages:

-bash-4.1$ rpm -qa | grep -i mysql
mysql-connector-odbc-5.1.5r1144-7.el6.x86_64
MySQL-python-1.2.3-0.3.c1.1.el6.x86_64
mysql-libs-5.5.37-22.el6.art.x86_64
mysql-server-5.5.37-22.el6.art.x86_64
mysql-5.5.37-22.el6.art.x86_64
perl-DBD-MySQL-4.013-3.el6.x86_64
php-mysql-5.4.29-35.el6.art.x86_64
mysqlclient16-5.1.59-2.el6.art.x86_64

How to repeat:
Not known at the moment.
[23 Nov 2017 17:03] Miguel Solorzano
Thank you for the bug report. Have you resolved this issue with major version than 5.5?. Thanks.
[24 Dec 2017 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".