Please let me know when the beta includes updated drivers.
73 Christian AK7VV
MariaDB configuration problems
Re: MariaDB configuration problems
GM,
gentlemen I tried 2.30.1.5 beta with mariaDB 10.11.6 and can confirm that the mentioned version has the same issues.
I'll be glad to test any new beta version when available.
Daniele, many thanks to you and your teammates for the outstanding work you do with Log4om for our community.
Tomas, OM5AST
gentlemen I tried 2.30.1.5 beta with mariaDB 10.11.6 and can confirm that the mentioned version has the same issues.
I'll be glad to test any new beta version when available.
Daniele, many thanks to you and your teammates for the outstanding work you do with Log4om for our community.
Tomas, OM5AST
Re: MariaDB configuration problems
GA,
I tried to use MySQL 8.3 instead of MariaDB 10.11.6. I installed a standalone independent MySQL8.3 instance on port 3336 and left MariaDB as it is.
I can confirm that Log4OM v.2.30.1.5 beta works perfectly on MySQL 8.3 with the following settings:
- changed default auth to authentication-policy=mysql_native_password in [mysqld] section of my.ini file
- in the database screen in Log4om settings use appropriate settings with a correct port for database creation and do not forget to USE SSL as this is a default option for MySQL 8.3
- be very careful to not overwrite your old database, watch your steps with ports and instances
- you can play with default settings, e.g. disable MySQL SSL if you wish but it was not necessary as this worked out-of-the-box
I did a mysqldump from MariaDB log4om2 database and imported it to the MySQL log4om2 database.
I'll use this setup temporarily until a fix is available, and then I'll migrate back to MariaDB 10.11.
Hope this helps if you want to use Log4OM and don't want to downgrade or sideload MariaDB.
Tomas, OM5AST
I tried to use MySQL 8.3 instead of MariaDB 10.11.6. I installed a standalone independent MySQL8.3 instance on port 3336 and left MariaDB as it is.
I can confirm that Log4OM v.2.30.1.5 beta works perfectly on MySQL 8.3 with the following settings:
- changed default auth to authentication-policy=mysql_native_password in [mysqld] section of my.ini file
- in the database screen in Log4om settings use appropriate settings with a correct port for database creation and do not forget to USE SSL as this is a default option for MySQL 8.3
- be very careful to not overwrite your old database, watch your steps with ports and instances
- you can play with default settings, e.g. disable MySQL SSL if you wish but it was not necessary as this worked out-of-the-box
I did a mysqldump from MariaDB log4om2 database and imported it to the MySQL log4om2 database.
I'll use this setup temporarily until a fix is available, and then I'll migrate back to MariaDB 10.11.
Hope this helps if you want to use Log4OM and don't want to downgrade or sideload MariaDB.
Tomas, OM5AST
Re: MariaDB configuration problems
I'd like to join the 'me too' bandwagon.
I went on to install latest MariaDB on a new Ubuntu server last night and ran into this problem.
Server version: 10.6.16-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04 (current - working)
Server version: 10.11.6-MariaDB-0ubuntu0.23.10.2 Ubuntu 23.10 (new)
I was scratching my head for a while as I could connect remotely to new database from MYSQL workbench but LOG4OM2, latest v2.31.0.0 kept failing with the "database seems not correct' error
17:21:23.95 Error: [DbMysql][Connect] : [EXCEPTION] Object cannot be cast from DBNull to other types.
17:21:23.952 Warn: [DatabaseManagement][TestConnection] : Connection not valid
73, Nick VE3EY
I went on to install latest MariaDB on a new Ubuntu server last night and ran into this problem.
Server version: 10.6.16-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04 (current - working)
Server version: 10.11.6-MariaDB-0ubuntu0.23.10.2 Ubuntu 23.10 (new)
I was scratching my head for a while as I could connect remotely to new database from MYSQL workbench but LOG4OM2, latest v2.31.0.0 kept failing with the "database seems not correct' error
17:21:23.95 Error: [DbMysql][Connect] : [EXCEPTION] Object cannot be cast from DBNull to other types.
17:21:23.952 Warn: [DatabaseManagement][TestConnection] : Connection not valid
73, Nick VE3EY
