Ubuntu 18.04.1 LTS
4.15.0-34-generic # 37-Ubuntu
Docker: 18.06.1-this build e68fc7a
mysql: 5 @ sha256: e47e309f72c831cf880cc0e1990b9c5ac427016acdc71346a36c83806ca79bb4
mysql --version = Ver 14.14 Distrib 5.7.25, for Linux (x86_64) using the EditLine wrapper
07:17:39 UTC - mysqld has signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries to which it was linked is corrupt, poorly constructed,
or wrongly configured. This error can also be caused by hardware malfunction.
Attempt to collect information that can help diagnose the problem.
Since this is a crash and something is really wrong, the information
collection process may fail.
key_buffer_size = 8388608
read_buffer_size = 131072
max_used_connections = 6
max_threads = 151
thread_count = 5
number_connection = 5
It is possible that mysqld uses up to
key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 68196 KB of memory
I hope it goes otherwise, decrease some variables of the equation.
Thread Pointer: 0x7f9814012240
Trace attempt. You can use the following information to discover
where mysqld is dead. If you do not see any message after that, something has happened
terribly wrong ...
stack_bottom = 7f98580a4e80 thread_stack 0x40000
mysqld (my_print_stacktrace + 0x2c)[0x560da4deb81c]
mysqld (handle_fatal_signal + 0x479)[0x560da4716879]
mysqld (_Z32page_cur_search_with_match_bytesPK11buf_block_tPK12dict_index_tPK8dtuple_t15page_cur_mode_tPmS9_S9_S9_P9page_cur_t + 0x167)[0x560da4eb2be7]
mysqld (_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t + 0x989)[0x560da4fd81a9]
mysqld (+ 0xe682d9)[0x560da4f2c2d9]
mysqld (_Z15row_search_mvccPh15page_cur_mode_tP14row_prebuilt_tmm + 0x1b9e)[0x560da4f3307e]
mysqld (_ZN11ha_innobase10index_readEPhPKhj16ha_rkey_function + 0x244)[0x560da4e2ee24]
mysqld (_ZN7handler17ha_index_read_mapEPhPKhm16ha_rkey_function + 0x30f)[0x560da476830f]
mysqld (+ 0xac68f4)[0x560da4b8a8f4]
mysqld (_Z10sub_selectP4JOINP7QEP_TABb + 0x105)[0x560da4b8dbb5]
mysqld (_ZN4JOIN4execEv + 0x370)[0x560da4b86a30]
mysqld (_Z12handle_queryP3THDP3LEXP12Query_resultyy + 0x233)[0x560da4bf5eb3]
mysqld (+ 0x61cf32)[0x560da46e0f32]
mysqld (_Z21mysql_execute_commandP3THDb + 0x460d)[0x560da4bb972d]
mysqld (_Z11mysql_parseP3THDP12Parser_state + 0x395)[0x560da4bbbff5]
mysqld (_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command + 0xfc4)[0x560da4bbd0b4]
mysqld (_Z10do_commandP3THD + 0x197)[0x560da4bbe487]
mysqld (handle_connection + 0x278)[0x560da4c7af38]
mysqld (pfs_spawn_thread + 0x1b4)[0x560da5153164]
Try to get variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f98141c3520): SELECT `id`,` state`, `param`,` cursor_row`, `cursor_column`,` can_send`, `createdAt`,` updatedAt`, `userId`,` botId` FROM & # 39; states` AS `state` WHERE` state`.`userId` = 131913 AND` state`.`botId` = 3202 LIMIT 1
Connection ID (thread ID): 863486
The man page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you discover the cause of the crash.
Probably unrelated, but repeated a lot:
2019-06-12T14: 52: 32.090130Z 0 [Note] InnoDB: page_cleaner: the expected loop of 1000 ms took 10295ms. The settings may not be optimal. (rinsed = 9 and expelled = 0, during the time.)
2019-06-12T14: 53: 56.177026Z 0 [Note] InnoDB: page_cleaner: the expected loop of 1000 ms took 8427ms. The settings may not be optimal. (rinsed = 200 and expelled = 0, during the time.)
2019-06-12T15: 03: 05.055209Z 0 [Note] InnoDB: page_cleaner: The expected loop of 1000 ms took 6080ms. The settings may not be optimal. (rinsed = 3 and expelled = 0, during the time.)
2019-06-12T15: 03: 52.398646Z 0 [Note] InnoDB: page_cleaner: the expected loop of 1000 ms took 5042ms. The settings may not be optimal. (rinsed = 168 and expelled = 0, during the time.)
more logs and settings
The default settings of the fixed menu have not been changed. It works well and queries on all unassigned tables work well, but all queries, even
CHECK TABLE on the affected table has crashed the server instantly.
I did not attempt to recover data, just deleted and restored the table from backups. However, it's the second time in 2 months that this has happened (at different tables, but both were tables with more writes than others).
How can I diagnose the cause of corruption or make it less likely?
What I've checked so far:
- The included newspaper is the first sign of a problem, the previous entry of the newspaper dates from 30 minutes before and is independent. And although the crash with a corrupted table is reproducible, I have no way of reproducing the corruption and a superior log verbosity is unideal on the production server under load.
dmesg | egrep -i & # 39; process killed & # 39; is empty, the box has 4 GB of ram and swap enabled. I do not think tables have been corrupted because of a deadly error in the middle of a writing.