Your message dated Sun, 25 May 2025 13:15:58 -0700
with message-id
<CAOU6tABhhGBKW7NmMg3fMpbvwzMSU_mEYWmEVW=rzkzzxam...@mail.gmail.com>
and subject line Re: Bug#1058706: mariadb-server-core: mariadbd fails to start
on fresh install on armel
has caused the Debian Bug report #1058706,
regarding mariadb-server-core: mariadbd fails to start on fresh install on armel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server-core
Version: 1:10.11.6-1
Severity: important
Dear Maintainer,
On a fresh install of mariadb on armel architecture, mariadb fails to start.
This happens with the version of mariadb in Debian stable (bookworm, version
1:10.11.4-1~deb12u1) and Debian testing (trixie, version 1:10.11.6-1). There
were no existing databases, and the folder /var/lib/mysql did not exist prior
to the install.
Here is the error shown when dpkg perform the install and tries to start
mariadbd:
Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . .
231214 14:51:33 mysqld_safe Can't log to error log and syslog at the same time.
Remove all --log-error configuration options for --syslog to take effect.
231214 14:51:33 mysqld_safe Logging to '/tmp/tmp.AUoKfplrEX.err'.
231214 14:51:33 mysqld_safe Starting mariadbd daemon with databases from
/var/lib/mysql
Running '/etc/init.d/mariadb start' failed with error log:
231214 14:51:33 mysqld_safe Starting mariadbd daemon with databases from
/var/lib/mysql
2023-12-14 14:51:33 0 [Note] Starting MariaDB 10.11.6-MariaDB-1 source revision
as process 23044
2023-12-14 14:51:33 0 [Note] InnoDB: Compressed tables use zlib 1.3
2023-12-14 14:51:33 0 [Note] InnoDB: Number of transaction pools: 1
2023-12-14 14:51:33 0 [Note] InnoDB: Using generic crc32 instructions
2023-12-14 14:51:33 0 [Note] InnoDB: Using liburing
2023-12-14 14:51:33 0 [Note] InnoDB: Initializing buffer pool, total size =
128.000MiB, chunk size = 2.000MiB
2023-12-14 14:51:33 0 [Note] InnoDB: Completed initialization of buffer pool
2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in
datafile: ./ibdata1, Space ID:0, Flags: 0
2023-12-14 14:51:33 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page
number=0] of datafile './ibdata1' could not be found in the doublewrite buffer.
2023-12-14 14:51:33 0 [ERROR] InnoDB: Plugin initialization aborted with error
Data structure corruption
2023-12-14 14:51:33 0 [Note] InnoDB: Starting shutdown...
2023-12-14 14:51:34 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE
failed.
2023-12-14 14:51:34 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-12-14 14:51:34 0 [ERROR] Could not open mysql.plugin table: "Table
'mysql.plugin' doesn't exist". Some plugins may be not loaded
2023-12-14 14:51:34 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-12-14 14:51:34 0 [ERROR] Aborting
231214 14:51:34 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended
failed!
invoke-rc.d: initscript mariadb, action "start" failed.
dpkg: error processing package mariadb-server (--install):
installed mariadb-server package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
mariadb-server
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 5.10.0-26-marvell (UP)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages mariadb-server-core depends on:
ii libatomic1 12.2.0-14
ii libc6 2.36-9+deb12u3
ii libcrypt1 1:4.4.33-2
ii libelogind0 [libsystemd0] 246.10-1debian1
ii libnuma1 2.0.16-1
ii libpcre2-8-0 10.42-1
ii libssl3 3.0.11-1~deb12u2
ii libstdc++6 13.2.0-7
ii liburing2 2.3-3
ii mariadb-common 1:10.11.6-1
ii zlib1g 1:1.2.13.dfsg-1
mariadb-server-core recommends no packages.
mariadb-server-core suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
The bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058706 is
stale and there isn't a reproducible case to get further progress, so
I am closing this bug in Debian.
We have extensive testing that includes running MariaDB on armel, and
those CI systems have been reporting success, so this can't be a
wide-spread issue.
Thanks for using MariaDB and hopefully if there is a new issue, we
have better luck in reproducing it and getting a bug report that can
be fixed.
--- End Message ---
