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
Hello,
Please see upstream as this seems to be very similar to your problem:
https://jira.mariadb.org/browse/MDEV-27900
Sincerly,
Tuukka
k-...@web.de kirjoitti 20.12.2023 klo 11.27:
Starting point:
- Installed mariadb-server package which doesn't run
- /var/lib/mysql removed manually
-
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
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
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
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
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
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
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
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
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
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 mysql52 Dec 17 09:56
/var/lib/mysql/aria_log_control
61983 12304 -rw-rw 1 mysql mysql 12582912
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
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
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.
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,
16 matches
Mail list logo
