| Bug #89497 | mysqld got signal 11 ( and restart ) | ||
|---|---|---|---|
| Submitted: | 1 Feb 2018 12:26 | Modified: | 6 Mar 2018 17:55 |
| Reporter: | Szabo Laszlo | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.7.18 | OS: | Red Hat (Red Hat Enterprise Linux Server release 6.9 64bit) |
| Assigned to: | CPU Architecture: | Any | |
[1 Feb 2018 12:26]
Szabo Laszlo
[6 Feb 2018 17:55]
MySQL Verification Team
Hello, Thank you for your bug report. Truthfully, we have never seen a backtrace like this one. Hence , we need a fully repeatable test case in order to be able to verify the bug. Hence, dump of all tables involved in this crash, plus the statement that produced the error. You should also know that this kind of error can occur due to hardware errors or due to the temporary glitches in the RAM modules. If you use ECC DDR4 RAM modules, two bits checking one bit correcting, with some high quality RAID or SSD, then that is not your problem.
[6 Feb 2018 17:56]
MySQL Verification Team
In order to repeat the crash, do note that it is happening in a trigger before the UPDATE.
[7 Mar 2018 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".
[17 May 2018 10:01]
w yj
I have a similar problem. 00:43:02 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=209715200 read_buffer_size=1048576 max_used_connections=10 max_threads=3000 thread_count=15 connection_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27892831 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x2abc4c0be8b0 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 = 2abc4803fe28 thread_stack 0x40000 /apps/svr/mysql57/bin/mysqld(my_print_stacktrace+0x35)[0xf45e05] /apps/svr/mysql57/bin/mysqld(handle_fatal_signal+0x4a4)[0x7cd464] /lib64/libpthread.so.0[0x382b00f7e0] /lib64/libc.so.6(memcpy+0x3a1)[0x382ac89a51] /apps/svr/mysql57/bin/mysqld(strmake_root+0x39)[0xf3e7f9] /apps/svr/mysql57/bin/mysqld(_ZN17List_process_listclEP3THD+0x345)[0xd71db5] /apps/svr/mysql57/bin/mysqld(_ZN18Global_THD_manager19do_for_all_thd_copyEP11Do_THD_Impl+0x25d)[0x7cbf0d] /apps/svr/mysql57/bin/mysqld(_Z21mysqld_list_processesP3THDPKcb+0xfc8)[0xd69ef8] /apps/svr/mysql57/bin/mysqld(_Z21mysql_execute_commandP3THDb+0xb29)[0xd13949] /apps/svr/mysql57/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3a5)[0xd18245] /apps/svr/mysql57/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11af)[0xd1945f] /apps/svr/mysql57/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1a324] /apps/svr/mysql57/bin/mysqld(handle_connection+0x29c)[0xdea0fc] /apps/svr/mysql57/bin/mysqld(pfs_spawn_thread+0x174)[0xfbdbf4] /lib64/libpthread.so.0[0x382b007aa1] /lib64/libc.so.6(clone+0x6d)[0x382ace8bcd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (2abc4c12e8a0): is an invalid pointer Connection ID (thread ID): 12408003 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.
[17 May 2018 10:04]
w yj
Centos 6 (2.6.32-642.6.2.el6.x86_64）
