cqrlog needs to depend on mariadb instead of mysql

[Manoj Iyer]

Please update the cqrlog package (debian/control) to depend on mariadb server instead of mysql server.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Luc Langehegermann (lucl)]

This is still an issue in recent ubuntu Versions. CQRLOG does not work with recent Versions of mysql, only with mariadb.

The dependency in the package is default-mysql-core, which points to mysql on Ubuntu. Changing that to mariadb would likely fix the issue.

On the CQRLOG Forums, there are multiple such issues reported, one recent post: https://www.cqrlog.com/node/3476

Luc

[Koos van den Hout (koos-kzdoos)]

Still happening with Ubuntu 22.04. I'll attach the output of cqrlog --debug=1 and the mysql.err file.

[Koos van den Hout (koos-kzdoos)]

console messages with cqrlog --debug=1

[Koos van den Hout (koos-kzdoos)]

mysql.err file

[AsciiWolf (asciiwolf)]

CQRLOG (2.5.2-3ubuntu2) still does not seem to run on Ubuntu 24.04 because it cannot connect to the MySQL database. See the attached screenshot. I cannot believe that this was still not fixed after 4 years!

This is in the mysql.err log file:
2024-06-18T10:30:05.440022Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.37-0ubuntu0.24.04.1) starting as process 15289
2024-06-18T10:30:05.441321Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-06-18T10:30:05.441336Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8mb3_bin' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2024-06-18T10:30:05.459006Z 0 [Warning] [MY-010075] [Server] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: ba6b7bc4-2d5d-11ef-963e-525400dd5534.
2024-06-18T10:30:05.465986Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2024-06-18T10:30:05.466138Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-06-18T10:30:05.466158Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-06-18T10:30:05.466733Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.37-0ubuntu0.24.04.1) (Ubuntu).
2024-06-18T10:51:44.918174Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.37-0ubuntu0.24.04.1) starting as process 3066
2024-06-18T10:51:44.919415Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-06-18T10:51:44.919426Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8mb3_bin' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2024-06-18T10:51:44.938263Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2024-06-18T10:51:44.938440Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-06-18T10:51:44.938463Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-06-18T10:51:44.938981Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.37-0ubuntu0.24.04.1) (Ubuntu).

The issue was resolved and CQRLOG started working correctly after running "sudo apt install mariadb-server" (replacing the mysql server with mariadb).

I don't know how the mysql/mariadb package is handled in Debian, but someone should probably send a Merge request to the Debian GitLab repository: https://salsa.debian.org/debian-hamradio-team/cqrlog

[AsciiWolf (asciiwolf)]

This should ideally be fixed in Debian and then in 24.04 / 22.04 as a Stable Release Update.

https://wiki.ubuntu.com/StableReleaseUpdates

[AsciiWolf (asciiwolf)]

So, as Dave Hibberd found out, the problem is that Ubuntu is shipping mysql-* as mysql-* and Debian is shipping mariadb-* as mysql-*.

See his original comment with more details here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073790#10

One possible Debian-side solution could be changing the virtual-mysql-client-core and virtual-mysql-server-core to mariadb-client-core and mariadb-server-core, default-mysql-server to mariadb-server and removing the default-mysql-server-core dependency. That would cause dependency issues on systems that already have mysql-server-8 installed, but since CQRLOG does not seem to work with mysql anymore (only with mariadb), it should not be a big problem, at least in my opinion.

The other possible solution would be to patch this in Ubuntu. However, I am not sure whether the CQRLOG package has any Ubuntu maintainers and also it would probably break auto-sync of the package from Debian.

CQRLOG should also fix their MySQL 8 support if possible. That would probably be the best solution.

It looks like that there sadly are not other possible fixes to this issue.

[Dave Hibberd (hibby)]

Hi all,

It turns out I agreed after some more thinking on the subject, so have committed a fix for this as 2.5.2-5 in Debian: https://tracker.debian.org/news/1538653/accepted-cqrlog-252-5-source-into-unstable/

Code's on salsa if you want to try a build and install - I ran it through my build infrastructure for jammy and noble and it builds successfully, but I haven't tested installing and running as I don't have a VM to hand.

Cheers!

Hibby

[AsciiWolf (asciiwolf)]

Hi Dave,

Thanks a lot! The new build is already synced in Oracular (24.10):

https://launchpad.net/ubuntu/+source/cqrlog/2.5.2-5

I have tested it on a clean amd64 24.04 VM and can confirm that it works fine now! :-)

So, if anyone wants this to also be fixed in Noble (24.04 LTS), it should now be possible to make a SRU:

https://wiki.ubuntu.com/StableReleaseUpdates