MySQL Forums
Forum List  »  General

Re: Met ERROR 2013 (HY000): Lost connection to MySQL server during query error
Posted by: dclar dclar
Date: July 04, 2019 01:35AM

07:34:28 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.

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

Thread pointer: 0x7fdc2c000ae0
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 = 7fdc540b2e30 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fdc2c005640): explain (select sub_tmp.cid, (select count(*) from t10 where pid = ) as new_t10 from t10_sub as sub_tmp order by new_t10 + 1) union (select, from t10_sub as sub_tmp)
Connection ID (thread ID): 2

The manual page at contains
information that should help you find out what is causing the crash.
2019-07-04T07:34:29.407382Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-07-04T07:34:29.409167Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.26) starting as process 31993 ...
2019-07-04T07:34:29.412463Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-07-04T07:34:29.412500Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-07-04T07:34:29.412508Z 0 [Note] InnoDB: Uses event mutexes
2019-07-04T07:34:29.412529Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-07-04T07:34:29.412536Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-07-04T07:34:29.412540Z 0 [Note] InnoDB: Using Linux native AIO
2019-07-04T07:34:29.412850Z 0 [Note] InnoDB: Number of pools: 1
2019-07-04T07:34:29.412974Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-07-04T07:34:29.414640Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-07-04T07:34:29.423123Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-07-04T07:34:29.425153Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-07-04T07:34:29.437898Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-07-04T07:34:29.439273Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 282282231
2019-07-04T07:34:29.439296Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 282282240
2019-07-04T07:34:29.439302Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-07-04T07:34:29.439330Z 0 [Note] InnoDB: Starting crash recovery.
2019-07-04T07:34:29.565008Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-07-04T07:34:29.565037Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-07-04T07:34:29.565092Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-07-04T07:34:29.611575Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-07-04T07:34:29.613034Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-07-04T07:34:29.613062Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-07-04T07:34:29.613693Z 0 [Note] InnoDB: Waiting for purge to start
2019-07-04T07:34:29.663838Z 0 [Note] InnoDB: 5.7.26 started; log sequence number 282282240
2019-07-04T07:34:29.664238Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2019-07-04T07:34:29.664266Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-07-04T07:34:29.666550Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190704 15:34:29
2019-07-04T07:34:29.670356Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2019-07-04T07:34:29.670693Z 0 [Warning] CA certificate ca.pem is self signed.
2019-07-04T07:34:29.673308Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2019-07-04T07:34:29.675522Z 0 [Note] IPv6 is not available.
2019-07-04T07:34:29.675580Z 0 [Note] - '' resolves to '';
2019-07-04T07:34:29.675624Z 0 [Note] Server socket created on IP: ''.
2019-07-04T07:34:29.686571Z 0 [Note] Event Scheduler: Loaded 0 events
2019-07-04T07:34:29.686737Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.26' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)

Options: ReplyQuote

Written By
Re: Met ERROR 2013 (HY000): Lost connection to MySQL server during query error
July 04, 2019 01:35AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.