Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
5.5(EOL)
-
None
-
[root@freepbx ~]# systemctl status mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-08-19 08:15:20 CAT; 35min ago
Process: 19022 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
Process: 19021 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
Process: 18987 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 19021 (code=exited, status=0/SUCCESS)
Aug 19 08:15:19 freepbx.sangoma.local systemd[1]: Starting MariaDB database s...
Aug 19 08:15:19 freepbx.sangoma.local mariadb-prepare-db-dir[18987]: Database...
Aug 19 08:15:19 freepbx.sangoma.local mysqld_safe[19021]: 250819 08:15:19 mys...
Aug 19 08:15:19 freepbx.sangoma.local mysqld_safe[19021]: 250819 08:15:19 mys...
Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: mariadb.service: control pr...
Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: Failed to start MariaDB dat...
Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: Unit mariadb.service entere...
Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[ root@freepbx ~]# systemctl status mariadb.service ● mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2025-08-19 08:15:20 CAT; 35min ago Process: 19022 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE) Process: 19021 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS) Process: 18987 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS) Main PID: 19021 (code=exited, status=0/SUCCESS) Aug 19 08:15:19 freepbx.sangoma.local systemd[1]: Starting MariaDB database s... Aug 19 08:15:19 freepbx.sangoma.local mariadb-prepare-db-dir[18987]: Database... Aug 19 08:15:19 freepbx.sangoma.local mysqld_safe[19021]: 250819 08:15:19 mys... Aug 19 08:15:19 freepbx.sangoma.local mysqld_safe[19021]: 250819 08:15:19 mys... Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: mariadb.service: control pr... Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: Failed to start MariaDB dat... Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: Unit mariadb.service entere... Aug 19 08:15:20 freepbx.sangoma.local systemd[1]: mariadb.service failed. Hint: Some lines were ellipsized, use -l to show in full.
-
Not for Release Notes
Description
Server version: 5.5.65-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)[0x56505ed1fefd]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x56505e933805]
sigaction.c:0(__restore_rt)[0x7f012f007630]
:0(__GI_raise)[0x7f012d72f387]
:0(__GI_abort)[0x7f012d730a78]
/usr/libexec/mysqld(+0x2d2301)[0x56505e762301]
/usr/libexec/mysqld(+0x65295d)[0x56505eae295d]
/usr/libexec/mysqld(+0x644b93)[0x56505ead4b93]
/usr/libexec/mysqld(+0x6459fc)[0x56505ead59fc]
/usr/libexec/mysqld(+0x64815e)[0x56505ead815e]
/usr/libexec/mysqld(+0x631475)[0x56505eac1475]
/usr/libexec/mysqld(+0x5e8324)[0x56505ea78324]
/usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x56505e935888]
/usr/libexec/mysqld(+0x37c4a6)[0x56505e80c4a6]
/usr/libexec/mysqld(_Z11plugin_initPiPPci+0x559)[0x56505e8119c9]
/usr/libexec/mysqld(+0x2ed02a)[0x56505e77d02a]
/usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x5c2)[0x56505e7801c2]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f012d71b555]
/usr/libexec/mysqld(+0x2e71cd)[0x56505e7771cd]
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.
250505 12:06:29 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
250505 13:10:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
250505 13:10:10 [Note] /usr/libexec/mysqld (mysqld 5.5.65-MariaDB) starting as process 1360 ...
250505 13:10:10 InnoDB: The InnoDB memory heap is disabled
250505 13:10:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
250505 13:10:10 InnoDB: Compressed tables use zlib 1.2.7
250505 13:10:10 InnoDB: Using Linux native AIO
250505 13:10:10 InnoDB: Initializing buffer pool, size = 128.0M
250505 13:10:10 InnoDB: Completed initialization of buffer pool
250505 13:10:10 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...
250505 13:10:14 InnoDB: Assertion failure in thread 139752348661888 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.
250505 13:10:14 [ERROR] mysqld got signal 6 ;
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-