Comments - ERROR 2013 (HY000): Lost connection to MySQL server during query
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Can you please provide some example to reproduce?
MariaDB [misp]> select * from sightings; ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [misp]> select count(*) from sightings; ERROR 2013 (HY000): Lost connection to MySQL server during query
Error Log:
Some pointers may be invalid and cause the dump to abort. Query (0x7fc2e0011060): SELECT Sighting.org_id, Sighting.attribute_id, Sighting.type, (DATE(FROM_UNIXTIME(Sighting.date_sighting))) AS Sightingdate_sighting, (COUNT(id)) AS Sightingsighting_count, (MAX(date_sighting)) AS Sightinglast_timestamp FROM misp.sightings AS Sighting WHERE Sighting.event_id = 57324 GROUP BY org_id, attribute_id, type, (DATE(FROM_UNIXTIME(Sighting.date_sighting))) ORDER BY (DATE(FROM_UNIXTIME(Sighting.date_sighting))) ASC Connection ID (thread ID): 8 Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
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. 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Uses event mutexes 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Compressed tables use zlib 1.2.7 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Using Linux native AIO 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Number of pools: 1 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Using SSE2 crc32 instructions 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Completed initialization of buffer pool 2021-03-26 13:40:36 140349218248448 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Highest supported file format is Barracuda. 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Starting crash recovery from checkpoint LSN=2333672402984 2021-03-26 13:40:36 140349989546176 [Note] InnoDB: Starting final batch to recover 413 pages from redo log. 2021-03-26 13:40:37 140349989546176 [Note] InnoDB: 128 out of 128 rollback segments are active. 2021-03-26 13:40:37 140349989546176 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2021-03-26 13:40:37 140349989546176 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-03-26 13:40:37 140349989546176 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait