Hi,
I have installed Zabbix 4.2.8 with MySQL 5.6.46-2 on CentOS 7.7.1908.
After a power failure I try to start the zabbix but have these error in front end:
and had this errors in log:
I have try to reinstal the mysql and also remove the ibdata1, ib_logfile0 and ib_logfile1. After that it has start but I doesn't had the dabase.
After that I tried to copy it back but had these errors:
It looks like that I have broken database from the power failure, but cant repair it, while the MySQL will not start.
Please can you help me how to resolve my problem?
Thanks.
I have installed Zabbix 4.2.8 with MySQL 5.6.46-2 on CentOS 7.7.1908.
After a power failure I try to start the zabbix but have these error in front end:
Code:
Error connecting to database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Code:
191104 10:28:57 mysqld_safe Logging to '/var/log/mysqld.log'. 191104 10:28:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2019-11-04 10:28:57 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentat$ 2019-11-04 10:28:57 0 [Note] /usr/sbin/mysqld (mysqld 5.6.46) starting as process 5833 ... 2019-11-04 10:28:57 5833 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000) 2019-11-04 10:28:57 5833 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000) 2019-11-04 10:28:57 5833 [Note] Plugin 'FEDERATED' is disabled. 2019-11-04 10:28:57 5833 [Note] InnoDB: Using atomics to ref count buffer pool pages 2019-11-04 10:28:57 5833 [Note] InnoDB: The InnoDB memory heap is disabled 2019-11-04 10:28:57 5833 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-11-04 10:28:57 5833 [Note] InnoDB: Memory barrier is not used 2019-11-04 10:28:57 5833 [Note] InnoDB: Compressed tables use zlib 1.2.11 2019-11-04 10:28:57 5833 [Note] InnoDB: Using Linux native AIO 2019-11-04 10:28:57 5833 [Note] InnoDB: Using CPU crc32 instructions 2019-11-04 10:28:57 5833 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2019-11-04 10:28:57 5833 [Note] InnoDB: Completed initialization of buffer pool 2019-11-04 10:28:57 5833 [Note] InnoDB: Highest supported file format is Barracuda. 2019-11-04 10:28:57 5833 [Note] InnoDB: Log scan progressed past the checkpoint lsn 673652497954 2019-11-04 10:28:57 5833 [Note] InnoDB: Database was not shutdown normally! 2019-11-04 10:28:57 5833 [Note] InnoDB: Starting crash recovery. 2019-11-04 10:28:57 5833 [Note] InnoDB: Reading tablespace information from the .ibd files... 2019-11-04 10:28:57 5833 [Note] InnoDB: Restoring possible half-written data pages 2019-11-04 10:28:57 5833 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 673657740800 InnoDB: Doing recovery: scanned up to log sequence number 673660220631 2019-11-04 10:28:58 5833 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 09:28:58 UTC - mysqld got signal 11 ; 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. 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. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68109 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 = 0 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x9377eb] /usr/sbin/mysqld(handle_fatal_signal+0x491)[0x6c29c1] /lib64/libpthread.so.0(+0xf5f0)[0x7fd7c39dc5f0] /usr/sbin/mysqld[0x9c0f73] /usr/sbin/mysqld[0x9c2cef] /usr/sbin/mysqld[0x9a95bb] /usr/sbin/mysqld[0x9ab21f] /usr/sbin/mysqld[0xa89abf] /usr/sbin/mysqld[0xad25d0] /usr/sbin/mysqld[0xa26e88] /lib64/libpthread.so.0(+0x7e65)[0x7fd7c39d4e65] /lib64/libc.so.6(clone+0x6d)[0x7fd7c269688d] 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. 191104 10:28:58 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
After that I tried to copy it back but had these errors:
Code:
191104 15:42:22 mysqld_safe Logging to '/var/log/mysqld.log'. 191104 15:42:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2019-11-04 15:42:22 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentat$ 2019-11-04 15:42:22 0 [Note] /usr/sbin/mysqld (mysqld 5.6.46) starting as process 21987 ... 2019-11-04 15:42:22 21987 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000) 2019-11-04 15:42:22 21987 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000) 2019-11-04 15:42:22 21987 [Note] Plugin 'FEDERATED' is disabled. 2019-11-04 15:42:22 21987 [Note] InnoDB: Using atomics to ref count buffer pool pages 2019-11-04 15:42:22 21987 [Note] InnoDB: The InnoDB memory heap is disabled 2019-11-04 15:42:22 21987 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-11-04 15:42:22 21987 [Note] InnoDB: Memory barrier is not used 2019-11-04 15:42:22 21987 [Note] InnoDB: Compressed tables use zlib 1.2.11 2019-11-04 15:42:22 21987 [Note] InnoDB: Using Linux native AIO 2019-11-04 15:42:22 21987 [Note] InnoDB: Using CPU crc32 instructions 2019-11-04 15:42:22 21987 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2019-11-04 15:42:22 21987 [Note] InnoDB: Completed initialization of buffer pool 2019-11-04 15:42:22 21987 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 2019-11-04 15:42:23 21987 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 2019-11-04 15:42:23 21987 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2019-11-04 15:42:23 21987 [Warning] InnoDB: New log files created, LSN=593878114327 2019-11-04 15:42:23 21987 [Note] InnoDB: Highest supported file format is Barracuda. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 7 log sequence number 673660135642 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 2 log sequence number 673652343856 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 4 log sequence number 673660149416 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 5 log sequence number 673660119400 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 6 log sequence number 673658272159 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 448 log sequence number 673653231854 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 356 log sequence number 673657121963 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 45 log sequence number 673651857040 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 415 log sequence number 673657435280 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 419 log sequence number 673656782219 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 990 log sequence number 673648072287 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 46 log sequence number 673651842978 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 986 log sequence number 673655249210 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2019-11-04 15:42:23 7efcdc601780 InnoDB: Error: page 47 log sequence number 673650015054 InnoDB: is in the future! Current system log sequence number 593878114828. 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.6/en/forcing-innodb-recovery.html InnoDB: for more information. . . . . InnoDB: 18 transaction(s) which must be rolled back or cleaned up InnoDB: in total 0 row operations to undo InnoDB: Trx id counter is 662131456 InnoDB: Cleaning up trx with id 662128564 2019-11-04 15:42:23 7efcdc601780 InnoDB: Assertion failure in thread 139624494143360 in file trx0trx.cc line 300 InnoDB: Failing assertion: trx->update_undo == NULL 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.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 14:42:23 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. 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. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68109 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 = 0 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x9377eb] /usr/sbin/mysqld(handle_fatal_signal+0x491)[0x6c29c1] /lib64/libpthread.so.0(+0xf5f0)[0x7efcdc1e95f0] /lib64/libc.so.6(gsignal+0x37)[0x7efcdaddb337] /lib64/libc.so.6(abort+0x148)[0x7efcdaddca28] /usr/sbin/mysqld[0xa4538a] /usr/sbin/mysqld[0xa3c959] /usr/sbin/mysqld[0x9aed31] /usr/sbin/mysqld[0xa29de4] /usr/sbin/mysqld[0x965b88] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x602bc8] /usr/sbin/mysqld[0x74bd00] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x950)[0x752010] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8a0)[0x5fc560] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7efcdadc7505] /usr/sbin/mysqld[0x5eee7d] 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. 191104 15:42:23 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Please can you help me how to resolve my problem?
Thanks.
Comment