mariadb from Debian 12 (bookworm)

[dl3hm]

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

[SP2L]

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!

Database-seems-not-valid.jpg (10.62 KiB) Viewed 1385 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?

[va7gp]

I just upgraded today, from Debian 10 to Debian 12.5 (bookworm). I too cannot access my Log4OM database
Log4OM version 2.32.1.0 (latest stable)

On my remote server, I can see Log4OM connecting / contacting the server:

Code: Select all

240531 14:08:37	    31 Connect	log4om@192.168.2.4 on log4om using TCP/IP
		    31 Query	SELECT @@max_allowed_packet, @@character_set_client, 
        @@character_set_connection, @@license, @@sql_mode, @@lower_case_table_names, @@autocommit
240531 14:11:12	    32 Connect	log4om@142.58.181.248 on log4om using TCP/IP
		    32 Query	SELECT @@max_allowed_packet, @@character_set_client, 
        @@character_set_connection, @@license, @@sql_mode, @@lower_case_table_names, @@autocommit
		    32 Query	SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP())
		    32 Query	SHOW COLLATION
		    32 Quit	

But Log4OM doesn't comprehend what is returned, and gives "Database seems not valid". Like Original Poster and succeeding ...
Can this be addressed?

[va7gp]

To be thorough, I set up Debian 11 to check if this intermediate step (for me, in my upgrade path) would work.... It Does NOT. Debian 11 produces the same result as Debian 12: "Database seems not valid"

Debian 10 shows, in response to

Code: Select all

MariaDB [log4om]> show collation like 'utf8%';

(selected relevant extracts)

Code: Select all

+------------------------------+---------+------+---------+----------+---------+
| Collation                    | Charset | Id   | Default | Compiled | Sortlen |
+------------------------------+---------+------+---------+----------+---------+
| utf8_general_ci              | utf8    |   33 | Yes     | Yes      |       1 |
| utf8_bin                     | utf8    |   83 |         | Yes      |       1 |
| utf8mb4_general_ci           | utf8mb4 |   45 | Yes     | Yes      |       1 |
| utf8mb4_bin                  | utf8mb4 |   46 |         | Yes      |       1 |

WHEREAS Debian 12.5 shows only:

Code: Select all

+--------------------------------+---------+------+---------+----------+---------+
| Collation                      | Charset | Id   | Default | Compiled | Sortlen |
+--------------------------------+---------+------+---------+----------+---------+
| utf8mb3_general_ci             | utf8mb3 |   33 | Yes     | Yes      |       1 |
| utf8mb3_bin                    | utf8mb3 |   83 |         | Yes      |       1 |

[ak7vv]

The database client in Log4OM2 needs to be updated, as was discussed in another thread on the topic. Until that's done, you're stuck with older version of MariaDB/MySQL. This was supposed to happen in the next build but I haven't seen a change. I run a different version (10.6) of MariaDB just for Log4OM2 for just that reason.