Log4OM

va7gp

and also:

# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

va7gp

# mariadb -V
mariadb Ver 15.1 Distrib 10.11.6-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper

va7gp

I was considering following PA0PLY's approach (install real, actual MySQL). But I waited instead...
I am PLEASED to say that Log4OM 2.34.0.0 (released Nov 9 2024 I think) does entirely solve this! I upgraded from Debian 10, through Debian 11, to a final destination of Debian 12 and Log4OM was happy ...

va7gp

I am curious where this may lie, in Log4OM attention? Now that this thread is 18 months old.
Just curious...

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 MariaDB [log4om]> show collation like 'utf8%'; (selected ...

va7gp

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

On my remote server, I can see Log4OM connecting / contacting the server:
240531 14:08:37 31 Connect log4om@192.168.2.4 on log4om using TCP/IP
31 ...

Search found 6 matches

Re: MariaDB configuration problems

Re: MariaDB configuration problems

Re: MariaDB configuration problems

Re: MariaDB configuration problems

Re: mariadb from Debian 12 (bookworm)

Re: mariadb from Debian 12 (bookworm)