I have used mariadb from Debian-stable togehter with Log4OM(2) since years without problems. With the update to Debian 12 (bookworm) it does not work any longer.
The problem has something to do with an incompatibility between newer versions of mariadb and original MySQL software used by Log4OM2:
https://stackoverflow.com/questions/740 ... ast-from-d
The solution suggested in the following link does not work for me:
https://forum.log4om.com/viewtopic.php?f=31&t=6991
A further relatet link without solution:
https://forum.log4om.com/viewtopic.php?p=43835
What worked for me, was to install the original MySQL-Docker image in parallel to the existing mariadb:
https://hub.docker.com/r/mysql/mysql-server/
I have used the additional info from here:
https://geshan.com.np/blog/2022/02/mysq ... r-compose/
Docker was installed using the following guide:
https://docs.docker.com/engine/install/ ... repository
Since this procedure is very complex it would be highly appreciated if Log4OM2 would be modified in a way that it works with a current version of mariadb. Probably a change from MySql.Data.MySqlClient to MySqlConnector has to be done, as suggested by the first link above.
73 Harald, DL3HM
mariadb from Debian 12 (bookworm)
Re: mariadb from Debian 12 (bookworm)
Greetings.
I came across exactly the same problem like Harald when trying to use
for Log4OMv2 MariaDB 10.11.6 on Debian Bookworm 12.5 running on RPi4B.
The answer from remote MariaDB server is always "Database seems not valid".
Been searching Internet for any usable solution, to no avail so far.
MariaDB on Bullseye uses utf8_general_ci collation
whereas MariaDB on Bookworm uses utf8mb3_general_ci collation.
The latter do not offer at all utf8_general_ci collation.
Most probably this is the culprit, Hi!
Need to mention that MariaDB (and all databases) on Debian 12.5 Bookworm
are perfectly manageable from any machine on LAN by means of PHPMyAdmin via web browser.
Changing MariaDB to MySQL is NOT an option for me!
Any thougts/suggestions, please?
I came across exactly the same problem like Harald when trying to use
for Log4OMv2 MariaDB 10.11.6 on Debian Bookworm 12.5 running on RPi4B.
The answer from remote MariaDB server is always "Database seems not valid".
Been searching Internet for any usable solution, to no avail so far.
MariaDB on Bullseye uses utf8_general_ci collation
whereas MariaDB on Bookworm uses utf8mb3_general_ci collation.
The latter do not offer at all utf8_general_ci collation.
Most probably this is the culprit, Hi!
- Database-seems-not-valid.jpg (10.62 KiB) Viewed 858 times
Need to mention that MariaDB (and all databases) on Debian 12.5 Bookworm
are perfectly manageable from any machine on LAN by means of PHPMyAdmin via web browser.
Changing MariaDB to MySQL is NOT an option for me!
Any thougts/suggestions, please?
