Code: Select all
[zimbra@mail ~]$ cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
51.158.xx.xx mail.XXX.com mail
51.158.xx.xx web-mail.XXX.com web-mail
192.168.168.168 mail.XXX.com mail
10.70.150.43 mail.XXX.com mail
[zimbra@mail ~]$
Code: Select all
[zimbra@mail tmp]$ zmcontrol restart
Host mail.XXX.com
Stopping zmconfigd...Done.
Stopping zimlet webapp...Done.
Stopping zimbraAdmin webapp...Done.
Stopping zimbra webapp...Done.
Stopping service webapp...Done.
Stopping stats...Done.
Stopping mta...Done.
Stopping spell...Done.
Stopping snmp...Done.
Stopping cbpolicyd...Done.
Stopping archiving...Done.
Stopping opendkim...Done.
Stopping amavis...Done.
Stopping antivirus...Done.
Stopping antispam...Done.
Stopping proxy...Done.
Stopping memcached...Done.
Stopping mailbox...Done.
Stopping logger...Done.
Stopping dnscache...Done.
Stopping ldap...Done.
Host mail.XXX.com
Starting ldap...Done.
Search error: Unable to determine enabled services from ldap.
Unable to determine enabled services. Cache is out of date or doesn't exist.
[zimbra@mail tmp]$
Code: Select all
[zimbra@mail ~]$ /opt/zimbra/libexec/zmsetservername -f -n mail.XXX.com
Getting local config zimbra_server_hostname=mail.XXX.com
Hostname is already mail.XXX.com.
Getting local config zimbra_ldap_userdn=uid=zimbra,cn=admins,cn=zimbra
Getting local config zimbra_ldap_password=XXXXX
Getting local config ldap_is_master=true
Getting local config ldap_url=ldap://mail.XXX.com:389
Getting local config ldap_master_url=ldap://mail.XXX.com:389
Getting local config ldap_starttls_supported=0
Starting ldap...already running.
Renaming mail.XXXX.com to mail.XXX.com
Shutting down zimbra...done.
Getting local config ldap_host=mail.XXX.com
Getting local config av_notify_user=admin@XXX.com
Getting local config av_notify_domain=XXX.com
Getting local config snmp_trap_host=mail.XXX.com
Getting local config smtp_source=admin@XXX.com
Getting local config smtp_destination=admin@XXX.com
Starting ldap...done.
Failed to get server config for mail.XXX.com.
ldap bind failed for uid=zimbra,cn=admins,cn=zimbra
ldap bind failed for uid=zimbra,cn=admins,cn=zimbraldap bind failed for uid=zimbra,cn=admins,cn=zimbraServices:
[zimbra@mail ~]$
Code: Select all
220108 15:41:49 mysqld_safe Starting mysqld daemon with databases from /opt/zimbra/db/data
2022-01-08 15:41:49 139717620930432 [Note] /opt/zimbra/common/sbin/mysqld (mysqld 10.1.25-MariaDB) starting as process 197838 ...
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: Using Linux native AIO
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: Using SSE crc32 instructions
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: Initializing buffer pool, size = 2.3G
2022-01-08 15:41:49 139717620930432 [Note] InnoDB: Completed initialization of buffer pool
2022-01-08 15:41:49 139717620930432 [ERROR] InnoDB: Log file ./ib_logfile0 size 524314036 is not a multiple of innodb_page_size
2022-01-08 15:41:49 139717620930432 [ERROR] Plugin 'InnoDB' init function returned error.
2022-01-08 15:41:49 139717620930432 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-01-08 15:41:49 139717620930432 [Note] Plugin 'FEEDBACK' is disabled.
2022-01-08 15:41:49 139717620930432 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-01-08 15:41:49 139717620930432 [ERROR] Aborting
220108 15:41:49 mysqld_safe mysqld from pid file /opt/zimbra/log/mysql.pid ended
Code: Select all
[root@mail data]# pwd
/opt/zimbra/db/data
[root@mail data]# rm -rf ib_logfile*
Code: Select all
220108 15:52:26 mysqld_safe Starting mysqld daemon with databases from /opt/zimbra/db/data
2022-01-08 15:52:26 140355787757440 [Note] /opt/zimbra/common/sbin/mysqld (mysqld 10.1.25-MariaDB) starting as process 198834 ...
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Using Linux native AIO
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Using SSE crc32 instructions
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Initializing buffer pool, size = 2.3G
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Completed initialization of buffer pool
2022-01-08 15:52:26 140355787757440 [Note] InnoDB: Setting log file ./ib_logfile101 size to 500 MB
2022-01-08 15:52:28 140355787757440 [Note] InnoDB: Setting log file ./ib_logfile1 size to 500 MB
2022-01-08 15:52:30 140355787757440 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2022-01-08 15:52:30 140355787757440 [Warning] InnoDB: New log files created, LSN=670990738
2022-01-08 15:52:30 140355787757440 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-08 15:52:30 140355787757440 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:52:30 140355787757440 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace ./ibdata1 page [page id: space=0, page number=573]. You may have to recover from a backup.
2022-01-08 15:52:30 7fa720df1780 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000743a0e3951389f379336e1368c35dd352f348533d33327327331c3310d30632faf2eff2e4f2da32cf42c412b822b2d2a142957289e2817279226e025d9252a247f23d22323226f21bf210e205d1fb31eff1e501d9f1cee1c3d1b871a411a73195a189d17eb16df162d15d81529147b13
InnoDB: End of page dump
2022-01-08 15:52:31 7fa720df1780 InnoDB: uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 2697113374, innodb 2698999090, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 2697113374, innodb 1371122432, none 3735928559, page LSN 0 0, low 4 bytes of LSN at page end 0, page number (if stored to page already) 0, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: page type 0 meaning ALLOCATED
InnoDB: Page may be a freshly allocated page
2022-01-08 15:52:31 140355787757440 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html for information about forcing recovery.
2022-01-08 15:52:31 140355787757440 [ERROR] InnoDB: Ending processing because of a corrupt database page.
2022-01-08 15:52:31 7fa720df1780 InnoDB: Assertion failure in thread 140355787757440 in file ha_innodb.cc line 21945
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.
220108 15:52:31 [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 https://mariadb.com/kb/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: 10.1.25-MariaDB
key_buffer_size=134217728
read_buffer_size=1048576
max_used_connections=0
max_threads=112
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 362733 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 0x48400
/opt/zimbra/common/sbin/mysqld(my_print_stacktrace+0x2e)[0x558b62f2606e]
/opt/zimbra/common/sbin/mysqld(handle_fatal_signal+0x53b)[0x558b62b13a1b]
/lib64/libpthread.so.0(+0x12c20)[0x7fa720775c20]
/lib64/libc.so.6(gsignal+0x10f)[0x7fa71ecc537f]
/lib64/libc.so.6(abort+0x127)[0x7fa71ecafdb5]
/opt/zimbra/common/sbin/mysqld(+0x7718ad)[0x558b62d028ad]
/opt/zimbra/common/sbin/mysqld(+0x8ba1e8)[0x558b62e4b1e8]
/opt/zimbra/common/sbin/mysqld(+0x8d24ab)[0x558b62e634ab]
/opt/zimbra/common/sbin/mysqld(+0x8d3603)[0x558b62e64603]
/opt/zimbra/common/sbin/mysqld(+0x8b1cce)[0x558b62e42cce]
/opt/zimbra/common/sbin/mysqld(+0x8915eb)[0x558b62e225eb]
/opt/zimbra/common/sbin/mysqld(+0x89e06a)[0x558b62e2f06a]
/opt/zimbra/common/sbin/mysqld(+0x8f6182)[0x558b62e87182]
/opt/zimbra/common/sbin/mysqld(+0x8f71e4)[0x558b62e881e4]
/opt/zimbra/common/sbin/mysqld(+0x8d8b4f)[0x558b62e69b4f]
/opt/zimbra/common/sbin/mysqld(+0x84d8ef)[0x558b62dde8ef]
/opt/zimbra/common/sbin/mysqld(+0x763eae)[0x558b62cf4eae]
/opt/zimbra/common/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x6c)[0x558b62b15b5c]
/opt/zimbra/common/sbin/mysqld(+0x40f695)[0x558b629a0695]
/opt/zimbra/common/sbin/mysqld(_Z11plugin_initPiPPci+0x96a)[0x558b629a17fa]
/opt/zimbra/common/sbin/mysqld(+0x36e410)[0x558b628ff410]
mysys/stacktrace.c:268(my_print_stacktrace)[0x558b62902b93]
sql/signal_handler.cc:168(handle_fatal_signal)[0x7fa71ecb1493]
/opt/zimbra/common/sbin/mysqld(_start+0x2e)[0x558b628f6ade]
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.
220108 15:52:31 mysqld_safe mysqld from pid file /opt/zimbra/log/mysql.pid ended
Code: Select all
[mysqld]
innodb_force_recovery = 1
Code: Select all
220108 15:54:12 mysqld_safe Starting mysqld daemon with databases from /opt/zimbra/db/data
2022-01-08 15:54:12 139635865540480 [Note] /opt/zimbra/common/sbin/mysqld (mysqld 10.1.25-MariaDB) starting as process 199355 ...
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Using Linux native AIO
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Using SSE crc32 instructions
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Initializing buffer pool, size = 2.3G
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Completed initialization of buffer pool
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-08 15:54:12 139635865540480 [Note] InnoDB: The log sequence number 670990738 in ibdata file do not match the log sequence number 670990860 in the ib_logfiles!
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:524 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:524 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:562 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:562 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:558 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:558 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 1701666665 and the end 0 do not match.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:575 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:575 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:534 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:534 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:692 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:692 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:662 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:662 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:704 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:704 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:296 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:296 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:297 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:297 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:817 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:817 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:295 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:295 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:408 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:408 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:415 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:415 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:389 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:389 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 55265091 and the end 0 do not match.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:460 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:460 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 4294967295 and the end 0 do not match.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:498 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:498 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 0:479 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 0:479 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 16783712 and the end 0 do not match.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 35:53 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 35:53 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 1664314465 and the end 2960261120 do not match.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 35:31 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 35:31 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 35:63 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 35:63 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 1 and the end 1179648 do not match.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 35:41 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Recovered page 35:41 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 1480684337 and the end 1664314465 do not match.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Trying to recover page 35:80 from the doublewrite buffer.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Log sequence number at the start 670962395 and the end 0 do not match.
2022-01-08 15:54:13 139635865540480 [Warning] InnoDB: A doublewrite copy of page 35:80 is corrupted.
2022-01-08 15:54:13 139635865540480 [Note] InnoDB: Checksum fields zero but page is not empty.
2022-01-08 15:54:13 139635865540480 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace ./ibdata1 page [page id: space=0, page number=573]. You may have to recover from a backup.
2022-01-08 15:54:13 7eff8229d780 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000743a0e3951389f379336e1368c35dd352f348533d33327327331c3310d30632faf2eff2e4f2da32cf42c412b822b2d2a142957289e2817279226e025d9252a247f23d22323226f21bf210e205d1fb31eff1e501d9f1cee1c3d1b871a411a73195a189d17eb16df162d15d81529147b13d1131f127311bf110f10590faf0efb0e4b0d9b0cef0c400b8d0ace0a79096008a307ea076306de062c0525047603cb031e026f01bb010b00656ccd7123024209d9c0172d920000023dffffffff000001750000000000811ef745bf000000000000000000000000001c3b6b00d61e881cf2000000050000006a00000000000000000000000000000000000300000000000000000000000000000000000000000801000003008c696e66696d756d000903000803000073757072656d756d00332f2b27231d1610080000101300ce000000000000000b000000000000000b000000000300800000012d017749445f494e440000000100000003000000000000012e34302c28241d161008000018130111000000000000000b000000000000000c000000000300800000012d01a5464f525f494e440000000100000000000000000000012f34302c28241d161008000020130154000000000000000b000000000000000d000000000300800000012d01d35245465f494e4400000001000000000000000000000130332f2b27231d161008040028130196000000000000000c000000000000000e000000000300800000012d026d49445f494e4400000002000000030000000000000131423e3a36321d1610080000301301e7000000000000000d000000000000000f000000000301810000013201665359535f5441424c455350414345535f535041434500000001000000030000000000000133403c3834301d161008000038130236000000000000000e0000000000000010000000000301810000013201d35359535f4441544146494c45535f53504143450000000100000003000000000000013434302c28241d161008000040130279000000000000000f0000000000000011000000000302820000013501c65052494d4152590000000200000003000000010000000334302c28241d1610080400481302bc00000000000000100000000000000012000000000303830000013601f05052494d4152590000000400000003000000020000000334302c28241d1610080000501302ff00000000000000110000000000000013000000000304840000013701985052494d4152590000000200000003000000030000000334302c28241d16100800005813034200000000000000120000000000000014000000000904840000013702245052494d41525900000001000000030000000400000003332f2b27231d1610080000601303840000000000000012000000000000001500000000090484000001370252695f6e616d6500000001000000020000000400000004332f2b27231d1610080400681303c60000000000000012000000000000001600000000090484000001370280695f70617468000000010000000200000004000000053c3834302c1d16100800007013041100000000000000130000000000000017000000000907870000013a019a47454e5f434c5553545f494e44455800000000000000010000000500000003403c3834301d16100800007813046000000000000000130000000000000018000000000907870000013a01b3695f6d6573736167655f766f6c756d655f6964000000010000000000000005000000044a46423e3a1d1610080000801304b9000000000000001300000000
InnoDB: End of page dump
2022-01-08 15:54:15 7eff8229d780 InnoDB: uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 2697113374, innodb 2698999090, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 2697113374, innodb 1371122432, none 3735928559, page LSN 0 0, low 4 bytes of LSN at page end 0, page number (if stored to page already) 0, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: page type 0 meaning ALLOCATED
InnoDB: Page may be a freshly allocated page
220108 15:54:15 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/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: 10.1.25-MariaDB
key_buffer_size=134217728
read_buffer_size=1048576
max_used_connections=0
max_threads=112
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 362733 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 0x48400
/opt/zimbra/common/sbin/mysqld(my_print_stacktrace+0x2e)[0x55732ba2a06e]
/opt/zimbra/common/sbin/mysqld(handle_fatal_signal+0x53b)[0x55732b617a1b]
/lib64/libpthread.so.0(+0x12c20)[0x7eff81c21c20]
/opt/zimbra/common/sbin/mysqld(+0x7d6c3d)[0x55732b86bc3d]
/opt/zimbra/common/sbin/mysqld(+0x89150c)[0x55732b92650c]
/opt/zimbra/common/sbin/mysqld(+0x89e06a)[0x55732b93306a]
/opt/zimbra/common/sbin/mysqld(+0x8f6182)[0x55732b98b182]
/opt/zimbra/common/sbin/mysqld(+0x8f71e4)[0x55732b98c1e4]
/opt/zimbra/common/sbin/mysqld(+0x8d8b4f)[0x55732b96db4f]
mysys/stacktrace.c:268(my_print_stacktrace)[0x55732b8e28ef]
include/page0page.ic:679(page_dir_slot_get_rec)[0x55732b7f8eae]
btr/btr0cur.cc:837(btr_cur_search_to_nth_level(dict_index_t*, unsigned long, dtuple_t const*, unsigned long, unsigned long, btr_cur_t*, unsigned long, char const*, unsigned long, mtr_t*))[0x55732b619b5c]
include/ut0byte.ic:133(ut_align_offset)[0x55732b4a4695]
srv/srv0start.cc:2624(innobase_start_or_create_for_mysql())[0x55732b4a57fa]
handler/ha_innodb.cc:4439(innobase_init(void*))[0x55732b403410]
sql/handler.cc:513(ha_initialize_handlerton(st_plugin_int*))[0x55732b406b93]
sql/sql_plugin.cc:1406(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**, bool))[0x7eff8015d493]
sql/mysqld.cc:5148(init_server_components())[0x55732b3faade]
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.
220108 15:54:16 mysqld_safe mysqld from pid file /opt/zimbra/log/mysql.pid ended
Code: Select all
[root@mail data]# rm -rf ib*
Code: Select all
220108 17:17:29 mysqld_safe Starting mysqld daemon with databases from /opt/zimbra/db/data
2022-01-08 17:17:29 140235712141184 [Note] /opt/zimbra/common/sbin/mysqld (mysqld 10.1.25-MariaDB) starting as process 206477 ...
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Using Linux native AIO
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Using SSE crc32 instructions
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Initializing buffer pool, size = 2.3G
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Completed initialization of buffer pool
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Setting file ./ibdata1 size to 10 MB
2022-01-08 17:17:30 140235712141184 [Note] InnoDB: Setting log file ./ib_logfile101 size to 512 MB
2022-01-08 17:17:31 140235712141184 [Note] InnoDB: Setting log file ./ib_logfile1 size to 512 MB
2022-01-08 17:17:33 140235712141184 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2022-01-08 17:17:33 140235712141184 [Warning] InnoDB: New log files created, LSN=45883
2022-01-08 17:17:33 140235712141184 [Note] InnoDB: Doublewrite buffer not found: creating new
2022-01-08 17:17:33 140235712141184 [Note] InnoDB: Doublewrite buffer created
2022-01-08 17:17:33 140235712141184 [Note] InnoDB: 1 rollback segment(s) are active.
2022-01-08 17:17:33 140235712141184 [ERROR] InnoDB: Database creation was aborted at /home/build/git/88/packages/thirdparty/mariadb/build/RHEL8_64/zimbra-mariadb/rpm/BUILD/mariadb-10.1.25/storage/xtradb/srv/srv0start.cc [2943] with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
2022-01-08 17:17:33 140235712141184 [ERROR] Plugin 'InnoDB' init function returned error.
2022-01-08 17:17:33 140235712141184 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-01-08 17:17:33 140235712141184 [Note] Plugin 'FEEDBACK' is disabled.
2022-01-08 17:17:33 140235712141184 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-01-08 17:17:33 140235712141184 [ERROR] Aborting
220108 17:17:33 mysqld_safe mysqld from pid file /opt/zimbra/log/mysql.pid ended