Greetings.
It seems that for one reason or another, fairly quick upgrade of Log4OMv2 database
- to comply with Debian Bookworm OS - is not going to happen...
Devoted quite a lot of time to find working solution and finally managed it, Hi!!!
I spare most of my work and testing. Will describe only necessary and important steps.
All in all, performed many time consuming tasks.
Environment I worked with:
- desktop PC - W10 22H2 with running Log4OM 2 v2.33.0.0
- RPi400, Debian 12.7, mariadb Ver 15.1 Distrib 10.5.26-MariaDB
(YES! I intentionally uninstalled original 10.11.6 and installed above!)
Whole process I tried to describe in a manner that even layman should understand, Hi!
This "recipe" pertains
__ONLY__ to RaspberryPi OS'es!
Download from
https://www.raspberrypi.com/software/operating-systems/
"Raspberry Pi OS with desktop and recommended software"
file:
2024-10-22-raspios-bookworm-arm64-full.img.xz
(or any other of one's choice!) and etch it on SD card.
Once Debian 12.7 starts as expected we can proceed further.
Uninstal manually or by means of Synaptic, files similar
to listed few lines below but belonging to MariaDB-10.11.6 set
(or any others higher than 10.5.26).
Double/triple check that files related to MariaDB-10.11.6
were removed/purged from the working system!
As Raspberry Pi OS 12 bookworm local apt packages archive
doesn't include older versions of packages related to mariadb-10.5.26
download needed single files from this website:
http://archive.raspbian.org/raspbian/po ... iadb-10.5/
Alternatively from
https://dlm.mariadb.com/browse/mariadb_ ... 26/?flat=1
download file named
mariadb-10.5.26-debian-bullseye-arm64-debs.tar
which contains all files related to MariaDB 10.5.26
Only folowing *.deb files are needed:
galera-4_26.4.19-deb11_arm64.deb
libmariadb3_10.5.26+maria~deb11_arm64.deb
mariadb-backup_10.5.26+maria~deb11_arm64.deb
mariadb-client-10.5_10.5.26+maria~deb11_arm64.deb
mariadb-client-core-10.5_10.5.26+maria~deb11_arm64.deb
mariadb-client_10.5.26+maria~deb11_all.deb
mariadb-common_10.5.26+maria~deb11_all.deb
mariadb-server-10.5_10.5.26+maria~deb11_arm64.deb
mariadb-server-core-10.5_10.5.26+maria~deb11_arm64.deb
mariadb-server_10.5.26+maria~deb11_all.deb
mysql-common_10.5.26+maria~deb11_all.deb
Put these files in any empy directory of your choice.
In terminal window issue command:
cd /path/to/directory/of/your/choice
Then issue next command:
dpkg --force-depends -i ./*
This will install our packages in necessary order
insuring required dependencies.
After installation completes, RPi OS will attempt to start MariaDB.
To see if it works, in terminal window issue:
systemctl status mariadb
Output similar to this below means that everything went O.K!:
Quote
● mariadb.service - MariaDB 10.5.26 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-11-05 08:34:14 CET; 1 day 6h ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 598 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCES>
Process: 621 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCE>
Process: 625 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`;>
Process: 749 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCC>
Process: 752 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
Main PID: 709 (mariadbd)
Status: "Taking your SQL requests now..."
Tasks: 11 (limit: 10550)
CPU: 9min 4.337s
CGroup: /system.slice/mariadb.service
└─709 /usr/sbin/mariadbd
Nov 05 08:34:09 rpi4b systemd[1]: Starting MariaDB 10.5.26 database server...
Nov 05 08:34:10 rpi4b mariadbd[709]: 2024-11-05 8:34:10 0 [ERROR] feedback plugin: failed to retrieve the MAC address
Nov 05 08:34:14 rpi4b systemd[1]: Started MariaDB 10.5.26 database server.
Nov 05 08:34:14 rpi4b /etc/mysql/debian-start[758]: Looking for 'mariadb' as: /usr/bin/mariadb
Nov 05 08:34:14 rpi4b /etc/mysql/debian-start[758]: Looking for 'mariadb-check' as: /usr/bin/mariadb-check
Nov 05 08:34:14 rpi4b /etc/mysql/debian-start[758]: This installation of MariaDB is already upgraded to 10.5.26-MariaDB.
Nov 05 08:34:14 rpi4b /etc/mysql/debian-start[758]: There is no need to run mysql_upgrade again for 10.5.26-MariaDB.
Nov 05 08:34:14 rpi4b /etc/mysql/debian-start[758]: You can use --force if you still want to run mysql_upgrade
Nov 05 08:34:14 rpi4b /etc/mysql/debian-start[766]: Checking for insecure root accounts.
Unquote
If MariaDB doesn't start automatically & properly,
it's time to configure MariaDB server & client.
Please note that pop-up window with message "Database seems not valid"
appears also in very trivial situations, like for instance
lack of connection to computer running MariaDB server, Hi!!!
I strongly suggest usage of
Synaptic package manager
as it simplifies many important tasks to be performed,
like for instance locking "our" newly installed packages
from being mistakenly or accidentally upgraded!!!
Hovever this can be done also directly from terminal window
but requires knowledge on syntax of commands to be used.
See here:
https://askubuntu.com/questions/18654/h ... ic-package
and there
https://www.tecmint.com/disable-lock-bl ... debian-apt
Last but not least, I also strongly suggest to install
and fire up automatic system and/or single directories backups
which in case of SD cards I consider it almost "the must"!
