Hi, is it possible to upgrade the mariadb version, current is "Server version: 10.1.25-MariaDB". Reason for asking is, we encountered some issue when we created a trigger insert on the mboxgroup database, but it keeps crashing the db, on 10.1.5, but we have no issue on older zimbra like 8.8.x. Found some suggestion on mariadb forum to upgrade. How can we upgrade in case it's possible.
Version: '10.1.25-MariaDB' socket: '/opt/zimbra/data/tmp/mysql/mysql.sock' port: 7306 Zimbra MariaDB binary distribution
250303 5:37:27 [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=31997952
max_used_connections=1
max_threads=112
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 7133133 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x55c68edee008
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 = 0x7ff264a60138 thread_stack 0x48400
*** buffer overflow detected ***: terminated
Fatal signal 6 while backtracing
250303 05:37:28 mysqld_safe Number of processes running now: 0
250303 05:37:28 mysqld_safe mysqld restarted
2025-03-03 5:37:28 140582914166464 [Note] /opt/zimbra/common/sbin/mysqld (mysqld 10.1.25-MariaDB) starting as process 3415906 ...
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: The InnoDB memory heap is disabled
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Compressed tables use zlib 1.2.3
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Using Linux native AIO
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Using SSE crc32 instructions
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Initializing buffer pool, size = 3.2G
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Completed initialization of buffer pool
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Highest supported file format is Barracuda.
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: The log sequence number 64012642 in ibdata file do not match the log sequence number 69135189 in the ib_logfiles!
2025-03-03 5:37:29 140582914166464 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2025-03-03 5:37:30 140582914166464 [Note] InnoDB: 128 rollback segment(s) are active.
2025-03-03 5:37:30 140582914166464 [Note] InnoDB: Waiting for purge to start
2025-03-03 5:37:30 140582914166464 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.0 started; log sequence number 69135189
2025-03-03 5:37:30 140579148187200 [Note] InnoDB: Dumping buffer pool(s) not yet started
2025-03-03 5:37:30 140582914166464 [Note] Plugin 'FEEDBACK' is disabled.
2025-03-03 5:37:30 140582914166464 [Note] Recovering after a crash using tc.log
2025-03-03 5:37:30 140582914166464 [Note] Starting crash recovery...
2025-03-03 5:37:30 140582914166464 [Note] Crash recovery finished.
2025-03-03 5:37:30 140582914166464 [Note] Server socket created on IP: '127.0.0.1'.
2025-03-03 5:37:30 140582914166464 [Note] /opt/zimbra/common/sbin/mysqld: ready for connections.
Version: '10.1.25-MariaDB' socket: '/opt/zimbra/data/tmp/mysql/mysql.sock' port: 7306 Zimbra MariaDB binary distribution
250303 5:38:28 [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.
Version: '10.1.25-MariaDB' socket: '/opt/zimbra/data/tmp/mysql/mysql.sock' port: 7306 Zimbra MariaDB binary distribution
250303 5:37:27 [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=31997952
max_used_connections=1
max_threads=112
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 7133133 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x55c68edee008
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 = 0x7ff264a60138 thread_stack 0x48400
*** buffer overflow detected ***: terminated
Fatal signal 6 while backtracing
250303 05:37:28 mysqld_safe Number of processes running now: 0
250303 05:37:28 mysqld_safe mysqld restarted
2025-03-03 5:37:28 140582914166464 [Note] /opt/zimbra/common/sbin/mysqld (mysqld 10.1.25-MariaDB) starting as process 3415906 ...
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: The InnoDB memory heap is disabled
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Compressed tables use zlib 1.2.3
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Using Linux native AIO
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Using SSE crc32 instructions
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Initializing buffer pool, size = 3.2G
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Completed initialization of buffer pool
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: Highest supported file format is Barracuda.
2025-03-03 5:37:28 140582914166464 [Note] InnoDB: The log sequence number 64012642 in ibdata file do not match the log sequence number 69135189 in the ib_logfiles!
2025-03-03 5:37:29 140582914166464 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2025-03-03 5:37:30 140582914166464 [Note] InnoDB: 128 rollback segment(s) are active.
2025-03-03 5:37:30 140582914166464 [Note] InnoDB: Waiting for purge to start
2025-03-03 5:37:30 140582914166464 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.0 started; log sequence number 69135189
2025-03-03 5:37:30 140579148187200 [Note] InnoDB: Dumping buffer pool(s) not yet started
2025-03-03 5:37:30 140582914166464 [Note] Plugin 'FEEDBACK' is disabled.
2025-03-03 5:37:30 140582914166464 [Note] Recovering after a crash using tc.log
2025-03-03 5:37:30 140582914166464 [Note] Starting crash recovery...
2025-03-03 5:37:30 140582914166464 [Note] Crash recovery finished.
2025-03-03 5:37:30 140582914166464 [Note] Server socket created on IP: '127.0.0.1'.
2025-03-03 5:37:30 140582914166464 [Note] /opt/zimbra/common/sbin/mysqld: ready for connections.
Version: '10.1.25-MariaDB' socket: '/opt/zimbra/data/tmp/mysql/mysql.sock' port: 7306 Zimbra MariaDB binary distribution
250303 5:38:28 [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.
Statistics: Posted by zimuzer — Tue Mar 04, 2025 2:07 pm