Bug #78218 The database engine restarts due to internal failure. Got error: 2013: Lost con.
Submitted: 26 Aug 2015 8:27 Modified: 24 Apr 2019 20:16
Reporter: Allan Andersen Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.5.43 OS:CentOS (32bit)
Assigned to: CPU Architecture:Any

[26 Aug 2015 8:27] Allan Andersen
mysqlcheck --database confluence
Warning: Using unique option prefix database instead of databases is deprecated and will be removed in a future release. Please use the full name instead.
confluence.AO_187CCC_SIDEBAR_LINK                  OK
confluence.AO_21D670_WHITELIST_RULES               OK
confluence.AO_26DB7F_ENTITIES_TO_ROOMS             OK
confluence.AO_26DB7F_ENTITIES_TO_ROOM_CFG          OK
confluence.AO_38321B_CUSTOM_CONTENT_LINK           OK
confluence.AO_42E351_HEALTH_CHECK_ENTITY           OK
confluence.AO_54C900_CONTENT_BLUEPRINT_AO          OK
confluence.AO_54C900_C_TEMPLATE_REF                OK
confluence.AO_54C900_SPACE_BLUEPRINT_AO            OK
confluence.AO_5F3884_FEATURE_DISCOVERY             OK
confluence.AO_5FB9D7_AOHIP_CHAT_LINK               OK
confluence.AO_5FB9D7_AOHIP_CHAT_USER               OK
confluence.AO_6384AB_DISCOVERED                    OK
mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ... '

From mysql log:
150826  9:58:28 [Note] Server hostname (bind-address): ''; port: 3306
150826  9:58:28 [Note]   - '' resolves to '';
150826  9:58:28 [Note] Server socket created on IP: ''.
150826  9:58:28 [Note] Event Scheduler: Loaded 0 events
150826  9:58:28 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.43'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
150826 10:07:53 [Warning] IP address '' could not be resolved: Name or service not known
08:18:38 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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 335704 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x9394820
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 = ffffffffa3e3b31c thread_stack 0x30000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (ffffffffb6c7ff10): is an invalid pointer
Connection ID (thread ID): 55

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.
150826 10:18:39 mysqld_safe Number of processes running now: 0
150826 10:18:39 mysqld_safe mysqld restarted
150826 10:18:39 [Note] /usr/sbin/mysqld (mysqld 5.5.43) starting as process 14087 ...
150826 10:18:39 [Note] Plugin 'FEDERATED' is disabled.
150826 10:18:39 InnoDB: The InnoDB memory heap is disabled
150826 10:18:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150826 10:18:39 InnoDB: Compressed tables use zlib 1.2.3
150826 10:18:39 InnoDB: Using Linux native AIO
150826 10:18:39 InnoDB: Initializing buffer pool, size = 128.0M
150826 10:18:39 InnoDB: Completed initialization of buffer pool
150826 10:18:39 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 28128071961
150826 10:18:39  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 28128106575
150826 10:18:39  InnoDB: Starting an apply batch of log records to the database...
150826 10:18:40 InnoDB: 5.5.43 started; log sequence number 28128106575
150826 10:18:40 [Note] Server hostname (bind-address): ''; port: 3306
150826 10:18:40 [Note]   - '' resolves to '';
150826 10:18:40 [Note] Server socket created on IP: ''.
150826 10:18:40 [Note] Event Scheduler: Loaded 0 events
150826 10:18:40 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.43'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)

How to repeat:
I have been updating my confluence installation and tried to update a plugin which failed to write some data to the database. Now one table is corrupted and as you can see the mysqlcheck fails when running it.

I have tried to set the innodb recover paramter with no luck. Even if I try to fetch data from the table the database engine crash and restarts.
[24 Apr 2019 20:16] MySQL Verification Team
Not repeatable test case was provided to check with most recent releases.