Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1178750 > unrolled thread
| Started by | Scott Barker <scott@mostlylinux.ca> |
|---|---|
| First post | 2023-12-14 23:40 +0100 |
| Last post | 2023-12-21 16:30 +0100 |
| Articles | 15 — 5 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Scott Barker <scott@mostlylinux.ca> - 2023-12-14 23:40 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel kr <k-i-r@web.de> - 2023-12-17 13:00 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Otto Kekäläinen <otto@debian.org> - 2023-12-17 17:00 +0100
Bug#1058706: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel k-i-r@web.de - 2023-12-17 17:30 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Scott Barker <scott@mostlylinux.ca> - 2023-12-17 18:10 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Scott Barker <scott@mostlylinux.ca> - 2023-12-17 18:20 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Tuukka Pasanen <tuukka.pasanen@ilmi.fi> - 2023-12-18 08:40 +0100
Bug#1058706: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel k-i-r@web.de - 2023-12-19 11:30 +0100
Bug#1058706: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Tuukka Pasanen <tuukka.pasanen@ilmi.fi> - 2023-12-19 13:10 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Scott Barker <scott@mostlylinux.ca> - 2023-12-19 16:10 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Scott Barker <scott@mostlylinux.ca> - 2023-12-20 23:30 +0100
Bug#1058706: Aw: Re: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Tuukka Pasanen <tuukka.pasanen@ilmi.fi> - 2023-12-20 09:50 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel k-i-r@web.de - 2023-12-20 10:40 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Tuukka Pasanen <tuukka.pasanen@ilmi.fi> - 2023-12-21 08:40 +0100
Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Scott Barker <scott@mostlylinux.ca> - 2023-12-21 16:30 +0100
| From | Scott Barker <scott@mostlylinux.ca> |
|---|---|
| Date | 2023-12-14 23:40 +0100 |
| Subject | Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel |
| Message-ID | <HL2x3-dCil-1@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | kr <k-i-r@web.de> |
|---|---|
| Date | 2023-12-17 13:00 +0100 |
| Message-ID | <HLXYl-ebB6-1@gated-at.bofh.it> |
| In reply to | #1178750 |
I run 2 xen-virtualized debian 12.4 systems on different hardware.
One VM (gast1) shows the same mariadb bug after a fresh installation.
The other VM running on a different hardware installs mariadb-server without any issues.
----
root@gast1:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
root@gast1:~# cat /etc/debian_version
12.4
root@gast1:~#
root@gast1:~# uname -r
6.1.0-15-amd64
root@gast1:~# service mariadb status
x mariadb.service - MariaDB 10.11.4 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-12-17 11:17:58 UTC; 6min ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1345 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 1346 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1348 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_PO>
Process: 1407 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Main PID: 1407 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CPU: 421ms
Dec 17 11:17:58 gast1 mariadbd[1407]: 2023-12-17 11:17:58 0 [Note] InnoDB: Starting shutdown...
Dec 17 11:17:58 gast1 mariadbd[1407]: 2023-12-17 11:17:58 0 [ERROR] Plugin 'InnoDB' init function returned error.
Dec 17 11:17:58 gast1 mariadbd[1407]: 2023-12-17 11:17:58 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Dec 17 11:17:58 gast1 mariadbd[1407]: 2023-12-17 11:17:58 0 [Note] Plugin 'FEEDBACK' is disabled.
Dec 17 11:17:58 gast1 mariadbd[1407]: 2023-12-17 11:17:58 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Dec 17 11:17:58 gast1 mariadbd[1407]: 2023-12-17 11:17:58 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Dec 17 11:17:58 gast1 mariadbd[1407]: 2023-12-17 11:17:58 0 [ERROR] Aborting
Dec 17 11:17:58 gast1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Dec 17 11:17:58 gast1 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Dec 17 11:17:58 gast1 systemd[1]: Failed to start mariadb.service - MariaDB 10.11.4 database server.
root@gast1:~# journalctl -u mariadb
Dec 17 11:17:55 gast1 systemd[1]: Starting mariadb.service - MariaDB 10.11.4 database server...
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 1291
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Using transactional memory
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Number of transaction pools: 1
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Using liburing
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Completed initialization of buffer pool
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrite buffer.
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] InnoDB: Starting shutdown...
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Plugin 'InnoDB' init function returned error.
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [Note] Plugin 'FEEDBACK' is disabled.
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Aborting
Dec 17 11:17:55 gast1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Dec 17 11:17:55 gast1 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Dec 17 11:17:55 gast1 systemd[1]: Failed to start mariadb.service - MariaDB 10.11.4 database server.
root@gast1:~#
[toc] | [prev] | [next] | [standalone]
| From | Otto Kekäläinen <otto@debian.org> |
|---|---|
| Date | 2023-12-17 17:00 +0100 |
| Message-ID | <HM1IB-edOS-3@gated-at.bofh.it> |
| In reply to | #1178750 |
[Multipart message — attachments visible in raw view] — view raw
Hi Scott and Kr! Did you note this line? 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 Can you include the output of `find /var/lib/mysql -ls` so we can see what files your system has? What is the hardware you have? The report shows 'Linux 5.10.0-26-marvell '. What does `uname -a` yield? The test suite passes on armhf at e.g. https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. At https://ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to regression in subselect which is unrelated to what you reported.
[toc] | [prev] | [next] | [standalone]
| From | k-i-r@web.de |
|---|---|
| Date | 2023-12-17 17:30 +0100 |
| Subject | Bug#1058706: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel |
| Message-ID | <HM2bE-eeeJ-15@gated-at.bofh.it> |
| In reply to | #1179061 |
Hi Otto, root@gast1:~# find /var/lib/mysql -ls 262301 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 11:17 /var/lib/mysql 263594 4 -rw-rw---- 1 mysql mysql 52 Dec 17 11:17 /var/lib/mysql/aria_log_control 263597 98304 -rw-rw---- 1 mysql mysql 100663296 Dec 17 11:17 /var/lib/mysql/ib_logfile101 263596 12288 -rw-rw---- 1 mysql mysql 12582912 Dec 17 11:17 /var/lib/mysql/ibdata1 263591 0 -rw-r--r-- 1 root root 0 Dec 17 11:17 /var/lib/mysql/debian-10.11.flag 263595 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 11:17 /var/lib/mysql/aria_log.00000001 root@gast1:~# root@gast1:~# uname -a Linux gast1 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64 GNU/Linux root@gast1:~# Regards, Konstantin Gesendet: Sonntag, 17. Dezember 2023 um 16:48 Uhr Von: "Otto Kekäläinen" <otto@debian.org> An: "Scott Barker" <scott@mostlylinux.ca>, 1058706@bugs.debian.org, k-i-r@web.de Cc: "Faustin Lammler" <faustin@mariadb.org>, "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi> Betreff: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Hi Scott and Kr! Did you note this line? 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 Can you include the output of `find /var/lib/mysql -ls` so we can see what files your system has? What is the hardware you have? The report shows 'Linux 5.10.0-26-marvell '. What does `uname -a` yield? The test suite passes on armhf at e.g. https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. At https://ci.debian.net/packages/m/mariadb/unstable/armel/[https://ci.debian.net/packages/m/mariadb/unstable/armel/] it fails due to regression in subselect which is unrelated to what you reported.
[toc] | [prev] | [next] | [standalone]
| From | Scott Barker <scott@mostlylinux.ca> |
|---|---|
| Date | 2023-12-17 18:10 +0100 |
| Message-ID | <HM2Ol-eeHK-3@gated-at.bofh.it> |
| In reply to | #1179061 |
Prior to the installation, /var/lib/mysql did not exist. After installation: 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 /var/lib/mysql 61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 /var/lib/mysql/aria_log_control 61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 /var/lib/mysql/ibdata1 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 /var/lib/mysql/debian-10.11.flag 61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 /var/lib/mysql/ib_logfile101 61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 /var/lib/mysql/aria_log.00000001 uname -a reports: Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) armv5tel GNU/Linux On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: >Hi Scott and Kr! > >Did you note this line? > >2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in >datafile: ./ibdata1, Space ID:0, Flags: 0 > >Can you include the output of `find /var/lib/mysql -ls` so we can see what >files your system has? > >What is the hardware you have? The report shows 'Linux 5.10.0-26-marvell '. >What does `uname -a` yield? > >The test suite passes on armhf at e.g. https://launchpad.net/~mysql-ubuntu/ >+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. At https:// >ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to regression in >subselect which is unrelated to what you reported. > -- Scott Barker
[toc] | [prev] | [next] | [standalone]
| From | Scott Barker <scott@mostlylinux.ca> |
|---|---|
| Date | 2023-12-17 18:20 +0100 |
| Message-ID | <HM2Y2-eeLn-9@gated-at.bofh.it> |
| In reply to | #1179066 |
Same result with the latest kernel: Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel GNU/Linux On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: >Prior to the installation, /var/lib/mysql did not exist. After installation: > >61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 /var/lib/mysql >61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 /var/lib/mysql/aria_log_control >61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 /var/lib/mysql/ibdata1 >61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 /var/lib/mysql/debian-10.11.flag >61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 /var/lib/mysql/ib_logfile101 >61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 /var/lib/mysql/aria_log.00000001 > >uname -a reports: > >Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) armv5tel GNU/Linux > >On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: >>Hi Scott and Kr! >> >>Did you note this line? >> >>2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in >>datafile: ./ibdata1, Space ID:0, Flags: 0 >> >>Can you include the output of `find /var/lib/mysql -ls` so we can see what >>files your system has? >> >>What is the hardware you have? The report shows 'Linux 5.10.0-26-marvell '. >>What does `uname -a` yield? >> >>The test suite passes on armhf at e.g. https://launchpad.net/~mysql-ubuntu/ >>+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. At https:// >>ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to regression in >>subselect which is unrelated to what you reported. >> > >-- >Scott Barker > >-- >To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org. -- Scott Barker
[toc] | [prev] | [next] | [standalone]
| From | Tuukka Pasanen <tuukka.pasanen@ilmi.fi> |
|---|---|
| Date | 2023-12-18 08:40 +0100 |
| Message-ID | <HMgoh-emLh-7@gated-at.bofh.it> |
| In reply to | #1179068 |
Hello, Have you monitored that is memory exhausted at the installation? This could lead error like that. I assume your XEN/KVM/Docker base machine is some older system with not so fancy CPU or is there any particular reason to use armel build? Sincerly, Tuukka Scott Barker kirjoitti 17.12.2023 klo 19.15: > Same result with the latest kernel: > > Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel > GNU/Linux > > On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: >> Prior to the installation, /var/lib/mysql did not exist. After >> installation: >> >> 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 >> /var/lib/mysql >> 61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 >> /var/lib/mysql/aria_log_control >> 61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 >> /var/lib/mysql/ibdata1 >> 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 >> /var/lib/mysql/debian-10.11.flag >> 61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 >> /var/lib/mysql/ib_logfile101 >> 61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 >> /var/lib/mysql/aria_log.00000001 >> >> uname -a reports: >> >> Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) >> armv5tel GNU/Linux >> >> On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: >>> Hi Scott and Kr! >>> >>> Did you note this line? >>> >>> 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero >>> bytes in >>> datafile: ./ibdata1, Space ID:0, Flags: 0 >>> >>> Can you include the output of `find /var/lib/mysql -ls` so we can >>> see what >>> files your system has? >>> >>> What is the hardware you have? The report shows 'Linux >>> 5.10.0-26-marvell '. >>> What does `uname -a` yield? >>> >>> The test suite passes on armhf at >>> e.g. https://launchpad.net/~mysql-ubuntu/ >>> +archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. >>> At https:// >>> ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to >>> regression in >>> subselect which is unrelated to what you reported. >>> >> >> -- >> Scott Barker >> >> -- >> To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org. >
[toc] | [prev] | [next] | [standalone]
| From | k-i-r@web.de |
|---|---|
| Date | 2023-12-19 11:30 +0100 |
| Subject | Bug#1058706: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel |
| Message-ID | <HMFwl-eCgo-13@gated-at.bofh.it> |
| In reply to | #1179115 |
Hi Tuukka, I don't think the issue is related to the armel hardware. I see the same error on my XEN-VM (1 VCPU) based on a Intel(R) Celeron(R) CPU G3900 @ 2.80GHz processor with 2 cores. No lack of memory could be seen during installation of mariadb-server package. I tested it with 2 or 8 GB of assigned RAM. Regards, Konstantin Gesendet: Montag, 18. Dezember 2023 um 08:23 Uhr Von: "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi> An: "Scott Barker" <scott@mostlylinux.ca>, 1058706@bugs.debian.org, "Otto Kekäläinen" <otto@debian.org>, k-i-r@web.de Cc: "Faustin Lammler" <faustin@mariadb.org> Betreff: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel Hello, Have you monitored that is memory exhausted at the installation? This could lead error like that. I assume your XEN/KVM/Docker base machine is some older system with not so fancy CPU or is there any particular reason to use armel build? Sincerly, Tuukka Scott Barker kirjoitti 17.12.2023 klo 19.15: > Same result with the latest kernel: > > Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel > GNU/Linux > > On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: >> Prior to the installation, /var/lib/mysql did not exist. After >> installation: >> >> 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 >> /var/lib/mysql >> 61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 >> /var/lib/mysql/aria_log_control >> 61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 >> /var/lib/mysql/ibdata1 >> 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 >> /var/lib/mysql/debian-10.11.flag >> 61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 >> /var/lib/mysql/ib_logfile101 >> 61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 >> /var/lib/mysql/aria_log.00000001 >> >> uname -a reports: >> >> Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) >> armv5tel GNU/Linux >> >> On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: >>> Hi Scott and Kr! >>> >>> Did you note this line? >>> >>> 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero >>> bytes in >>> datafile: ./ibdata1, Space ID:0, Flags: 0 >>> >>> Can you include the output of `find /var/lib/mysql -ls` so we can >>> see what >>> files your system has? >>> >>> What is the hardware you have? The report shows 'Linux >>> 5.10.0-26-marvell '. >>> What does `uname -a` yield? >>> >>> The test suite passes on armhf at >>> e.g. https://launchpad.net/~mysql-ubuntu/ >>> +archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. >>> At https:// >>> ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to >>> regression in >>> subselect which is unrelated to what you reported. >>> >> >> -- >> Scott Barker >> >> -- >> To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org. >
[toc] | [prev] | [next] | [standalone]
| From | Tuukka Pasanen <tuukka.pasanen@ilmi.fi> |
|---|---|
| Date | 2023-12-19 13:10 +0100 |
| Subject | Bug#1058706: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel |
| Message-ID | <HMH57-eDnt-9@gated-at.bofh.it> |
| In reply to | #1179302 |
[Multipart message — attachments visible in raw view] — view raw
Hello, I've investigate this yesterday and I could reproduce this one: Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Aborting Can you do (Please on testing machine not production will destroy your database!!!) apt purge mariadb-server # check is your database is not available /var/lib/mysql if it is remote it mkdir -p /var/lib/mysql chown mysql:mysql /var/lib/mysql and then re-install mariad-server again. Does it work then? Just trying to see if my findings are correct. What comes to this InnoDB corruption I can't reproduce that. Sincerely, Tuukka k-i-r@web.de kirjoitti 19.12.2023 klo 12.18: > Hi Tuukka, > I don't think the issue is related to the armel hardware. > I see the same error on my XEN-VM (1 VCPU) based on a Intel(R) Celeron(R) CPU G3900 @ 2.80GHz processor with 2 cores. > No lack of memory could be seen during installation of mariadb-server package. I tested it with 2 or 8 GB of assigned RAM. > > Regards, > Konstantin > > > Gesendet: Montag, 18. Dezember 2023 um 08:23 Uhr > Von: "Tuukka Pasanen"<tuukka.pasanen@ilmi.fi> > An: "Scott Barker"<scott@mostlylinux.ca>,1058706@bugs.debian.org, "Otto Kekäläinen"<otto@debian.org>,k-i-r@web.de > Cc: "Faustin Lammler"<faustin@mariadb.org> > Betreff: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel > Hello, > > Have you monitored that is memory exhausted at the installation? This > could lead error like that. > > I assume your XEN/KVM/Docker base machine is some older system with not > so fancy CPU or is there any particular reason to use armel build? > > Sincerly, > > Tuukka > > Scott Barker kirjoitti 17.12.2023 klo 19.15: >> Same result with the latest kernel: >> >> Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel >> GNU/Linux >> >> On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: >>> Prior to the installation, /var/lib/mysql did not exist. After >>> installation: >>> >>> 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 >>> /var/lib/mysql >>> 61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 >>> /var/lib/mysql/aria_log_control >>> 61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 >>> /var/lib/mysql/ibdata1 >>> 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 >>> /var/lib/mysql/debian-10.11.flag >>> 61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 >>> /var/lib/mysql/ib_logfile101 >>> 61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 >>> /var/lib/mysql/aria_log.00000001 >>> >>> uname -a reports: >>> >>> Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) >>> armv5tel GNU/Linux >>> >>> On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: >>>> Hi Scott and Kr! >>>> >>>> Did you note this line? >>>> >>>> 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero >>>> bytes in >>>> datafile: ./ibdata1, Space ID:0, Flags: 0 >>>> >>>> Can you include the output of `find /var/lib/mysql -ls` so we can >>>> see what >>>> files your system has? >>>> >>>> What is the hardware you have? The report shows 'Linux >>>> 5.10.0-26-marvell '. >>>> What does `uname -a` yield? >>>> >>>> The test suite passes on armhf at >>>> e.g.https://launchpad.net/~mysql-ubuntu/ >>>> +archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. >>>> At https:// >>>> ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to >>>> regression in >>>> subselect which is unrelated to what you reported. >>>> >>> -- >>> Scott Barker >>> >>> -- >>> To unsubscribe, send mail to1058706-unsubscribe@bugs.debian.org.
[toc] | [prev] | [next] | [standalone]
| From | Scott Barker <scott@mostlylinux.ca> |
|---|---|
| Date | 2023-12-19 16:10 +0100 |
| Message-ID | <HMJTj-eF1p-19@gated-at.bofh.it> |
| In reply to | #1179115 |
For myself, I am not using XEN/KVM/Docker. I am installing this on a NAS device with an ARM chip and only 512M of RAM. I tried adding a 2G swap file, but it did not make a difference. I was able to start mariadb by disabling INNODB and using MyISAM instead with the options: --innodb=OFF --default-storage-engine=MyISAM On Mon, Dec 18, 2023 at 09:23:55AM +0200, Tuukka Pasanen wrote: >Hello, > >Have you monitored that is memory exhausted at the installation? This >could lead error like that. > >I assume your XEN/KVM/Docker base machine is some older system with >not so fancy CPU or is there any particular reason to use armel build? > >Sincerly, > >Tuukka > >Scott Barker kirjoitti 17.12.2023 klo 19.15: >>Same result with the latest kernel: >> >>Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) >>armv5tel GNU/Linux >> >>On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: >>>Prior to the installation, /var/lib/mysql did not exist. After >>>installation: >>> >>>61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 >>>/var/lib/mysql >>>61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 >>>/var/lib/mysql/aria_log_control >>>61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 >>>/var/lib/mysql/ibdata1 >>>61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 >>>/var/lib/mysql/debian-10.11.flag >>>61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 >>>/var/lib/mysql/ib_logfile101 >>>61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 >>>/var/lib/mysql/aria_log.00000001 >>> >>>uname -a reports: >>> >>>Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) >>>armv5tel GNU/Linux >>> >>>On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: >>>>Hi Scott and Kr! >>>> >>>>Did you note this line? >>>> >>>>2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of >>>>zero bytes in >>>>datafile: ./ibdata1, Space ID:0, Flags: 0 >>>> >>>>Can you include the output of `find /var/lib/mysql -ls` so we >>>>can see what >>>>files your system has? >>>> >>>>What is the hardware you have? The report shows 'Linux >>>>5.10.0-26-marvell '. >>>>What does `uname -a` yield? >>>> >>>>The test suite passes on armhf at >>>>e.g. https://launchpad.net/~mysql-ubuntu/ >>>>+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. >>>>At https:// >>>>ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to >>>>regression in >>>>subselect which is unrelated to what you reported. >>>> >>> >>>-- >>>Scott Barker >>> >>>-- >>>To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org. >> -- Scott Barker
[toc] | [prev] | [next] | [standalone]
| From | Scott Barker <scott@mostlylinux.ca> |
|---|---|
| Date | 2023-12-20 23:30 +0100 |
| Message-ID | <HNdeF-eXdd-3@gated-at.bofh.it> |
| In reply to | #1179330 |
On my secondard ARM NAS, I downgraded from bookworm to bullseye, and installed mariadb 10.5 from scratch (no pre-existing /var/lib/mysql or /etc/mysql). Everything worked without issues. From syslog: mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql mysqld: 2023-12-20 7:58:07 0 [Note] Starting MariaDB 10.5.21-MariaDB-0+deb11u1 source revision bed70468ea08c2820647f5e3ac006a9ff88144ac as process 2250 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Uses event mutexes mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Number of pools: 1 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using generic crc32 instructions mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using Linux native AIO mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Completed initialization of buffer pool mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 128 rollback segments are active. mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 10.5.21 started; log sequence number 45079; transaction id 20 mysqld: 2023-12-20 7:58:07 0 [Note] Plugin 'FEEDBACK' is disabled. mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Buffer pool(s) load completed at 231220 7:58:07 mysqld: 2023-12-20 7:58:07 0 [Note] Server socket created on IP: '127.0.0.1'. mysqld: 2023-12-20 7:58:07 0 [Note] Reading of all Master_info entries succeeded mysqld: 2023-12-20 7:58:07 0 [Note] Added new Master_info '' to hash table mysqld: 2023-12-20 7:58:07 0 [Note] /usr/sbin/mariadbd: ready for connections. mysqld: Version: '10.5.21-MariaDB-0+deb11u1' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 11 I then proceeded to upgrade from bookworm all packages containing libraries to which /usr/sbin/mariadbd and /usr/lib/mysql/plugin/* were linked, one at a time, restarting mariadb after each package was installed, and there were no issues. I then upgraded the rest of the system to bookworm, a few packages at a time, excluding the mariadb packages. I restarted mariadb after each batch of packages, and there were no issues, including after reboot into the new kernel. I then renamed /var/lib/mysql to /var/lib/mysql.bak and ran: dpkg-reconfigure -plow mariadb-server-10.5 mariadb-server-core-10.5 Again, no issues - /var/lib/mysql was re-created and mariadbd started just fine, with the same syslog entries as above. I then copied /var/lib/mysql to /var/lib/mysql-10.5 and upgraded mariadb with: apt upgrade mariadb-server-10.5 Here is the entire output, you can see the errors at the end: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-core-10.5 The following NEW packages will be installed: libnuma1 liburing2 mariadb-client mariadb-client-core mariadb-server mariadb-server-core The following packages will be upgraded: mariadb-server-10.5 1 upgraded, 6 newly installed, 3 to remove and 0 not upgraded. Need to get 12.7 MB of archives. After this operation, 28.0 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 https://deb.debian.org/debian bookworm/main armel mariadb-server-10.5 armel 1:10.11.4-1~deb12u1 [22.7 kB] Get:2 https://deb.debian.org/debian bookworm/main armel mariadb-client-core armel 1:10.11.4-1~deb12u1 [754 kB] Get:3 https://deb.debian.org/debian bookworm/main armel mariadb-client armel 1:10.11.4-1~deb12u1 [2,510 kB] Get:4 https://deb.debian.org/debian bookworm/main armel libnuma1 armel 2.0.16-1 [18.3 kB] Get:5 https://deb.debian.org/debian bookworm/main armel liburing2 armel 2.3-3 [13.2 kB] Get:6 https://deb.debian.org/debian bookworm/main armel mariadb-server-core armel 1:10.11.4-1~deb12u1 [6,328 kB] Get:7 https://deb.debian.org/debian bookworm/main armel mariadb-server armel 1:10.11.4-1~deb12u1 [3,027 kB] Fetched 12.7 MB in 5s (2,486 kB/s) Preconfiguring packages ... (Reading database ... 24167 files and directories currently installed.) Preparing to unpack .../mariadb-server-10.5_1%3a10.11.4-1~deb12u1_armel.deb ... Stopping MariaDB database server: mariadbd. Unpacking mariadb-server-10.5 (1:10.11.4-1~deb12u1) over (1:10.5.21-0+deb11u1) ... (Reading database ... 24042 files and directories currently installed.) Removing mariadb-client-10.5 (1:10.5.21-0+deb11u1) ... Removing mariadb-client-core-10.5 (1:10.5.21-0+deb11u1) ... Removing mariadb-server-core-10.5 (1:10.5.21-0+deb11u1) ... Selecting previously unselected package mariadb-client-core. (Reading database ... 23850 files and directories currently installed.) Preparing to unpack .../0-mariadb-client-core_1%3a10.11.4-1~deb12u1_armel.deb ... Unpacking mariadb-client-core (1:10.11.4-1~deb12u1) ... Selecting previously unselected package mariadb-client. Preparing to unpack .../1-mariadb-client_1%3a10.11.4-1~deb12u1_armel.deb ... Unpacking mariadb-client (1:10.11.4-1~deb12u1) ... Selecting previously unselected package libnuma1:armel. Preparing to unpack .../2-libnuma1_2.0.16-1_armel.deb ... Unpacking libnuma1:armel (2.0.16-1) ... Selecting previously unselected package liburing2:armel. Preparing to unpack .../3-liburing2_2.3-3_armel.deb ... Unpacking liburing2:armel (2.3-3) ... Selecting previously unselected package mariadb-server-core. Preparing to unpack .../4-mariadb-server-core_1%3a10.11.4-1~deb12u1_armel.deb ... Unpacking mariadb-server-core (1:10.11.4-1~deb12u1) ... Selecting previously unselected package mariadb-server. Preparing to unpack .../5-mariadb-server_1%3a10.11.4-1~deb12u1_armel.deb ... /var/lib/mysql: found previous version 10.5 Unpacking mariadb-server (1:10.11.4-1~deb12u1) ... Setting up mariadb-client-core (1:10.11.4-1~deb12u1) ... Setting up libnuma1:armel (2.0.16-1) ... Setting up liburing2:armel (2.3-3) ... Setting up mariadb-client (1:10.11.4-1~deb12u1) ... Setting up mariadb-server-core (1:10.11.4-1~deb12u1) ... Setting up mariadb-server (1:10.11.4-1~deb12u1) ... Installing new version of config file /etc/init.d/mariadb ... Installing new version of config file /etc/logrotate.d/mariadb ... Installing new version of config file /etc/mysql/debian-start ... Installing new version of config file /etc/mysql/mariadb.conf.d/50-server.cnf ... Stopping MariaDB database server: mariadbd. Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed! invoke-rc.d: initscript mariadb, action "start" failed. dpkg: error processing package mariadb-server (--configure): installed mariadb-server package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of mariadb-server-10.5: mariadb-server-10.5 depends on mariadb-server (>= 1:10.11); however: Package mariadb-server is not configured yet. dpkg: error processing package mariadb-server-10.5 (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.36-9+deb12u3) ... Errors were encountered while processing: mariadb-server mariadb-server-10.5 E: Sub-process /usr/bin/dpkg returned an error code (1) Here is what was logged to syslog: mariadb-server.postinst[3596]: mysql.user table already exists! mariadb-server.postinst[3596]: Run mysql_upgrade, not mysql_install_db mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql mysqld: 2023-12-20 10:23:51 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 3765 mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Number of transaction pools: 1 mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Using generic crc32 instructions mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Using liburing mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Completed initialization of buffer pool mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes) mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Upgrading redo log: 96.000MiB; LSN=45767 mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes) mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: 128 rollback segments are active. mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. mysqld: 2023-12-20 10:23:53 0 [Note] InnoDB: log sequence number 45767; transaction id 20 mysqld: 2023-12-20 10:23:53 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool mysqld: 2023-12-20 10:23:53 0 [Note] Plugin 'FEEDBACK' is disabled. mysqld: 2023-12-20 10:23:53 0 [ERROR] InnoDB: File ./ibdata1: 'aio read' returned OS error 0. Cannot continue operation mysqld: 231220 10:23:53 [ERROR] mysqld got signal 6 ; mysqld: This could be because you hit a bug. It is also possible that this binary mysqld: or one of the libraries it was linked against is corrupt, improperly built, mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. mysqld: mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs mysqld: mysqld: We will try our best to scrape up some info that will hopefully help mysqld: diagnose the problem, but since we have already crashed, mysqld: something is definitely wrong and this may fail. mysqld: mysqld: Server version: 10.11.4-MariaDB-1~deb12u1 source revision: mysqld: key_buffer_size=134217728 mysqld: read_buffer_size=131072 mysqld: max_used_connections=0 mysqld: max_threads=153 mysqld: thread_count=1 mysqld: It is possible that mysqld could use up to mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466625 K bytes of memory mysqld: Hope that's ok; if not, decrease some variables in the equation. mysqld: mysqld: Thread pointer: 0x0 mysqld: Attempting backtrace. You can use the following information to find out mysqld: where mysqld died. If you see no messages after this, something went mysqld: terribly wrong... mysqld: stack_bottom = 0x0 thread_stack 0x49000 mysqld: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains mysqld: information that should help you find out what is causing the crash. mysqld: Writing a core file... mysqld: Working directory at /var/lib/mysql mysqld: Resource Limits: mysqld: Limit Soft Limit Hard Limit Units mysqld: Max cpu time unlimited unlimited seconds mysqld: Max file size unlimited unlimited bytes mysqld: Max data size unlimited unlimited bytes mysqld: Max stack size 8388608 unlimited bytes mysqld: Max core file size 0 unlimited bytes mysqld: Max resident set unlimited unlimited bytes mysqld: Max processes 1904 1904 processes mysqld: Max open files 32183 32183 files mysqld: Max locked memory 8388608 8388608 bytes mysqld: Max address space unlimited unlimited bytes mysqld: Max file locks unlimited unlimited locks mysqld: Max pending signals 1904 1904 signals mysqld: Max msgqueue size 819200 819200 bytes mysqld: Max nice priority 0 0 mysqld: Max realtime priority 0 0 mysqld: Max realtime timeout unlimited unlimited us mysqld: Core pattern: core mysqld: mysqld: Kernel version: Linux version 6.1.0-16-marvell (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 Debian 6.1.67-1 (2023-12-12) mysqld: mysqld_safe: mysqld from pid file /run/mysqld/mysqld.pid ended /etc/init.d/mariadb[4054]: 0 processes alive and '/usr/bin/mariadb-admin --defaults-file=/etc/mysql/debian.cnf ping' resulted in /etc/init.d/mariadb[4054]: #007/usr/bin/mariadb-admin: connect to server at 'localhost' failed /etc/init.d/mariadb[4054]: error: 'Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)' /etc/init.d/mariadb[4054]: Check that mariadbd is running and that the socket: '/run/mysqld/mysqld.sock' exists! After the upgrade, a "diff" on the two mysql folders shows: Only in mysql/: ddl_recovery.log Only in mysql/: debian-10.11.flag Only in mysql-10.5/: debian-10.5.flag Binary files mysql-10.5/ib_logfile0 and mysql/ib_logfile0 differ Only in mysql/: ibtmp1 No other files changed. I then added these two lines in the [server] section of /etc/mysql/mariadb.conf.d/50-server.cnf: innodb = OFF default-storage-engine = MyISAM Then I ran: apt install -f After this, mariadbd started successfully, but without the InnoDB engine, as can be seen in syslog: mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql mysqld: 2023-12-20 11:01:31 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 5560 mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'InnoDB' is disabled. mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'FEEDBACK' is disabled. mysqld: 2023-12-20 11:01:32 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. mysqld: 2023-12-20 11:01:32 0 [Note] Server socket created on IP: '127.0.0.1'. mysqld: 2023-12-20 11:01:32 0 [Note] /usr/sbin/mariadbd: ready for connections. mysqld: Version: '10.11.4-MariaDB-1~deb12u1' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 12 /etc/mysql/debian-start[5589]: Upgrading MySQL tables if necessary. /etc/mysql/debian-start[5599]: Checking for insecure root accounts. /etc/mysql/debian-start[5603]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables On Tue, Dec 19, 2023 at 08:07:16AM -0700, Scott Barker wrote: >For myself, I am not using XEN/KVM/Docker. I am installing this on a >NAS device with an ARM chip and only 512M of RAM. I tried adding a 2G >swap file, but it did not make a difference. I was able to start >mariadb by disabling INNODB and using MyISAM instead with the options: > >--innodb=OFF --default-storage-engine=MyISAM > >On Mon, Dec 18, 2023 at 09:23:55AM +0200, Tuukka Pasanen wrote: >>Hello, >> >>Have you monitored that is memory exhausted at the installation? >>This could lead error like that. >> >>I assume your XEN/KVM/Docker base machine is some older system with >>not so fancy CPU or is there any particular reason to use armel >>build? >> >>Sincerly, >> >>Tuukka >> >>Scott Barker kirjoitti 17.12.2023 klo 19.15: >>>Same result with the latest kernel: >>> >>>Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) >>>armv5tel GNU/Linux >>> >>>On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: >>>>Prior to the installation, /var/lib/mysql did not exist. After >>>>installation: >>>> >>>>61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 >>>>/var/lib/mysql >>>>61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 >>>>/var/lib/mysql/aria_log_control >>>>61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 >>>>/var/lib/mysql/ibdata1 >>>>61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 >>>>/var/lib/mysql/debian-10.11.flag >>>>61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 >>>>/var/lib/mysql/ib_logfile101 >>>>61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 >>>>/var/lib/mysql/aria_log.00000001 >>>> >>>>uname -a reports: >>>> >>>>Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) >>>>armv5tel GNU/Linux >>>> >>>>On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: >>>>>Hi Scott and Kr! >>>>> >>>>>Did you note this line? >>>>> >>>>>2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of >>>>>zero bytes in >>>>>datafile: ./ibdata1, Space ID:0, Flags: 0 >>>>> >>>>>Can you include the output of `find /var/lib/mysql -ls` so we >>>>>can see what >>>>>files your system has? >>>>> >>>>>What is the hardware you have? The report shows 'Linux >>>>>5.10.0-26-marvell '. >>>>>What does `uname -a` yield? >>>>> >>>>>The test suite passes on armhf at >>>>>e.g. https://launchpad.net/~mysql-ubuntu/ >>>>>+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. >>>>>At https:// >>>>>ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due >>>>>to regression in >>>>>subselect which is unrelated to what you reported. >>>>> >>>> >>>>-- >>>>Scott Barker >>>> >>>>-- >>>>To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org. >>> > >-- >Scott Barker > >-- >To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org. -- Scott Barker
[toc] | [prev] | [next] | [standalone]
| From | Tuukka Pasanen <tuukka.pasanen@ilmi.fi> |
|---|---|
| Date | 2023-12-20 09:50 +0100 |
| Subject | Bug#1058706: Aw: Re: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel |
| Message-ID | <HN0r7-eOUp-1@gated-at.bofh.it> |
| In reply to | #1178750 |
[Multipart message — attachments visible in raw view] — view raw
Hello, Thank you for testing. I assume these are different issues. Other happens in low end ARMv5 machine with 512 MB (memory which is kind of low now a days) and other is in normal server/laptop inside XEN machine (although i686? 32-bit still as armel). As I understand your problem is in initializing mysql-dir (which is mandatory) but MYISAM/Aria and InnoDB works ok? But you can debug this (I ate my dogfood and tested not just write from the memory sorry for that) shutdown mariadbd (which is not probably not running) remove /var/lib/mysql which again will destroy your database (Please note) use to install your database: /usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql Does it print some errors? Is there any errors in syslog? Does MariaDB start after this? Sincerely, Tuukka k-i-r@web.de kirjoitti 19.12.2023 klo 16.33: > Removing mariadb-server via apt purge also removes the user mysql. > --> chown mysql:mylsql doesn't work. > Reinstalling mariadb-server doesn't solve the issue. > *Gesendet:* Dienstag, 19. Dezember 2023 um 13:01 Uhr > *Von:* "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi> > *An:* k-i-r@web.de > *Cc:* "Scott Barker" <scott@mostlylinux.ca>, 1058706@bugs.debian.org, > "Otto Kekäläinen" <otto@debian.org>, "Faustin Lammler" > <faustin@mariadb.org> > *Betreff:* Re: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd > fails to start on fresh install on armel > > Hello, > > I've investigate this yesterday and I could reproduce this one: > > Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded > Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB > Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Aborting > > Can you do (Please on testing machine not production will destroy your database!!!) > apt purge mariadb-server > # check is your database is not available /var/lib/mysql if it is remote it > mkdir -p /var/lib/mysql > chown mysql:mysql /var/lib/mysql > and then re-install mariad-server again. Does it work then? Just trying to see if my findings are correct. What comes to this InnoDB corruption I can't reproduce that. > > Sincerely, > Tuukka > > k-i-r@web.de kirjoitti 19.12.2023 klo 12.18: > > Hi Tuukka, > I don't think the issue is related to the armel hardware. > I see the same error on my XEN-VM (1 VCPU) based on a Intel(R) Celeron(R) CPU G3900 @ 2.80GHz processor with 2 cores. > No lack of memory could be seen during installation of mariadb-server package. I tested it with 2 or 8 GB of assigned RAM. > > Regards, > Konstantin > > > Gesendet: Montag, 18. Dezember 2023 um 08:23 Uhr > Von: "Tuukka Pasanen"<tuukka.pasanen@ilmi.fi> > An: "Scott Barker"<scott@mostlylinux.ca>,1058706@bugs.debian.org, "Otto Kekäläinen"<otto@debian.org>,k-i-r@web.de > Cc: "Faustin Lammler"<faustin@mariadb.org> > Betreff: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel > Hello, > > Have you monitored that is memory exhausted at the installation? This > could lead error like that. > > I assume your XEN/KVM/Docker base machine is some older system with not > so fancy CPU or is there any particular reason to use armel build? > > Sincerly, > > Tuukka > > Scott Barker kirjoitti 17.12.2023 klo 19.15: > > Same result with the latest kernel: > > Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel > GNU/Linux > > On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: > > Prior to the installation, /var/lib/mysql did not exist. After > installation: > > 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 > /var/lib/mysql > 61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 > /var/lib/mysql/aria_log_control > 61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 > /var/lib/mysql/ibdata1 > 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 > /var/lib/mysql/debian-10.11.flag > 61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 > /var/lib/mysql/ib_logfile101 > 61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 > /var/lib/mysql/aria_log.00000001 > > uname -a reports: > > Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) > armv5tel GNU/Linux > > On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: > > Hi Scott and Kr! > > Did you note this line? > > 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero > bytes in > datafile: ./ibdata1, Space ID:0, Flags: 0 > > Can you include the output of `find /var/lib/mysql -ls` so we can > see what > files your system has? > > What is the hardware you have? The report shows 'Linux > 5.10.0-26-marvell '. > What does `uname -a` yield? > > The test suite passes on armhf at > e.g.https://launchpad.net/~mysql-ubuntu/ > +archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. > At https:// > ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to > regression in > subselect which is unrelated to what you reported. > > -- > Scott Barker > > -- > To unsubscribe, send mail to1058706-unsubscribe@bugs.debian.org. > > > > > >
[toc] | [prev] | [next] | [standalone]
| From | k-i-r@web.de |
|---|---|
| Date | 2023-12-20 10:40 +0100 |
| Message-ID | <HN1dw-ePpf-11@gated-at.bofh.it> |
| In reply to | #1179441 |
Starting point:
- Installed mariadb-server package which doesn't run
- /var/lib/mysql removed manually
- root@gast1:/var/lib# /usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql -- > error, see below
root@gast1:/var/lib# /usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql
231220 9:21:04 [ERROR] mysqld got signal 4 ;
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.11.4-MariaDB-1~deb12u1 source revision:
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 = 468022 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 0x49000
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5599a37984ae]
/usr/sbin/mariadbd(handle_fatal_signal+0x409)[0x5599a3305f49]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bfd0)[0x7fb58645afd0]
/usr/sbin/mariadbd(+0x6f5d79)[0x5599a2fd2d79]
/usr/sbin/mariadbd(+0xe2590a)[0x5599a370290a]
/usr/sbin/mariadbd(+0x6862e2)[0x5599a2f632e2]
/usr/sbin/mariadbd(+0xcd9671)[0x5599a35b6671]
/usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x5599a330927e]
Printing to addr2line failed
/usr/sbin/mariadbd(+0x80f997)[0x5599a30ec997]
/usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x85a)[0x5599a30ed95a]
/usr/sbin/mariadbd(+0x701037)[0x5599a2fde037]
/usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x41d)[0x5599a2fe3a5d]
/lib/x86_64-linux-gnu/libc.so.6(+0x271ca)[0x7fb5864461ca]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7fb586446285]
/usr/sbin/mariadbd(_start+0x21)[0x5599a2fd8c81]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 31372 31372 processes
Max open files 32183 32183 files
Max locked memory 1045245952 1045245952 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 31372 31372 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core
Kernel version: Linux version 6.1.0-15-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09)
Illegal instruction
Installation of system tables failed! Examine the logs in
/var/lib/mysql for more information.
The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:
shell> /usr/bin/mariadb-install-db --defaults-file=~/.my.cnf
You can also try to start the mariadbd daemon with:
shell> /usr/sbin/mariadbd --skip-grant-tables --general-log &
and use the command line tool /usr/bin/mariadb
to connect to the mysql database and look at the grant tables:
shell> /usr/bin/mariadb -u root mysql
MariaDB> show tables;
Try '/usr/sbin/mariadbd --help' if you have problems with paths. Using
--general-log gives you a log in /var/lib/mysql that may be helpful.
The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
You can find the latest source at https://downloads.mariadb.org and
the maria-discuss email list at https://launchpad.net/~maria-discuss
Please check all of the above before submitting a bug report
at https://mariadb.org/jira
root@gast1:/var/lib#
root@gast1:/var/lib# journalctl -u mariadb
Dec 20 09:20:36 gast1 systemd[1]: Starting mariadb.service - MariaDB 10.11.4 database server...
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 1310
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Using transactional memory
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Number of transaction pools: 1
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Using liburing
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Completed initialization of buffer pool
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrit>
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Starting shutdown...
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Plugin 'InnoDB' init function returned error.
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] Plugin 'FEEDBACK' is disabled.
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Aborting
Dec 20 09:20:37 gast1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Dec 20 09:20:37 gast1 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Dec 20 09:20:37 gast1 systemd[1]: Failed to start mariadb.service - MariaDB 10.11.4 database server.
Dec 20 09:20:39 gast1 systemd[1]: Starting mariadb.service - MariaDB 10.11.4 database server...
Dec 20 09:20:39 gast1 mariadbd[1426]: 2023-12-20 9:20:39 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 1426
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Using transactional memory
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Number of transaction pools: 1
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Using liburing
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Completed initialization of buffer pool
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrit>
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Starting shutdown...
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Plugin 'InnoDB' init function returned error.
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] Plugin 'FEEDBACK' is disabled.
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Aborting
Dec 20 09:20:40 gast1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Dec 20 09:20:40 gast1 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Dec 20 09:20:40 gast1 systemd[1]: Failed to start mariadb.service - MariaDB 10.11.4 database server.
root@gast1:/var/lib#
------------------------------
Gesendet: Mittwoch, 20. Dezember 2023 um 09:43 Uhr
Von: "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi>
An: k-i-r@web.de
Cc: "Scott Barker" <scott@mostlylinux.ca>, 1058706@bugs.debian.org, "Otto Kekäläinen" <otto@debian.org>, "Faustin Lammler" <faustin@mariadb.org>
Betreff: Re: Aw: Re: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
Hello,
Thank you for testing. I assume these are different issues. Other happens in low end ARMv5 machine with 512 MB (memory which is kind of low now a days) and other is in normal server/laptop inside XEN machine (although i686? 32-bit still as armel). As I understand your problem is in initializing mysql-dir (which is mandatory) but MYISAM/Aria and InnoDB works ok?
But you can debug this (I ate my dogfood and tested not just write from the memory sorry for that)
shutdown mariadbd (which is not probably not running)
remove /var/lib/mysql which again will destroy your database (Please note)
use to install your database:
/usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql
Does it print some errors? Is there any errors in syslog? Does MariaDB start after this?
Sincerely,
Tuukka
k-i-r@web.de[mailto:k-i-r@web.de] kirjoitti 19.12.2023 klo 16.33:
Removing mariadb-server via apt purge also removes the user mysql.
--> chown mysql:mylsql doesn't work.
Reinstalling mariadb-server doesn't solve the issue.
Gesendet: Dienstag, 19. Dezember 2023 um 13:01 Uhr
Von: "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi>[mailto:tuukka.pasanen@ilmi.fi]
An: k-i-r@web.de[mailto:k-i-r@web.de]
Cc: "Scott Barker" <scott@mostlylinux.ca>[mailto:scott@mostlylinux.ca], 1058706@bugs.debian.org[mailto:1058706@bugs.debian.org], "Otto Kekäläinen" <otto@debian.org>[mailto:otto@debian.org], "Faustin Lammler" <faustin@mariadb.org>[mailto:faustin@mariadb.org]
Betreff: Re: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
Hello,
I've investigate this yesterday and I could reproduce this one:
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Aborting
Can you do (Please on testing machine not production will destroy your database!!!)
apt purge mariadb-server
# check is your database is not available /var/lib/mysql if it is remote it
mkdir -p /var/lib/mysql
chown mysql:mysql /var/lib/mysql
and then re-install mariad-server again. Does it work then? Just trying to see if my findings are correct. What comes to this InnoDB corruption I can't reproduce that.
Sincerely,
Tuukka
k-i-r@web.de[mailto:k-i-r@web.de] kirjoitti 19.12.2023 klo 12.18:
Hi Tuukka,
I don't think the issue is related to the armel hardware.
I see the same error on my XEN-VM (1 VCPU) based on a Intel(R) Celeron(R) CPU G3900 @ 2.80GHz processor with 2 cores.
No lack of memory could be seen during installation of mariadb-server package. I tested it with 2 or 8 GB of assigned RAM.
Regards,
Konstantin
Gesendet: Montag, 18. Dezember 2023 um 08:23 Uhr
Von: "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi>[mailto:tuukka.pasanen@ilmi.fi]
An: "Scott Barker" <scott@mostlylinux.ca>[mailto:scott@mostlylinux.ca], 1058706@bugs.debian.org[mailto:1058706@bugs.debian.org], "Otto Kekäläinen" <otto@debian.org>[mailto:otto@debian.org], k-i-r@web.de[mailto:k-i-r@web.de]
Cc: "Faustin Lammler" <faustin@mariadb.org>[mailto:faustin@mariadb.org]
Betreff: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel
Hello,
Have you monitored that is memory exhausted at the installation? This
could lead error like that.
I assume your XEN/KVM/Docker base machine is some older system with not
so fancy CPU or is there any particular reason to use armel build?
Sincerly,
Tuukka
Scott Barker kirjoitti 17.12.2023 klo 19.15:
Same result with the latest kernel:
Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel
GNU/Linux
On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote:
Prior to the installation, /var/lib/mysql did not exist. After
installation:
61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56
/var/lib/mysql
61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56
/var/lib/mysql/aria_log_control
61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56
/var/lib/mysql/ibdata1
61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56
/var/lib/mysql/debian-10.11.flag
61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56
/var/lib/mysql/ib_logfile101
61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56
/var/lib/mysql/aria_log.00000001
uname -a reports:
Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29)
armv5tel GNU/Linux
On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote:
Hi Scott and Kr!
Did you note this line?
2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero
bytes in
datafile: ./ibdata1, Space ID:0, Flags: 0
Can you include the output of `find /var/lib/mysql -ls` so we can
see what
files your system has?
What is the hardware you have? The report shows 'Linux
5.10.0-26-marvell '.
What does `uname -a` yield?
The test suite passes on armhf at
e.g. https://launchpad.net/~mysql-ubuntu/[https://launchpad.net/~mysql-ubuntu/]
+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all.
At https://
ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to
regression in
subselect which is unrelated to what you reported.
--
Scott Barker
--
To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org[mailto:1058706-unsubscribe@bugs.debian.org].
[toc] | [prev] | [next] | [standalone]
| From | Tuukka Pasanen <tuukka.pasanen@ilmi.fi> |
|---|---|
| Date | 2023-12-21 08:40 +0100 |
| Message-ID | <HNlOV-f2D1-5@gated-at.bofh.it> |
| In reply to | #1179447 |
Hello, Please see upstream as this seems to be very similar to your problem: https://jira.mariadb.org/browse/MDEV-27900 Sincerly, Tuukka k-i-r@web.de kirjoitti 20.12.2023 klo 11.27: > Starting point: > - Installed mariadb-server package which doesn't run > - /var/lib/mysql removed manually > - root@gast1:/var/lib# /usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql -- > error, see below > > root@gast1:/var/lib# /usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql > 231220 9:21:04 [ERROR] mysqld got signal 4 ; > 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.11.4-MariaDB-1~deb12u1 source revision: > 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 = 468022 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 0x49000 > /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5599a37984ae] > /usr/sbin/mariadbd(handle_fatal_signal+0x409)[0x5599a3305f49] > /lib/x86_64-linux-gnu/libc.so.6(+0x3bfd0)[0x7fb58645afd0] > /usr/sbin/mariadbd(+0x6f5d79)[0x5599a2fd2d79] > /usr/sbin/mariadbd(+0xe2590a)[0x5599a370290a] > /usr/sbin/mariadbd(+0x6862e2)[0x5599a2f632e2] > /usr/sbin/mariadbd(+0xcd9671)[0x5599a35b6671] > /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x5599a330927e] > Printing to addr2line failed > /usr/sbin/mariadbd(+0x80f997)[0x5599a30ec997] > /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x85a)[0x5599a30ed95a] > /usr/sbin/mariadbd(+0x701037)[0x5599a2fde037] > /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x41d)[0x5599a2fe3a5d] > /lib/x86_64-linux-gnu/libc.so.6(+0x271ca)[0x7fb5864461ca] > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7fb586446285] > /usr/sbin/mariadbd(_start+0x21)[0x5599a2fd8c81] > The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains > information that should help you find out what is causing the crash. > Writing a core file... > Working directory at /var/lib/mysql > Resource Limits: > Limit Soft Limit Hard Limit Units > Max cpu time unlimited unlimited seconds > Max file size unlimited unlimited bytes > Max data size unlimited unlimited bytes > Max stack size 8388608 unlimited bytes > Max core file size 0 unlimited bytes > Max resident set unlimited unlimited bytes > Max processes 31372 31372 processes > Max open files 32183 32183 files > Max locked memory 1045245952 1045245952 bytes > Max address space unlimited unlimited bytes > Max file locks unlimited unlimited locks > Max pending signals 31372 31372 signals > Max msgqueue size 819200 819200 bytes > Max nice priority 0 0 > Max realtime priority 0 0 > Max realtime timeout unlimited unlimited us > Core pattern: core > > Kernel version: Linux version 6.1.0-15-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) > > Illegal instruction > > Installation of system tables failed! Examine the logs in > /var/lib/mysql for more information. > > The problem could be conflicting information in an external > my.cnf files. You can ignore these by doing: > > shell> /usr/bin/mariadb-install-db --defaults-file=~/.my.cnf > > You can also try to start the mariadbd daemon with: > > shell> /usr/sbin/mariadbd --skip-grant-tables --general-log & > > and use the command line tool /usr/bin/mariadb > to connect to the mysql database and look at the grant tables: > > shell> /usr/bin/mariadb -u root mysql > MariaDB> show tables; > > Try '/usr/sbin/mariadbd --help' if you have problems with paths. Using > --general-log gives you a log in /var/lib/mysql that may be helpful. > > The latest information about mysql_install_db is available at > https://mariadb.com/kb/en/installing-system-tables-mysql_install_db > You can find the latest source at https://downloads.mariadb.org and > the maria-discuss email list at https://launchpad.net/~maria-discuss > > Please check all of the above before submitting a bug report > at https://mariadb.org/jira > > root@gast1:/var/lib# > > root@gast1:/var/lib# journalctl -u mariadb > Dec 20 09:20:36 gast1 systemd[1]: Starting mariadb.service - MariaDB 10.11.4 database server... > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 1310 > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Using transactional memory > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Number of transaction pools: 1 > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Using liburing > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Completed initialization of buffer pool > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrit> > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] InnoDB: Starting shutdown... > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Plugin 'InnoDB' init function returned error. > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [Note] Plugin 'FEEDBACK' is disabled. > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Unknown/unsupported storage engine: InnoDB > Dec 20 09:20:37 gast1 mariadbd[1310]: 2023-12-20 9:20:37 0 [ERROR] Aborting > Dec 20 09:20:37 gast1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE > Dec 20 09:20:37 gast1 systemd[1]: mariadb.service: Failed with result 'exit-code'. > Dec 20 09:20:37 gast1 systemd[1]: Failed to start mariadb.service - MariaDB 10.11.4 database server. > Dec 20 09:20:39 gast1 systemd[1]: Starting mariadb.service - MariaDB 10.11.4 database server... > Dec 20 09:20:39 gast1 mariadbd[1426]: 2023-12-20 9:20:39 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision as process 1426 > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Using transactional memory > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Number of transaction pools: 1 > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Using liburing > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Completed initialization of buffer pool > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrit> > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] InnoDB: Starting shutdown... > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Plugin 'InnoDB' init function returned error. > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [Note] Plugin 'FEEDBACK' is disabled. > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Unknown/unsupported storage engine: InnoDB > Dec 20 09:20:40 gast1 mariadbd[1426]: 2023-12-20 9:20:40 0 [ERROR] Aborting > Dec 20 09:20:40 gast1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE > Dec 20 09:20:40 gast1 systemd[1]: mariadb.service: Failed with result 'exit-code'. > Dec 20 09:20:40 gast1 systemd[1]: Failed to start mariadb.service - MariaDB 10.11.4 database server. > root@gast1:/var/lib# > > ------------------------------ > > > > > > > > > > Gesendet: Mittwoch, 20. Dezember 2023 um 09:43 Uhr > Von: "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi> > An: k-i-r@web.de > Cc: "Scott Barker" <scott@mostlylinux.ca>, 1058706@bugs.debian.org, "Otto Kekäläinen" <otto@debian.org>, "Faustin Lammler" <faustin@mariadb.org> > Betreff: Re: Aw: Re: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel > Hello, > Thank you for testing. I assume these are different issues. Other happens in low end ARMv5 machine with 512 MB (memory which is kind of low now a days) and other is in normal server/laptop inside XEN machine (although i686? 32-bit still as armel). As I understand your problem is in initializing mysql-dir (which is mandatory) but MYISAM/Aria and InnoDB works ok? > > But you can debug this (I ate my dogfood and tested not just write from the memory sorry for that) > shutdown mariadbd (which is not probably not running) > remove /var/lib/mysql which again will destroy your database (Please note) > use to install your database: > > /usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql > > Does it print some errors? Is there any errors in syslog? Does MariaDB start after this? > Sincerely, > Tuukka > > > k-i-r@web.de[mailto:k-i-r@web.de] kirjoitti 19.12.2023 klo 16.33: > > Removing mariadb-server via apt purge also removes the user mysql. > --> chown mysql:mylsql doesn't work. > Reinstalling mariadb-server doesn't solve the issue. > > > > Gesendet: Dienstag, 19. Dezember 2023 um 13:01 Uhr > > Von: "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi>[mailto:tuukka.pasanen@ilmi.fi] > An: k-i-r@web.de[mailto:k-i-r@web.de] > Cc: "Scott Barker" <scott@mostlylinux.ca>[mailto:scott@mostlylinux.ca], 1058706@bugs.debian.org[mailto:1058706@bugs.debian.org], "Otto Kekäläinen" <otto@debian.org>[mailto:otto@debian.org], "Faustin Lammler" <faustin@mariadb.org>[mailto:faustin@mariadb.org] > Betreff: Re: Aw: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel > Hello, > I've investigate this yesterday and I could reproduce this one: > Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded > Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB > Dec 17 11:17:55 gast1 mariadbd[1291]: 2023-12-17 11:17:55 0 [ERROR] Aborting > > Can you do (Please on testing machine not production will destroy your database!!!) > apt purge mariadb-server > # check is your database is not available /var/lib/mysql if it is remote it > mkdir -p /var/lib/mysql > chown mysql:mysql /var/lib/mysql > and then re-install mariad-server again. Does it work then? Just trying to see if my findings are correct. What comes to this InnoDB corruption I can't reproduce that. > > Sincerely, > Tuukka > > > k-i-r@web.de[mailto:k-i-r@web.de] kirjoitti 19.12.2023 klo 12.18: > Hi Tuukka, > I don't think the issue is related to the armel hardware. > I see the same error on my XEN-VM (1 VCPU) based on a Intel(R) Celeron(R) CPU G3900 @ 2.80GHz processor with 2 cores. > No lack of memory could be seen during installation of mariadb-server package. I tested it with 2 or 8 GB of assigned RAM. > > Regards, > Konstantin > > > Gesendet: Montag, 18. Dezember 2023 um 08:23 Uhr > Von: "Tuukka Pasanen" <tuukka.pasanen@ilmi.fi>[mailto:tuukka.pasanen@ilmi.fi] > An: "Scott Barker" <scott@mostlylinux.ca>[mailto:scott@mostlylinux.ca], 1058706@bugs.debian.org[mailto:1058706@bugs.debian.org], "Otto Kekäläinen" <otto@debian.org>[mailto:otto@debian.org], k-i-r@web.de[mailto:k-i-r@web.de] > Cc: "Faustin Lammler" <faustin@mariadb.org>[mailto:faustin@mariadb.org] > Betreff: Re: Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel > Hello, > > Have you monitored that is memory exhausted at the installation? This > could lead error like that. > > I assume your XEN/KVM/Docker base machine is some older system with not > so fancy CPU or is there any particular reason to use armel build? > > Sincerly, > > Tuukka > > Scott Barker kirjoitti 17.12.2023 klo 19.15: > Same result with the latest kernel: > > Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) armv5tel > GNU/Linux > > On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: > Prior to the installation, /var/lib/mysql did not exist. After > installation: > > 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 09:56 > /var/lib/mysql > 61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 09:56 > /var/lib/mysql/aria_log_control > 61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 09:56 > /var/lib/mysql/ibdata1 > 61963 0 -rw-r--r-- 1 root root 0 Dec 17 09:56 > /var/lib/mysql/debian-10.11.flag > 61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 09:56 > /var/lib/mysql/ib_logfile101 > 61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 09:56 > /var/lib/mysql/aria_log.00000001 > > uname -a reports: > > Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) > armv5tel GNU/Linux > > On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen wrote: > Hi Scott and Kr! > > Did you note this line? > > 2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero > bytes in > datafile: ./ibdata1, Space ID:0, Flags: 0 > > Can you include the output of `find /var/lib/mysql -ls` so we can > see what > files your system has? > > What is the hardware you have? The report shows 'Linux > 5.10.0-26-marvell '. > What does `uname -a` yield? > > The test suite passes on armhf at > e.g. https://launchpad.net/~mysql-ubuntu/[https://launchpad.net/~mysql-ubuntu/] > +archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all. > At https:// > ci.debian.net/packages/m/mariadb/unstable/armel/ it fails due to > regression in > subselect which is unrelated to what you reported. > > -- > Scott Barker > > -- > To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org[mailto:1058706-unsubscribe@bugs.debian.org]. > > > > > >
[toc] | [prev] | [next] | [standalone]
| From | Scott Barker <scott@mostlylinux.ca> |
|---|---|
| Date | 2023-12-21 16:30 +0100 |
| Message-ID | <HNt9M-f76l-29@gated-at.bofh.it> |
| In reply to | #1178750 |
Yes, this NAS unit also has 512M of RAM. Unfortunately, setting "innodb_flush_method=fsync" did not work. However, setting "innodb_use_native_aio=OFF" did work, but only after deleting the corrupted InnoDB files in /var/lib/mysql. On Thu, Dec 21, 2023 at 09:25:20AM +0200, Tuukka Pasanen wrote: >Hello, >Memory is still 512 MB? >Thing that pops to my eye in 10.11 is >mysqld: 2023-12-20 10:23:53 0 [ERROR] InnoDB: File ./ibdata1: 'aio read' >returned OS error 0. Cannot continue operation >As on 10.5 is used fsync not O_DIRECT which is default from 10.6 you can try >(not promising anything) get it 10.11 working (more slowly though) with: >innodb_flush_method=fsync >More on change here: > >https://mariadb.com/kb/en/innodb-system-variables/#innodb_use_native_aio > >Sincerely, >Tuukka > > >Scott Barker kirjoitti 21.12.2023 klo 0.20: > > On my secondard ARM NAS, I downgraded from bookworm to bullseye, and > installed mariadb 10.5 from scratch (no pre-existing /var/lib/mysql or /etc > /mysql). Everything worked without issues. From syslog: > > mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql > mysqld: 2023-12-20 7:58:07 0 [Note] Starting MariaDB > 10.5.21-MariaDB-0+deb11u1 source revision > bed70468ea08c2820647f5e3ac006a9ff88144ac as process 2250 > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Uses event mutexes > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Compressed tables use zlib > 1.2.11 > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Number of pools: 1 > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using generic crc32 > instructions > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using Linux native AIO > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Initializing buffer pool, > total size = 134217728, chunk size = 134217728 > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Completed initialization of > buffer pool > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 128 rollback segments are > active. > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Creating shared tablespace for > temporary tables > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Setting file './ibtmp1' size > to 12 MB. Physically writing the file full; Please wait ... > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: File './ibtmp1' size is now 12 > MB. > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 10.5.21 started; log sequence > number 45079; transaction id 20 > mysqld: 2023-12-20 7:58:07 0 [Note] Plugin 'FEEDBACK' is disabled. > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Loading buffer pool(s) from / > var/lib/mysql/ib_buffer_pool > mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Buffer pool(s) load completed > at 231220 7:58:07 > mysqld: 2023-12-20 7:58:07 0 [Note] Server socket created on IP: > '127.0.0.1'. > mysqld: 2023-12-20 7:58:07 0 [Note] Reading of all Master_info entries > succeeded > mysqld: 2023-12-20 7:58:07 0 [Note] Added new Master_info '' to hash table > mysqld: 2023-12-20 7:58:07 0 [Note] /usr/sbin/mariadbd: ready for > connections. > mysqld: Version: '10.5.21-MariaDB-0+deb11u1' socket: '/run/mysqld/ > mysqld.sock' port: 3306 Debian 11 > > I then proceeded to upgrade from bookworm all packages containing libraries > to which /usr/sbin/mariadbd and /usr/lib/mysql/plugin/* were linked, one at > a time, restarting mariadb after each package was installed, and there were > no issues. > > I then upgraded the rest of the system to bookworm, a few packages at a > time, excluding the mariadb packages. I restarted mariadb after each batch > of packages, and there were no issues, including after reboot into the new > kernel. > > I then renamed /var/lib/mysql to /var/lib/mysql.bak and ran: > > dpkg-reconfigure -plow mariadb-server-10.5 mariadb-server-core-10.5 > > Again, no issues - /var/lib/mysql was re-created and mariadbd started just > fine, with the same syslog entries as above. > > I then copied /var/lib/mysql to /var/lib/mysql-10.5 and upgraded mariadb > with: > > apt upgrade mariadb-server-10.5 > > Here is the entire output, you can see the errors at the end: > > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-core-10.5 > The following NEW packages will be installed: > libnuma1 liburing2 mariadb-client mariadb-client-core mariadb-server > mariadb-server-core > The following packages will be upgraded: > mariadb-server-10.5 > 1 upgraded, 6 newly installed, 3 to remove and 0 not upgraded. > Need to get 12.7 MB of archives. > After this operation, 28.0 MB of additional disk space will be used. > Do you want to continue? [Y/n] > Get:1 https://deb.debian.org/debian bookworm/main armel mariadb-server-10.5 > armel 1:10.11.4-1~deb12u1 [22.7 kB] > Get:2 https://deb.debian.org/debian bookworm/main armel mariadb-client-core > armel 1:10.11.4-1~deb12u1 [754 kB] > Get:3 https://deb.debian.org/debian bookworm/main armel mariadb-client > armel 1:10.11.4-1~deb12u1 [2,510 kB] > Get:4 https://deb.debian.org/debian bookworm/main armel libnuma1 armel > 2.0.16-1 [18.3 kB] > Get:5 https://deb.debian.org/debian bookworm/main armel liburing2 armel > 2.3-3 [13.2 kB] > Get:6 https://deb.debian.org/debian bookworm/main armel mariadb-server-core > armel 1:10.11.4-1~deb12u1 [6,328 kB] > Get:7 https://deb.debian.org/debian bookworm/main armel mariadb-server > armel 1:10.11.4-1~deb12u1 [3,027 kB] > Fetched 12.7 MB in 5s (2,486 kB/s) > Preconfiguring packages ... > (Reading database ... 24167 files and directories currently installed.) > Preparing to unpack .../mariadb-server-10.5_1%3a10.11.4-1~deb12u1_armel.deb > ... > Stopping MariaDB database server: mariadbd. > Unpacking mariadb-server-10.5 (1:10.11.4-1~deb12u1) over > (1:10.5.21-0+deb11u1) ... > (Reading database ... 24042 files and directories currently installed.) > Removing mariadb-client-10.5 (1:10.5.21-0+deb11u1) ... > Removing mariadb-client-core-10.5 (1:10.5.21-0+deb11u1) ... > Removing mariadb-server-core-10.5 (1:10.5.21-0+deb11u1) ... > Selecting previously unselected package mariadb-client-core. > (Reading database ... 23850 files and directories currently installed.) > Preparing to unpack .../ > 0-mariadb-client-core_1%3a10.11.4-1~deb12u1_armel.deb ... > Unpacking mariadb-client-core (1:10.11.4-1~deb12u1) ... > Selecting previously unselected package mariadb-client. > Preparing to unpack .../1-mariadb-client_1%3a10.11.4-1~deb12u1_armel.deb > ... > Unpacking mariadb-client (1:10.11.4-1~deb12u1) ... > Selecting previously unselected package libnuma1:armel. > Preparing to unpack .../2-libnuma1_2.0.16-1_armel.deb ... > Unpacking libnuma1:armel (2.0.16-1) ... > Selecting previously unselected package liburing2:armel. > Preparing to unpack .../3-liburing2_2.3-3_armel.deb ... > Unpacking liburing2:armel (2.3-3) ... > Selecting previously unselected package mariadb-server-core. > Preparing to unpack .../ > 4-mariadb-server-core_1%3a10.11.4-1~deb12u1_armel.deb ... > Unpacking mariadb-server-core (1:10.11.4-1~deb12u1) ... > Selecting previously unselected package mariadb-server. > Preparing to unpack .../5-mariadb-server_1%3a10.11.4-1~deb12u1_armel.deb > ... > /var/lib/mysql: found previous version 10.5 > Unpacking mariadb-server (1:10.11.4-1~deb12u1) ... > Setting up mariadb-client-core (1:10.11.4-1~deb12u1) ... > Setting up libnuma1:armel (2.0.16-1) ... > Setting up liburing2:armel (2.3-3) ... > Setting up mariadb-client (1:10.11.4-1~deb12u1) ... > Setting up mariadb-server-core (1:10.11.4-1~deb12u1) ... > Setting up mariadb-server (1:10.11.4-1~deb12u1) ... > Installing new version of config file /etc/init.d/mariadb ... > Installing new version of config file /etc/logrotate.d/mariadb ... > Installing new version of config file /etc/mysql/debian-start ... > Installing new version of config file /etc/mysql/mariadb.conf.d/ > 50-server.cnf ... > Stopping MariaDB database server: mariadbd. > Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . > . . . . . . . . . . . . . . failed! > invoke-rc.d: initscript mariadb, action "start" failed. > dpkg: error processing package mariadb-server (--configure): > installed mariadb-server package post-installation script subprocess > returned error exit status 1 > dpkg: dependency problems prevent configuration of mariadb-server-10.5: > mariadb-server-10.5 depends on mariadb-server (>= 1:10.11); however: > Package mariadb-server is not configured yet. > > dpkg: error processing package mariadb-server-10.5 (--configure): > dependency problems - leaving unconfigured > Processing triggers for libc-bin (2.36-9+deb12u3) ... > Errors were encountered while processing: > mariadb-server > mariadb-server-10.5 > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Here is what was logged to syslog: > > mariadb-server.postinst[3596]: mysql.user table already exists! > mariadb-server.postinst[3596]: Run mysql_upgrade, not mysql_install_db > mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql > mysqld: 2023-12-20 10:23:51 0 [Note] Starting MariaDB > 10.11.4-MariaDB-1~deb12u1 source revision as process 3765 > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Compressed tables use zlib > 1.2.13 > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Number of transaction pools: 1 > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Using generic crc32 > instructions > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Using liburing > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Initializing buffer pool, > total size = 128.000MiB, chunk size = 2.000MiB > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Completed initialization of > buffer pool > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File system buffers for log > disabled (block size=4096 bytes) > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Upgrading redo log: 96.000MiB; > LSN=45767 > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File system buffers for log > disabled (block size=4096 bytes) > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: 128 rollback segments are > active. > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Setting file './ibtmp1' size > to 12.000MiB. Physically writing the file full; Please wait ... > mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File './ibtmp1' size is now > 12.000MiB. > mysqld: 2023-12-20 10:23:53 0 [Note] InnoDB: log sequence number 45767; > transaction id 20 > mysqld: 2023-12-20 10:23:53 0 [Note] InnoDB: Loading buffer pool(s) from / > var/lib/mysql/ib_buffer_pool > mysqld: 2023-12-20 10:23:53 0 [Note] Plugin 'FEEDBACK' is disabled. > mysqld: 2023-12-20 10:23:53 0 [ERROR] InnoDB: File ./ibdata1: 'aio read' > returned OS error 0. Cannot continue operation > mysqld: 231220 10:23:53 [ERROR] mysqld got signal 6 ; > mysqld: This could be because you hit a bug. It is also possible that this > binary > mysqld: or one of the libraries it was linked against is corrupt, > improperly built, > mysqld: or misconfigured. This error can also be caused by malfunctioning > hardware. > mysqld: mysqld: To report this bug, see https://mariadb.com/kb/en/ > reporting-bugs > mysqld: mysqld: We will try our best to scrape up some info that will > hopefully help > mysqld: diagnose the problem, but since we have already crashed, mysqld: > something is definitely wrong and this may fail. > mysqld: mysqld: Server version: 10.11.4-MariaDB-1~deb12u1 source revision: > mysqld: key_buffer_size=134217728 > mysqld: read_buffer_size=131072 > mysqld: max_used_connections=0 > mysqld: max_threads=153 > mysqld: thread_count=1 > mysqld: It is possible that mysqld could use up to mysqld: key_buffer_size > + (read_buffer_size + sort_buffer_size)*max_threads = 466625 K bytes of > memory > mysqld: Hope that's ok; if not, decrease some variables in the equation. > mysqld: mysqld: Thread pointer: 0x0 > mysqld: Attempting backtrace. You can use the following information to find > out > mysqld: where mysqld died. If you see no messages after this, something > went > mysqld: terribly wrong... > mysqld: stack_bottom = 0x0 thread_stack 0x49000 > mysqld: The manual page at https://mariadb.com/kb/en/ > how-to-produce-a-full-stack-trace-for-mysqld/ contains > mysqld: information that should help you find out what is causing the > crash. > mysqld: Writing a core file... > mysqld: Working directory at /var/lib/mysql > mysqld: Resource Limits: > mysqld: Limit Soft Limit Hard Limit > Units mysqld: Max cpu time unlimited > unlimited seconds mysqld: Max file size > unlimited unlimited bytes mysqld: Max data > size unlimited unlimited bytes > mysqld: Max stack size 8388608 unlimited > bytes mysqld: Max core file size 0 > unlimited bytes mysqld: Max resident set > unlimited unlimited bytes mysqld: Max > processes 1904 1904 processes > mysqld: Max open files 32183 32183 > files mysqld: Max locked memory 8388608 > 8388608 bytes mysqld: Max address space > unlimited unlimited bytes mysqld: Max file > locks unlimited unlimited locks > mysqld: Max pending signals 1904 1904 > signals mysqld: Max msgqueue size 819200 > 819200 bytes mysqld: Max nice priority > 0 0 mysqld: Max realtime priority > 0 0 mysqld: Max realtime timeout > unlimited unlimited us mysqld: Core pattern: > core > mysqld: mysqld: Kernel version: Linux version 6.1.0-16-marvell ( > debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld > (GNU Binutils for Debian) 2.40) #1 Debian 6.1.67-1 (2023-12-12) > mysqld: mysqld_safe: mysqld from pid file /run/mysqld/mysqld.pid ended > /etc/init.d/mariadb[4054]: 0 processes alive and '/usr/bin/mariadb-admin > --defaults-file=/etc/mysql/debian.cnf ping' resulted in > /etc/init.d/mariadb[4054]: #007/usr/bin/mariadb-admin: connect to server at > 'localhost' failed > /etc/init.d/mariadb[4054]: error: 'Can't connect to local server through > socket '/run/mysqld/mysqld.sock' (2)' > /etc/init.d/mariadb[4054]: Check that mariadbd is running and that the > socket: '/run/mysqld/mysqld.sock' exists! > > After the upgrade, a "diff" on the two mysql folders shows: > > Only in mysql/: ddl_recovery.log > Only in mysql/: debian-10.11.flag > Only in mysql-10.5/: debian-10.5.flag > Binary files mysql-10.5/ib_logfile0 and mysql/ib_logfile0 differ > Only in mysql/: ibtmp1 > > No other files changed. > > I then added these two lines in the [server] section of /etc/mysql/ > mariadb.conf.d/50-server.cnf: > > innodb = OFF > default-storage-engine = MyISAM > > Then I ran: > > apt install -f > > After this, mariadbd started successfully, but without the InnoDB engine, > as can be seen in syslog: > > mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql > mysqld: 2023-12-20 11:01:31 0 [Note] Starting MariaDB > 10.11.4-MariaDB-1~deb12u1 source revision as process 5560 > mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'InnoDB' is disabled. > mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'FEEDBACK' is disabled. > mysqld: 2023-12-20 11:01:32 0 [Warning] You need to use --log-bin to make > --expire-logs-days or --binlog-expire-logs-seconds work. > mysqld: 2023-12-20 11:01:32 0 [Note] Server socket created on IP: > '127.0.0.1'. > mysqld: 2023-12-20 11:01:32 0 [Note] /usr/sbin/mariadbd: ready for > connections. > mysqld: Version: '10.11.4-MariaDB-1~deb12u1' socket: '/run/mysqld/ > mysqld.sock' port: 3306 Debian 12 > /etc/mysql/debian-start[5589]: Upgrading MySQL tables if necessary. > /etc/mysql/debian-start[5599]: Checking for insecure root accounts. > /etc/mysql/debian-start[5603]: Triggering myisam-recover for all MyISAM > tables and aria-recover for all Aria tables > > On Tue, Dec 19, 2023 at 08:07:16AM -0700, Scott Barker wrote: > > For myself, I am not using XEN/KVM/Docker. I am installing this on a > NAS device with an ARM chip and only 512M of RAM. I tried adding a 2G > swap file, but it did not make a difference. I was able to start > mariadb by disabling INNODB and using MyISAM instead with the options: > > --innodb=OFF --default-storage-engine=MyISAM > > On Mon, Dec 18, 2023 at 09:23:55AM +0200, Tuukka Pasanen wrote: > > Hello, > > Have you monitored that is memory exhausted at the installation? > This could lead error like that. > > I assume your XEN/KVM/Docker base machine is some older system with > not so fancy CPU or is there any particular reason to use armel > build? > > Sincerly, > > Tuukka > > Scott Barker kirjoitti 17.12.2023 klo 19.15: > > Same result with the latest kernel: > > Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12) > armv5tel GNU/Linux > > On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker wrote: > > Prior to the installation, /var/lib/mysql did not exist. > After installation: > > 61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17 > 09:56 /var/lib/mysql > 61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17 > 09:56 /var/lib/mysql/aria_log_control > 61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17 > 09:56 /var/lib/mysql/ibdata1 > 61963 0 -rw-r--r-- 1 root root 0 Dec 17 > 09:56 /var/lib/mysql/debian-10.11.flag > 61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17 > 09:56 /var/lib/mysql/ib_logfile101 > 61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17 > 09:56 /var/lib/mysql/aria_log.00000001 > > uname -a reports: > > Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1 > (2023-09-29) armv5tel GNU/Linux > > On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen > wrote: > > Hi Scott and Kr! > > Did you note this line? > > 2023-12-14 14:51:33 0 [Note] InnoDB: Header page > consists of zero bytes in > datafile: ./ibdata1, Space ID:0, Flags: 0 > > Can you include the output of `find /var/lib/mysql -ls > ` so we can see what > files your system has? > > What is the hardware you have? The report shows 'Linux > 5.10.0-26-marvell '. > What does `uname -a` yield? > > The test suite passes on armhf at e.g. https:// > launchpad.net/~mysql-ubuntu/ > +archive/ubuntu/mariadb-10.11/+builds?build_text=& > build_state=all. At https:// > ci.debian.net/packages/m/mariadb/unstable/armel/ it > fails due to regression in > subselect which is unrelated to what you reported. > > > > -- > Scott Barker > > -- > To unsubscribe, send mail to > 1058706-unsubscribe@bugs.debian.org. > > > > > -- > Scott Barker > > -- > To unsubscribe, send mail to 1058706-unsubscribe@bugs.debian.org. > > > -- Scott Barker
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web