MySQL 5.7.24磁盘满了,导致数据库崩溃
Posted digdeep
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了MySQL 5.7.24磁盘满了,导致数据库崩溃相关的知识,希望对你有一定的参考价值。
2020-05-08T03:25:12.059499+08:00 2863585 [ERROR] Disk is full writing ‘/data/mysql/mysql3306/logs/mysql-bin.000086‘ (Errcode: 16044192 - No space left on device). Waiting for someone to free space...
2020-05-08T03:25:12.059525+08:00 2863585 [ERROR] Retry in 60 secs. Message reprinted in 600 secs
2020-05-08T03:26:12.059750+08:00 2863585 [ERROR] bin/mysqld: Binary logging not possible. Message: An error occurred during flush stage of the commit. ‘binlog_error_action‘ is set to ‘ABORT_SERVER‘. Hence aborting the server.
19:26:12 UTC - mysqld got signal 6 ;
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=201
max_threads=1000
thread_count=90
connection_count=90
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 405567 K bytes of memory
Hope that‘s ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f9d8474e3f0
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 = 7f9d1ea14e68 thread_stack 0x40000
bin/mysqld(my_print_stacktrace+0x35)[0xf4e815]
bin/mysqld(handle_fatal_signal+0x4a4)[0x7d1be4]
/lib64/libpthread.so.0(+0xf6d0)[0x7f9e3fa5e6d0]
/lib64/libc.so.6(gsignal+0x37)[0x7f9e3e448277]
/lib64/libc.so.6(abort+0x148)[0x7f9e3e449968]
bin/mysqld[0xee560a]
bin/mysqld(_ZN13MYSQL_BIN_LOG33handle_binlog_flush_or_sync_errorEP3THDb+0x17b)[0xeed92b]
bin/mysqld(_ZN13MYSQL_BIN_LOG14ordered_commitEP3THDbb+0x3ca)[0xef392a]
bin/mysqld(_ZN13MYSQL_BIN_LOG6commitEP3THDb+0x51d)[0xef407d]
bin/mysqld(_Z15ha_commit_transP3THDbb+0x174)[0x823004]
bin/mysqld(_Z17trans_commit_stmtP3THD+0x32)[0xdd2b92]
bin/mysqld(_Z21mysql_execute_commandP3THDb+0x73f)[0xd171df]
bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x40d)[0xd1bded]
bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11a5)[0xd1d015]
bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1dec4]
bin/mysqld(handle_connection+0x29c)[0xdef52c]
bin/mysqld(pfs_spawn_thread+0x174)[0xf74ee4]
/lib64/libpthread.so.0(+0x7e25)[0x7f9e3fa56e25]
/lib64/libc.so.6(clone+0x6d)[0x7f9e3e510bad]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f9d84187790): is an invalid pointer
Connection ID (thread ID): 2863585
Status: KILL_QUERY
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.
2020-05-08T08:20:14.845755+08:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-05-08T08:20:14.845966+08:00 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2020-05-08T08:20:14.846021+08:00 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.24-log) starting as process 16791 ...
2020-05-08T08:20:14.966104+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2020-05-08T08:20:14.966163+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-05-08T08:20:14.966175+08:00 0 [Note] InnoDB: Uses event mutexes
2020-05-08T08:20:14.966184+08:00 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2020-05-08T08:20:14.966192+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-05-08T08:20:14.966198+08:00 0 [Note] InnoDB: Using Linux native AIO
2020-05-08T08:20:14.967542+08:00 0 [Note] InnoDB: Number of pools: 1
2020-05-08T08:20:14.967740+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2020-05-08T08:20:14.970535+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
2020-05-08T08:20:15.226835+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2020-05-08T08:20:15.283149+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-05-08T08:20:15.326856+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-05-08T08:20:15.371735+08:00 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 232131895341
2020-05-08T08:20:15.371793+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 232131895350
2020-05-08T08:20:15.371806+08:00 0 [Note] InnoDB: Database was not shutdown normally!
2020-05-08T08:20:15.371814+08:00 0 [Note] InnoDB: Starting crash recovery.
2020-05-08T08:20:15.614143+08:00 0 [Note] InnoDB: Transaction 97940662 was in the XA prepared state.
2020-05-08T08:20:15.616262+08:00 0 [Note] InnoDB: Transaction 97940663 was in the XA prepared state.
2020-05-08T08:20:15.616300+08:00 0 [Note] InnoDB: 2 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
2020-05-08T08:20:15.616309+08:00 0 [Note] InnoDB: Trx id counter is 97940992
2020-05-08T08:20:15.674765+08:00 0 [Note] InnoDB: Last MySQL binlog file position 0 31399845, file name mysql-bin.000086
2020-05-08T08:21:08.670006+08:00 0 [Note] InnoDB: Starting in background the rollback of uncommitted transactions
2020-05-08T08:21:08.670086+08:00 0 [Note] InnoDB: Rollback of non-prepared transactions completed
2020-05-08T08:21:08.689269+08:00 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-05-08T08:21:08.689314+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-05-08T08:21:08.689411+08:00 0 [Note] InnoDB: Setting file ‘./ibtmp1‘ size to 12 MB. Physically writing the file full; Please wait ...
2020-05-08T08:21:08.811718+08:00 0 [Note] InnoDB: File ‘./ibtmp1‘ size is now 12 MB.
2020-05-08T08:21:08.813794+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2020-05-08T08:21:08.813822+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2020-05-08T08:21:08.814323+08:00 0 [Note] InnoDB: Waiting for purge to start
2020-05-08T08:21:08.864479+08:00 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 53581ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2020-05-08T08:21:08.864515+08:00 0 [Note] InnoDB: 5.7.24 started; log sequence number 232131895350
2020-05-08T08:21:08.864859+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/mysql3306/data/ib_buffer_pool
2020-05-08T08:21:08.865121+08:00 0 [Note] Plugin ‘FEDERATED‘ is disabled.
2020-05-08T08:21:08.873953+08:00 0 [Note] Recovering after a crash using /data/mysql/mysql3306/logs/mysql-bin
2020-05-08T08:21:08.941699+08:00 0 [ERROR] Error in Log_event::read_log_event(): ‘read error‘, data_len: 73, event_type: 2
2020-05-08T08:21:08.941741+08:00 0 [Note] Starting crash recovery...
2020-05-08T08:21:08.941799+08:00 0 [Note] InnoDB: Starting recovery for XA transactions...
2020-05-08T08:21:08.941809+08:00 0 [Note] InnoDB: Transaction 97940663 in prepared state after recovery
2020-05-08T08:21:08.941816+08:00 0 [Note] InnoDB: Transaction contains changes to 1 rows
2020-05-08T08:21:08.941823+08:00 0 [Note] InnoDB: Transaction 97940662 in prepared state after recovery
2020-05-08T08:21:08.941829+08:00 0 [Note] InnoDB: Transaction contains changes to 1 rows
2020-05-08T08:21:08.941835+08:00 0 [Note] InnoDB: 2 transactions in prepared state after recovery
2020-05-08T08:21:08.941841+08:00 0 [Note] Found 2 prepared transaction(s) in InnoDB
2020-05-08T08:21:08.942069+08:00 0 [Note] Crash recovery finished.
2020-05-08T08:21:08.942178+08:00 0 [Note] Crashed binlog file /data/mysql/mysql3306/logs/mysql-bin.000086 size is 31399936, but recovered up to 31399845. Binlog trimmed to 31399845 bytes.
2020-05-08T08:21:09.037887+08:00 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2020-05-08T08:21:09.037951+08:00 0 [Note] Server hostname (bind-address): ‘*‘; port: 3306
2020-05-08T08:21:09.038014+08:00 0 [Note] IPv6 is available.
2020-05-08T08:21:09.038031+08:00 0 [Note] - ‘::‘ resolves to ‘::‘;
2020-05-08T08:21:09.038058+08:00 0 [Note] Server socket created on IP: ‘::‘.
2020-05-08T08:21:09.043445+08:00 0 [Warning] ‘user‘ entry ‘mysql.session@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043470+08:00 0 [Warning] ‘user‘ entry ‘mysql.sys@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043486+08:00 0 [Warning] ‘user‘ entry ‘root@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043547+08:00 0 [Warning] ‘user‘ entry ‘dtexcel_nmg_db_user@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043609+08:00 0 [Warning] ‘db‘ entry ‘performance_schema mysql.session@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043620+08:00 0 [Warning] ‘db‘ entry ‘sys mysql.sys@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043648+08:00 0 [Warning] ‘db‘ entry ‘dtexcel_nmg dtexcel_nmg_db_user@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043660+08:00 0 [Warning] ‘db‘ entry ‘emr_new2 root@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.043707+08:00 0 [Warning] ‘proxies_priv‘ entry ‘@ root@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.090520+08:00 0 [Warning] ‘tables_priv‘ entry ‘user mysql.session@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.090568+08:00 0 [Warning] ‘tables_priv‘ entry ‘sys_config mysql.sys@localhost‘ ignored in --skip-name-resolve mode.
2020-05-08T08:21:09.092615+08:00 0 [Note] Failed to start slave threads for channel ‘‘
2020-05-08T08:21:09.118166+08:00 0 [Note] Event Scheduler: Loaded 5 events
2020-05-08T08:21:09.118518+08:00 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.7.24-log‘ socket: ‘/tmp/mysql3306.sock‘ port: 3306 MySQL Community Server (GPL)
2020-05-08T08:21:11.619425+08:00 0 [Note] InnoDB: Buffer pool(s) load completed at 200508 8:21:11
以上是关于MySQL 5.7.24磁盘满了,导致数据库崩溃的主要内容,如果未能解决你的问题,请参考以下文章