Bug #103660 Sporadic crashes with signal 11
Submitted: 11 May 14:18 Modified: 11 May 14:26
Reporter: Sebastiano Degan Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.6.51 OS:Debian (9)
Assigned to: CPU Architecture:x86

[11 May 14:18] Sebastiano Degan
Description:
After an upgrade to mysql 5.6.51 (from 5.6.50) we have been experiencing crashes (5/6 a day) with the following stack:

05:49:21 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=30
max_threads=300
thread_count=28
connection_count=28
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 127233 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x559db57f59c0
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 = 7f3374a66e98 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x559daa438adc]
/usr/sbin/mysqld(handle_fatal_signal+0x4b1)[0x559daa1d35f1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f34ea56c0e0]
/usr/sbin/mysqld(+0x7c2ec6)[0x559daa4b0ec6]
/usr/sbin/mysqld(+0x873c7d)[0x559daa561c7d]
/usr/sbin/mysqld(+0x8745a8)[0x559daa5625a8]
/usr/sbin/mysqld(+0x874b90)[0x559daa562b90]
/usr/sbin/mysqld(+0x822ce5)[0x559daa510ce5]
/usr/sbin/mysqld(+0x826a4b)[0x559daa514a4b]
/usr/sbin/mysqld(+0x82775f)[0x559daa51575f]
/usr/sbin/mysqld(+0x80b59f)[0x559daa4f959f]
/usr/sbin/mysqld(+0x77f494)[0x559daa46d494]
/usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0xa1)[0x559daa1295c1]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x197f)[0x559daa2b6dbf]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x311b)[0x559daa24e87b]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x390)[0x559daa252020]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1279)[0x559daa253ab9]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17a)[0x559daa21fbfa]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x559daa21fc60]
/usr/sbin/mysqld(pfs_spawn_thread+0x146)[0x559daa6771b6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f34ea5624a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f34e91bed0f]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f332c3172b0): UPDATE nodi set internet_online='0'  where id='3734'
Connection ID (thread ID): 11518
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.

The query seems always to point to the same table, but that table is also one of the most used so we are unsure whether that is the real problem.
We have already issued an ALTER TABLE nodi FORCE with no result.

How to repeat:
Any attempt to replicate the problem on a test instance failed.
At the moment we have no way to replicate this.

Suggested fix:
Downgrade to 5.6.50
[11 May 14:26] MySQL Verification Team
Thank you for the bug report. For further process of this bug report we need a repeatable test case which you could comment and print here. Anyway I would you suggest to upgrade to new current versions since 5.6 is on EOL:

https://endoflife.software/applications/databases/mysql