hi all
in this day we have problem on our zabbix server , on wall view we lost map and when I check zabbix server's found that zabbix server are stoped ,
during troubleshooting check I see that mariadb sql is crached with the error below ,
I am trying upgrade mariadb to last version using yum update mariadb ,
after update steel have a problem
p.s : in another time I try to recover my clone backup of our server but after one day mysql crached again ,
anyone can help me what happen to our server ?
Server : centos 7.3 ( upgrade to 7.4 )
Zabbix server : 3.4
in this day we have problem on our zabbix server , on wall view we lost map and when I check zabbix server's found that zabbix server are stoped ,
during troubleshooting check I see that mariadb sql is crached with the error below ,
I am trying upgrade mariadb to last version using yum update mariadb ,
after update steel have a problem
p.s : in another time I try to recover my clone backup of our server but after one day mysql crached again ,
anyone can help me what happen to our server ?
Server : centos 7.3 ( upgrade to 7.4 )
Zabbix server : 3.4
PHP Code:
###/var/log/mariadb/mariadb.log
171016 08:00:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
171016 8:00:10 [Note] /usr/libexec/mysqld (mysqld 5.5.56-MariaDB) starting as process 38260 ...
171016 8:00:10 InnoDB: The InnoDB memory heap is disabled
171016 8:00:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
171016 8:00:10 InnoDB: Compressed tables use zlib 1.2.7
171016 8:00:10 InnoDB: Using Linux native AIO
171016 8:00:10 InnoDB: Initializing buffer pool, size = 128.0M
171016 8:00:10 InnoDB: Completed initialization of buffer pool
171016 8:00:10 InnoDB: highest supported file format is Barracuda.
171016 8:00:10 InnoDB: Starting crash recovery from checkpoint LSN=860866004661
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
171016 8:00:10 InnoDB: Starting final batch to recover 1921 pages from redo log
171016 8:00:11 InnoDB: Waiting for the background threads to start
171016 8:00:12 InnoDB: Assertion failure in thread 139977639614208 in file btr0btr.c line 3380
InnoDB: Failing assertion: btr_page_get_next(merge_page, mtr) == buf_block_get_page_no(block)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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.
171016 8:00:12 [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.56-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 = 466711 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
PHP Code:
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 104797810688
InnoDB: Doing recovery: scanned up to log sequence number 104798046742
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 53044165 row operations to undo
InnoDB: Trx id counter is 3558500
170301 11:28:58 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting in background the rollback of uncommitted transactions
170301 11:29:00 InnoDB: Rolling back trx with id 3546DD4, 53044165 rows to undo
InnoDB: Progress in percents: 1170301 11:29:00 InnoDB: Waiting for the background threads to start
170301 11:29:01 Percona XtraDB (http://www.percona.com) 5.5.49-MariaDB-38.0 started; log sequence number 104798046742
170301 11:29:01 [Note] Plugin 'FEEDBACK' is disabled.
170301 11:29:01 [Note] Server socket created on IP: '0.0.0.0'.
170301 11:29:01 [Note] Event Scheduler: Loaded 0 events
170301 11:29:01 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.52-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 3546DD4 completed
170301 12:02:04 InnoDB: Rollback of non-prepared transactions completed
170928 10:12:24 [Note] /usr/libexec/mysqld: Normal shutdown
170928 10:12:24 [Note] Event Scheduler: Purging the queue. 0 events
170928 10:12:24 InnoDB: Starting shutdown...
170928 10:12:24 InnoDB: Waiting for 201 pages to be flushed
170928 10:12:25 InnoDB: Shutdown completed; log sequence number 832554350725
170928 10:12:25 [Note] /usr/libexec/mysqld: Shutdown complete
170928 10:12:26 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
170928 10:49:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170928 10:49:49 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 1351 ...
170928 10:49:49 InnoDB: The InnoDB memory heap is disabled
170928 10:49:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170928 10:49:49 InnoDB: Compressed tables use zlib 1.2.7
170928 10:49:49 InnoDB: Using Linux native AIO
170928 10:49:49 InnoDB: Initializing buffer pool, size = 128.0M
170928 10:49:49 InnoDB: Completed initialization of buffer pool
170928 10:49:49 InnoDB: highest supported file format is Barracuda.
170928 10:49:51 InnoDB: Waiting for the background threads to start
170928 10:49:52 Percona XtraDB (http://www.percona.com) 5.5.49-MariaDB-38.0 started; log sequence number 832554350725
170928 10:49:52 [Note] Plugin 'FEEDBACK' is disabled.