mysql磁盘问题记录

2021-10-25 15:10:13

210127 19:25:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210127 19:25:28 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 24858 ...
210127 19:25:28 InnoDB: The InnoDB memory heap is disabled
210127 19:25:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210127 19:25:28 InnoDB: Compressed tables use zlib 1.2.7
210127 19:25:28 InnoDB: Using Linux native AIO
210127 19:25:28 InnoDB: Initializing buffer pool, size = 128.0M
210127 19:25:28 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
210127 19:25:28 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
210127 19:25:28 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
210127 19:25:28 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
210127 19:25:28 InnoDB: Waiting for the background threads to start
210127 19:25:29 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 0
210127 19:25:29 [Note] Plugin ‘FEEDBACK‘ is disabled.
210127 19:25:29 [Note] Server socket created on IP: ‘127.0.0.1‘.
210127 19:25:29 [Note] Event Scheduler: Loaded 0 events
210127 19:25:29 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210127 19:27:37 [Note] /usr/libexec/mysqld: Normal shutdown
210127 19:27:37 [Note] Event Scheduler: Purging the queue. 0 events
210127 19:27:37 InnoDB: Starting shutdown...
210127 19:27:39 InnoDB: Shutdown completed; log sequence number 5812568
210127 19:27:39 [Note] /usr/libexec/mysqld: Shutdown complete

210127 19:27:39 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210127 19:27:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210127 19:27:52 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9594 ...
210127 19:27:53 InnoDB: The InnoDB memory heap is disabled
210127 19:27:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210127 19:27:53 InnoDB: Compressed tables use zlib 1.2.7
210127 19:27:53 InnoDB: Using Linux native AIO
210127 19:27:53 InnoDB: Initializing buffer pool, size = 128.0M
210127 19:27:53 InnoDB: Completed initialization of buffer pool
210127 19:27:53 InnoDB: highest supported file format is Barracuda.
210127 19:27:53 InnoDB: Waiting for the background threads to start
210127 19:27:54 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 5812568
210127 19:27:54 [Note] Plugin ‘FEEDBACK‘ is disabled.
210127 19:27:54 [Note] Server socket created on IP: ‘127.0.0.1‘.
210127 19:27:54 [Note] Event Scheduler: Loaded 0 events
210127 19:27:54 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210127 19:35:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210127 19:35:57 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9662 ...
210127 19:35:57 InnoDB: The InnoDB memory heap is disabled
210127 19:35:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210127 19:35:57 InnoDB: Compressed tables use zlib 1.2.7
210127 19:35:57 InnoDB: Using Linux native AIO
210127 19:35:57 InnoDB: Initializing buffer pool, size = 128.0M
210127 19:35:58 InnoDB: Completed initialization of buffer pool
210127 19:35:58 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210127 19:35:58 InnoDB: Waiting for the background threads to start
210127 19:35:59 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 5846620
210127 19:35:59 [Note] Plugin ‘FEEDBACK‘ is disabled.
210127 19:35:59 [Note] Server socket created on IP: ‘127.0.0.1‘.
210127 19:35:59 [Note] Event Scheduler: Loaded 0 events
210127 19:35:59 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210127 19:36:44 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210127 19:36:44 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9625 ...
210127 19:36:44 InnoDB: The InnoDB memory heap is disabled
210127 19:36:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210127 19:36:44 InnoDB: Compressed tables use zlib 1.2.7
210127 19:36:44 InnoDB: Using Linux native AIO
210127 19:36:44 InnoDB: Initializing buffer pool, size = 128.0M
210127 19:36:44 InnoDB: Completed initialization of buffer pool
210127 19:36:44 InnoDB: highest supported file format is Barracuda.
210127 19:36:44 InnoDB: Starting crash recovery from checkpoint LSN=5846650
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210127 19:36:44 InnoDB: Starting final batch to recover 1 pages from redo log
210127 19:36:44 InnoDB: Waiting for the background threads to start
210127 19:36:45 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 5846835
210127 19:36:45 [Note] Plugin ‘FEEDBACK‘ is disabled.
210127 19:36:45 [Note] Server socket created on IP: ‘127.0.0.1‘.
210127 19:36:45 [Note] Event Scheduler: Loaded 0 events
210127 19:36:45 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210129 10:32:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210129 10:32:56 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9444 ...
210129 10:32:57 InnoDB: The InnoDB memory heap is disabled
210129 10:32:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210129 10:32:57 InnoDB: Compressed tables use zlib 1.2.7
210129 10:32:57 InnoDB: Using Linux native AIO
210129 10:32:57 InnoDB: Initializing buffer pool, size = 128.0M
210129 10:32:57 InnoDB: Completed initialization of buffer pool
210129 10:32:57 InnoDB: highest supported file format is Barracuda.
210129 10:32:57 InnoDB: Starting crash recovery from checkpoint LSN=5975706
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210129 10:33:04 InnoDB: Starting final batch to recover 3 pages from redo log
210129 10:33:05 InnoDB: Waiting for the background threads to start
210129 10:33:06 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 5977120
210129 10:33:08 [Note] Plugin ‘FEEDBACK‘ is disabled.
210129 10:33:08 [Note] Server socket created on IP: ‘127.0.0.1‘.
210129 10:33:11 [Note] Event Scheduler: Loaded 0 events
210129 10:33:11 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210201 12:38:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210201 12:38:15 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9548 ...
210201 12:38:16 InnoDB: The InnoDB memory heap is disabled
210201 12:38:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210201 12:38:16 InnoDB: Compressed tables use zlib 1.2.7
210201 12:38:16 InnoDB: Using Linux native AIO
210201 12:38:17 InnoDB: Initializing buffer pool, size = 128.0M
210201 12:38:17 InnoDB: Completed initialization of buffer pool
210201 12:38:17 InnoDB: highest supported file format is Barracuda.
210201 12:38:17 InnoDB: Starting crash recovery from checkpoint LSN=52409894
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210201 12:38:25 InnoDB: Starting final batch to recover 2 pages from redo log
210201 12:38:25 InnoDB: Waiting for the background threads to start
210201 12:38:26 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 52410335
210201 12:38:26 [Note] Plugin ‘FEEDBACK‘ is disabled.
210201 12:38:27 [Note] Server socket created on IP: ‘127.0.0.1‘.
210201 12:38:27 [Note] Event Scheduler: Loaded 0 events
210201 12:38:27 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210201 17:17:20 [Note] /usr/libexec/mysqld: Normal shutdown
210201 17:17:20 [Note] Event Scheduler: Purging the queue. 0 events
210201 17:17:20 InnoDB: Starting shutdown...
210201 17:17:25 InnoDB: Shutdown completed; log sequence number 55810475
210201 17:17:25 [Note] /usr/libexec/mysqld: Shutdown complete

210201 17:17:25 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210201 17:17:51 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210201 17:17:53 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9456 ...
210201 17:17:53 InnoDB: The InnoDB memory heap is disabled
210201 17:17:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210201 17:17:53 InnoDB: Compressed tables use zlib 1.2.7
210201 17:17:53 InnoDB: Using Linux native AIO
210201 17:17:54 InnoDB: Initializing buffer pool, size = 128.0M
210201 17:17:54 InnoDB: Completed initialization of buffer pool
210201 17:17:54 InnoDB: highest supported file format is Barracuda.
210201 17:17:55 InnoDB: Waiting for the background threads to start
210201 17:17:56 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 55810475
210201 17:17:56 [Note] Plugin ‘FEEDBACK‘ is disabled.
210201 17:17:56 [Note] Server socket created on IP: ‘127.0.0.1‘.
210201 17:17:57 [Note] Event Scheduler: Loaded 0 events
210201 17:17:57 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210202 13:27:58 [Note] /usr/libexec/mysqld: Normal shutdown
210202 13:27:58 [Note] Event Scheduler: Purging the queue. 0 events
210202 13:27:58 InnoDB: Starting shutdown...
210202 13:28:04 InnoDB: Shutdown completed; log sequence number 61897681
210202 13:28:04 [Note] /usr/libexec/mysqld: Shutdown complete

210202 13:28:04 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210202 13:28:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210202 13:28:35 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9552 ...
210202 13:28:36 InnoDB: The InnoDB memory heap is disabled
210202 13:28:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210202 13:28:36 InnoDB: Compressed tables use zlib 1.2.7
210202 13:28:36 InnoDB: Using Linux native AIO
210202 13:28:37 InnoDB: Initializing buffer pool, size = 128.0M
210202 13:28:37 InnoDB: Completed initialization of buffer pool
210202 13:28:37 InnoDB: highest supported file format is Barracuda.
210202 13:28:39 InnoDB: Waiting for the background threads to start
210202 13:28:40 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 61897681
210202 13:28:40 [Note] Plugin ‘FEEDBACK‘ is disabled.
210202 13:28:41 [Note] Server socket created on IP: ‘127.0.0.1‘.
210202 13:28:41 [Note] Event Scheduler: Loaded 0 events
210202 13:28:41 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210202 13:30:52 [Note] /usr/libexec/mysqld: Normal shutdown
210202 13:30:52 [Note] Event Scheduler: Purging the queue. 0 events
210202 13:30:52 InnoDB: Starting shutdown...
210202 13:30:55 InnoDB: Shutdown completed; log sequence number 61902108
210202 13:30:55 [Note] /usr/libexec/mysqld: Shutdown complete

210202 13:30:55 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210202 13:31:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210202 13:31:21 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9608 ...
210202 13:31:21 InnoDB: The InnoDB memory heap is disabled
210202 13:31:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210202 13:31:21 InnoDB: Compressed tables use zlib 1.2.7
210202 13:31:21 InnoDB: Using Linux native AIO
210202 13:31:21 InnoDB: Initializing buffer pool, size = 128.0M
210202 13:31:21 InnoDB: Completed initialization of buffer pool
210202 13:31:21 InnoDB: highest supported file format is Barracuda.
210202 13:31:21 InnoDB: Waiting for the background threads to start
210202 13:31:22 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 61902108
210202 13:31:22 [Note] Plugin ‘FEEDBACK‘ is disabled.
210202 13:31:22 [Note] Server socket created on IP: ‘127.0.0.1‘.
210202 13:31:22 [Note] Event Scheduler: Loaded 0 events
210202 13:31:22 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210202 14:06:29 [Note] /usr/libexec/mysqld: Normal shutdown
210202 14:06:29 [Note] Event Scheduler: Purging the queue. 0 events
210202 14:06:29 InnoDB: Starting shutdown...
210202 14:06:32 InnoDB: Shutdown completed; log sequence number 62049032
210202 14:06:32 [Note] /usr/libexec/mysqld: Shutdown complete

210202 14:06:32 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210202 14:07:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210202 14:07:04 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9553 ...
210202 14:07:04 InnoDB: The InnoDB memory heap is disabled
210202 14:07:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210202 14:07:04 InnoDB: Compressed tables use zlib 1.2.7
210202 14:07:04 InnoDB: Using Linux native AIO
210202 14:07:04 InnoDB: Initializing buffer pool, size = 128.0M
210202 14:07:04 InnoDB: Completed initialization of buffer pool
210202 14:07:05 InnoDB: highest supported file format is Barracuda.
210202 14:07:07 InnoDB: Waiting for the background threads to start
210202 14:07:08 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 62049032
210202 14:07:08 [Note] Plugin ‘FEEDBACK‘ is disabled.
210202 14:07:08 [Note] Server socket created on IP: ‘127.0.0.1‘.
210202 14:07:08 [Note] Event Scheduler: Loaded 0 events
210202 14:07:08 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210207 10:44:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210207 10:45:01 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9596 ...
210207 10:45:03 InnoDB: The InnoDB memory heap is disabled
210207 10:45:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210207 10:45:03 InnoDB: Compressed tables use zlib 1.2.7
210207 10:45:03 InnoDB: Using Linux native AIO
210207 10:45:03 InnoDB: Initializing buffer pool, size = 128.0M
210207 10:45:03 InnoDB: Completed initialization of buffer pool
210207 10:45:03 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210207 10:45:10 InnoDB: Waiting for the background threads to start
210207 10:45:11 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 71118417
210207 10:45:11 [Note] Plugin ‘FEEDBACK‘ is disabled.
210207 10:45:11 [Note] Server socket created on IP: ‘127.0.0.1‘.
210207 10:45:12 [Note] Event Scheduler: Loaded 0 events
210207 10:45:12 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210304 11:17:01 [Note] /usr/libexec/mysqld: Normal shutdown
210304 11:17:01 [Note] Event Scheduler: Purging the queue. 0 events
210304 11:17:06 InnoDB: Starting shutdown...
210304 11:17:16 InnoDB: Shutdown completed; log sequence number 546298351
210304 11:17:16 [Note] /usr/libexec/mysqld: Shutdown complete

210304 11:17:19 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210304 11:32:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210304 11:32:41 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9538 ...
210304 11:32:37 InnoDB: The InnoDB memory heap is disabled
210304 11:32:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210304 11:32:37 InnoDB: Compressed tables use zlib 1.2.7
210304 11:32:37 InnoDB: Using Linux native AIO
210304 11:32:38 InnoDB: Initializing buffer pool, size = 128.0M
210304 11:32:39 InnoDB: Completed initialization of buffer pool
210304 11:32:43 InnoDB: highest supported file format is Barracuda.
210304 11:32:47 InnoDB: Waiting for the background threads to start
210304 11:32:48 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 546298351
210304 11:32:49 [Note] Plugin ‘FEEDBACK‘ is disabled.
210304 11:32:49 [Note] Server socket created on IP: ‘127.0.0.1‘.
210304 11:32:49 [Note] Event Scheduler: Loaded 0 events
210304 11:32:49 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210309 10:02:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210309 10:02:10 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9633 ...
210309 10:02:10 InnoDB: The InnoDB memory heap is disabled
210309 10:02:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210309 10:02:10 InnoDB: Compressed tables use zlib 1.2.7
210309 10:02:10 InnoDB: Using Linux native AIO
210309 10:02:11 InnoDB: Initializing buffer pool, size = 128.0M
210309 10:02:11 InnoDB: Completed initialization of buffer pool
210309 10:02:11 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210309 10:02:14 InnoDB: Waiting for the background threads to start
210309 10:02:15 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 746086019
210309 10:02:15 [Note] Plugin ‘FEEDBACK‘ is disabled.
210309 10:02:15 [Note] Server socket created on IP: ‘127.0.0.1‘.
210309 10:02:16 [Note] Event Scheduler: Loaded 0 events
210309 10:02:16 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210315 09:11:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210315 9:11:18 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9550 ...
210315 9:11:18 InnoDB: The InnoDB memory heap is disabled
210315 9:11:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210315 9:11:18 InnoDB: Compressed tables use zlib 1.2.7
210315 9:11:18 InnoDB: Using Linux native AIO
210315 9:11:18 InnoDB: Initializing buffer pool, size = 128.0M
210315 9:11:18 InnoDB: Completed initialization of buffer pool
210315 9:11:18 InnoDB: highest supported file format is Barracuda.
210315 9:11:19 InnoDB: Starting crash recovery from checkpoint LSN=462362593439
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210315 9:11:21 InnoDB: Starting final batch to recover 321 pages from redo log
210315 9:11:23 InnoDB: Waiting for the background threads to start
210315 9:11:24 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 462368690709
210315 9:11:24 [Note] Plugin ‘FEEDBACK‘ is disabled.
210315 9:11:24 [Note] Server socket created on IP: ‘127.0.0.1‘.
210315 9:11:25 [Note] Event Scheduler: Loaded 0 events
210315 9:11:25 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210316 08:49:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210316 8:49:23 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9553 ...
210316 8:49:24 InnoDB: The InnoDB memory heap is disabled
210316 8:49:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210316 8:49:24 InnoDB: Compressed tables use zlib 1.2.7
210316 8:49:24 InnoDB: Using Linux native AIO
210316 8:49:24 InnoDB: Initializing buffer pool, size = 128.0M
210316 8:49:24 InnoDB: Completed initialization of buffer pool
210316 8:49:24 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210316 8:49:24 InnoDB: Waiting for the background threads to start
210316 8:49:25 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 462378204220
210316 8:49:25 [Note] Plugin ‘FEEDBACK‘ is disabled.
210316 8:49:25 [Note] Server socket created on IP: ‘127.0.0.1‘.
210316 8:49:25 [Note] Event Scheduler: Loaded 0 events
210316 8:49:25 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210319 10:25:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210319 10:25:20 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9539 ...
210319 10:25:21 InnoDB: The InnoDB memory heap is disabled
210319 10:25:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210319 10:25:21 InnoDB: Compressed tables use zlib 1.2.7
210319 10:25:21 InnoDB: Using Linux native AIO
210319 10:25:21 InnoDB: Initializing buffer pool, size = 128.0M
210319 10:25:21 InnoDB: Completed initialization of buffer pool
210319 10:25:21 InnoDB: highest supported file format is Barracuda.
210319 10:25:21 InnoDB: Starting crash recovery from checkpoint LSN=463362456546
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: Database page corruption or a failed
InnoDB: file read of space 0 page 49152.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Database page corruption or a failed
InnoDB: file read of space 0 page 16384.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
210319 10:25:25 InnoDB: Starting final batch to recover 173 pages from redo log
210319 10:25:28 InnoDB: Waiting for the background threads to start
210319 10:25:29 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 463362605421
210319 10:25:29 [Note] Plugin ‘FEEDBACK‘ is disabled.
210319 10:25:29 [Note] Server socket created on IP: ‘127.0.0.1‘.
210319 10:25:29 [Note] Event Scheduler: Loaded 0 events
210319 10:25:29 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210323 11:51:00 [Note] /usr/libexec/mysqld: Normal shutdown
210323 11:51:00 [Note] Event Scheduler: Purging the queue. 0 events
210323 11:51:02 InnoDB: Starting shutdown...
210323 11:51:08 InnoDB: Shutdown completed; log sequence number 464169188159
210323 11:51:08 [Note] /usr/libexec/mysqld: Shutdown complete

210323 11:51:09 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210323 11:51:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210323 11:51:44 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9504 ...
210323 11:51:45 InnoDB: The InnoDB memory heap is disabled
210323 11:51:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210323 11:51:45 InnoDB: Compressed tables use zlib 1.2.7
210323 11:51:45 InnoDB: Using Linux native AIO
210323 11:51:45 InnoDB: Initializing buffer pool, size = 128.0M
210323 11:51:45 InnoDB: Completed initialization of buffer pool
210323 11:51:45 InnoDB: highest supported file format is Barracuda.
210323 11:51:49 InnoDB: Waiting for the background threads to start
210323 11:51:50 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 464169188159
210323 11:51:50 [Note] Plugin ‘FEEDBACK‘ is disabled.
210323 11:51:50 [Note] Server socket created on IP: ‘127.0.0.1‘.
210323 11:51:51 [Note] Event Scheduler: Loaded 0 events
210323 11:51:51 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210325 15:24:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210325 15:24:44 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9530 ...
210325 15:24:44 InnoDB: The InnoDB memory heap is disabled
210325 15:24:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210325 15:24:44 InnoDB: Compressed tables use zlib 1.2.7
210325 15:24:44 InnoDB: Using Linux native AIO
210325 15:24:44 InnoDB: Initializing buffer pool, size = 128.0M
210325 15:24:44 InnoDB: Completed initialization of buffer pool
210325 15:24:45 InnoDB: highest supported file format is Barracuda.
210325 15:24:45 InnoDB: Starting crash recovery from checkpoint LSN=464739113667
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210325 15:24:48 InnoDB: Error: page 1 log sequence number 464739235893
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:48 InnoDB: Error: page 4 log sequence number 464739238118
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:48 InnoDB: Error: page 5 log sequence number 464739238128
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:48 InnoDB: Error: page 32769 log sequence number 464739236377
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:48 InnoDB: Error: page 16385 log sequence number 464739238044
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:48 InnoDB: Error: page 340 log sequence number 464739231895
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:49 InnoDB: Error: page 65537 log sequence number 464739236287
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:49 InnoDB: Error: page 342 log sequence number 464739233480
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:49 InnoDB: Error: page 81921 log sequence number 464739238118
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:49 InnoDB: Error: page 49153 log sequence number 464739235975
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:49 InnoDB: Error: page 81950 log sequence number 464739240186
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:49 InnoDB: Error: page 16414 log sequence number 464739237962
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:50 InnoDB: Error: page 0 log sequence number 464739219980
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:50 InnoDB: Starting final batch to recover 165 pages from redo log
210325 15:24:50 InnoDB: Error: page 700 log sequence number 464739219980
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:50 InnoDB: Error: page 81920 log sequence number 464739219980
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:50 InnoDB: Error: page 82294 log sequence number 464739237674
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:50 InnoDB: Error: page 87617 log sequence number 464739237608
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:50 InnoDB: Error: page 31978 log sequence number 464739228630
InnoDB: is in the future! Current system log sequence number 464739210622.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
210325 15:24:51 InnoDB: Waiting for the background threads to start
210325 15:24:52 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 464739210622
210325 15:24:52 [Note] Plugin ‘FEEDBACK‘ is disabled.
210325 15:24:52 [Note] Server socket created on IP: ‘127.0.0.1‘.
210325 15:24:52 [Note] Event Scheduler: Loaded 0 events
210325 15:24:52 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB‘ socket: ‘/var/lib/mysql/mysql.sock‘ port: 3306 MariaDB Server
210325 15:28:30 InnoDB: Assertion failure in thread 140346101065472 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
210325 15:28:30 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.68-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=13
max_threads=153
thread_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466719 K bytes of memory
Hope that‘s ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x563caafcdcad]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x563caabe1975]
sigaction.c:0(__restore_rt)[0x7fa503a81630]
:0(__GI_raise)[0x7fa5021a8387]
:0(__GI_abort)[0x7fa5021a9a78]
/usr/libexec/mysqld(+0x63845f)[0x563caad7645f]
/usr/libexec/mysqld(+0x638f69)[0x563caad76f69]
/usr/libexec/mysqld(+0x73b504)[0x563caae79504]
/usr/libexec/mysqld(+0x730487)[0x563caae6e487]
/usr/libexec/mysqld(+0x63b17d)[0x563caad7917d]
/usr/libexec/mysqld(+0x62f0f6)[0x563caad6d0f6]
pthread_create.c:0(start_thread)[0x7fa503a79ea5]
/lib64/libc.so.6(clone+0x6d)[0x7fa50227096d]
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.
210325 15:28:31 mysqld_safe Number of processes running now: 0
210325 15:28:31 mysqld_safe mysqld restarted
210325 15:28:32 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 24479 ...
210325 15:28:32 InnoDB: The InnoDB memory heap is disabled
210325 15:28:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210325 15:28:32 InnoDB: Compressed tables use zlib 1.2.7
210325 15:28:32 InnoDB: Using Linux native AIO
210325 15:28:32 InnoDB: Initializing buffer pool, size = 128.0M
210325 15:28:32 InnoDB: Completed initialization of buffer pool
210325 15:28:32 InnoDB: highest supported file format is Barracuda.
210325 15:28:32 InnoDB: Starting crash recovery from checkpoint LSN=464739309996
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210325 15:28:35 InnoDB: Starting final batch to recover 17 pages from redo log
210325 15:28:36 InnoDB: Waiting for the background threads to start
210325 15:28:36 InnoDB: Assertion failure in thread 140198973257472 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
210325 15:28:36 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.68-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466719 K bytes of memory
Hope that‘s ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x56392d8c0cad]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x56392d4d4975]
sigaction.c:0(__restore_rt)[0x7f82ca630630]
:0(__GI_raise)[0x7f82c8d57387]
:0(__GI_abort)[0x7f82c8d58a78]
/usr/libexec/mysqld(+0x63845f)[0x56392d66945f]
/usr/libexec/mysqld(+0x638f69)[0x56392d669f69]
/usr/libexec/mysqld(+0x73b504)[0x56392d76c504]
/usr/libexec/mysqld(+0x730487)[0x56392d761487]
/usr/libexec/mysqld(+0x63b17d)[0x56392d66c17d]
/usr/libexec/mysqld(+0x62f0f6)[0x56392d6600f6]
pthread_create.c:0(start_thread)[0x7f82ca628ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f82c8e1f96d]
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.
210325 15:28:36 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210325 16:16:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210325 16:16:14 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9588 ...
210325 16:16:14 InnoDB: The InnoDB memory heap is disabled
210325 16:16:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210325 16:16:14 InnoDB: Compressed tables use zlib 1.2.7
210325 16:16:14 InnoDB: Using Linux native AIO
210325 16:16:14 InnoDB: Initializing buffer pool, size = 128.0M
210325 16:16:14 InnoDB: Completed initialization of buffer pool
210325 16:16:14 InnoDB: highest supported file format is Barracuda.
210325 16:16:14 InnoDB: Starting crash recovery from checkpoint LSN=464739309996
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210325 16:16:19 InnoDB: Starting final batch to recover 17 pages from redo log
210325 16:16:20 InnoDB: Waiting for the background threads to start
210325 16:16:20 InnoDB: Assertion failure in thread 140056383706880 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
210325 16:16:20 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x55b989722cad]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x55b989336975]
sigaction.c:0(__restore_rt)[0x7f619728a630]
:0(__GI_raise)[0x7f61959b1387]
:0(__GI_abort)[0x7f61959b2a78]
/usr/libexec/mysqld(+0x63845f)[0x55b9894cb45f]
/usr/libexec/mysqld(+0x638f69)[0x55b9894cbf69]
/usr/libexec/mysqld(+0x73b504)[0x55b9895ce504]
/usr/libexec/mysqld(+0x730487)[0x55b9895c3487]
/usr/libexec/mysqld(+0x63b17d)[0x55b9894ce17d]
/usr/libexec/mysqld(+0x62f0f6)[0x55b9894c20f6]
pthread_create.c:0(start_thread)[0x7f6197282ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f6195a7996d]
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.
210325 16:16:20 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210325 16:25:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210325 16:25:32 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9647 ...
210325 16:25:32 InnoDB: The InnoDB memory heap is disabled
210325 16:25:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210325 16:25:32 InnoDB: Compressed tables use zlib 1.2.7
210325 16:25:32 InnoDB: Using Linux native AIO
210325 16:25:32 InnoDB: Initializing buffer pool, size = 128.0M
210325 16:25:32 InnoDB: Completed initialization of buffer pool
210325 16:25:32 InnoDB: highest supported file format is Barracuda.
210325 16:25:32 InnoDB: Starting crash recovery from checkpoint LSN=464739309996
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210325 16:25:32 InnoDB: Starting final batch to recover 17 pages from redo log
210325 16:25:33 InnoDB: Waiting for the background threads to start
210325 16:25:33 InnoDB: Assertion failure in thread 139646751201024 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
210325 16:25:33 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x55a794e84cad]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x55a794a98975]
sigaction.c:0(__restore_rt)[0x7f02377ad630]
:0(__GI_raise)[0x7f0235ed4387]
:0(__GI_abort)[0x7f0235ed5a78]
/usr/libexec/mysqld(+0x63845f)[0x55a794c2d45f]
/usr/libexec/mysqld(+0x638f69)[0x55a794c2df69]
/usr/libexec/mysqld(+0x73b504)[0x55a794d30504]
/usr/libexec/mysqld(+0x730487)[0x55a794d25487]
/usr/libexec/mysqld(+0x63b17d)[0x55a794c3017d]
/usr/libexec/mysqld(+0x62f0f6)[0x55a794c240f6]
pthread_create.c:0(start_thread)[0x7f02377a5ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f0235f9c96d]
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.
210325 16:25:33 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210325 16:54:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210325 16:54:39 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 43416 ...
210325 16:54:39 InnoDB: The InnoDB memory heap is disabled
210325 16:54:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210325 16:54:39 InnoDB: Compressed tables use zlib 1.2.7
210325 16:54:39 InnoDB: Using Linux native AIO
210325 16:54:39 InnoDB: Initializing buffer pool, size = 128.0M
210325 16:54:39 InnoDB: Completed initialization of buffer pool
210325 16:54:39 InnoDB: highest supported file format is Barracuda.
210325 16:54:39 InnoDB: Starting crash recovery from checkpoint LSN=464739309996
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210325 16:54:39 InnoDB: Starting final batch to recover 17 pages from redo log
210325 16:54:39 InnoDB: Waiting for the background threads to start
210325 16:54:39 InnoDB: Assertion failure in thread 140458335811328 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
210325 16:54:39 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x55ec7a0afcad]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x55ec79cc3975]
sigaction.c:0(__restore_rt)[0x7fbf2120c630]
:0(__GI_raise)[0x7fbf1f933387]
:0(__GI_abort)[0x7fbf1f934a78]
/usr/libexec/mysqld(+0x63845f)[0x55ec79e5845f]
/usr/libexec/mysqld(+0x638f69)[0x55ec79e58f69]
/usr/libexec/mysqld(+0x73b504)[0x55ec79f5b504]
/usr/libexec/mysqld(+0x730487)[0x55ec79f50487]
/usr/libexec/mysqld(+0x63b17d)[0x55ec79e5b17d]
/usr/libexec/mysqld(+0x62f0f6)[0x55ec79e4f0f6]
pthread_create.c:0(start_thread)[0x7fbf21204ea5]
/lib64/libc.so.6(clone+0x6d)[0x7fbf1f9fb96d]
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.
210325 16:54:39 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210325 16:58:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210325 16:58:01 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 46310 ...
210325 16:58:01 InnoDB: The InnoDB memory heap is disabled
210325 16:58:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210325 16:58:01 InnoDB: Compressed tables use zlib 1.2.7
210325 16:58:01 InnoDB: Using Linux native AIO
210325 16:58:01 InnoDB: Initializing buffer pool, size = 128.0M
210325 16:58:01 InnoDB: Completed initialization of buffer pool
210325 16:58:01 InnoDB: highest supported file format is Barracuda.
210325 16:58:01 InnoDB: Starting crash recovery from checkpoint LSN=464739309996
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210325 16:58:01 InnoDB: Starting final batch to recover 17 pages from redo log
210325 16:58:02 InnoDB: Waiting for the background threads to start
210325 16:58:02 InnoDB: Assertion failure in thread 140109575857920 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
210325 16:58:02 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x558aa0a04cad]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x558aa0618975]
sigaction.c:0(__restore_rt)[0x7f6df1ca6630]
:0(__GI_raise)[0x7f6df03cd387]
:0(__GI_abort)[0x7f6df03cea78]
/usr/libexec/mysqld(+0x63845f)[0x558aa07ad45f]
/usr/libexec/mysqld(+0x638f69)[0x558aa07adf69]
/usr/libexec/mysqld(+0x73b504)[0x558aa08b0504]
/usr/libexec/mysqld(+0x730487)[0x558aa08a5487]
/usr/libexec/mysqld(+0x63b17d)[0x558aa07b017d]
/usr/libexec/mysqld(+0x62f0f6)[0x558aa07a40f6]
pthread_create.c:0(start_thread)[0x7f6df1c9eea5]
/lib64/libc.so.6(clone+0x6d)[0x7f6df049596d]
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.
210325 16:58:02 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
210325 17:05:05 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
210325 17:05:05 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 9753 ...
210325 17:05:05 InnoDB: The InnoDB memory heap is disabled
210325 17:05:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210325 17:05:05 InnoDB: Compressed tables use zlib 1.2.7
210325 17:05:05 InnoDB: Using Linux native AIO
210325 17:05:05 InnoDB: Initializing buffer pool, size = 128.0M
210325 17:05:05 InnoDB: Completed initialization of buffer pool
210325 17:05:05 InnoDB: highest supported file format is Barracuda.
210325 17:05:05 InnoDB: Starting crash recovery from checkpoint LSN=464739309996
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
210325 17:05:05 InnoDB: Starting final batch to recover 17 pages from redo log
210325 17:05:05 InnoDB: Waiting for the background threads to start
210325 17:05:05 InnoDB: Assertion failure in thread 139717676877568 in file trx0purge.c line 822
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
210325 17:05:05 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

经过我治兄弟的点拨，机器异常断电，造成mysql 数据文件损坏。启动失败

mysql磁盘问题记录

码农公寓

相关文章