CQRLOG dead after upgrade to Xubuntu 26.04

3 posts / 0 new
Last post
NK8O
CQRLOG dead after upgrade to Xubuntu 26.04

I had been running Xubuntu 25.10 and all was well with CQRLog. After the upgrade to 26.04, I'm getting the message: "TMySQL57Connection : Server connect failed."

The mysql.err has old entries from before I upgraded, but no new entries.

The following database components are installed: libmariadb-dev-compat mariadb-client mariadb-server mariadb-common

Any suggestions?

73

Charles

oh1kh
CQRLOG dead after upgrade to Xubuntu 26.04

Hi Charles!

Seem to be same problem that Joe, N0NOW, has. ( https://www.cqrlog.com/node/6159 ).
When we get a solution for that it perhaps helps you too.

I am a Fedora user myself. Perhaps I need to install latest "buntu" to virtual machine to see what there is wrong.

--
Saku
OH1KH

dl8abg
Hallo Saku,

Hallo Saku,

using Debian testing, I also observed the problem of cqrlog not starting anymore after an upgrade on Tuesday (June 2nd) after some weeks having done no upgrade but enjoying a good working cqrlog installation.

A closer look showed, that apparmor denied the access to the mysql.cnf within the cqrlog database directory. The reason was, that the apparmor profile file seems to be have changed from /etc/apparmor.d/usr.sbin.mariadbd to /etc/apparmor.d/mariadbd but there was not exemption file in /etc/apparmor.d/local/ for mariadb containing the configuration for local access to the cqrlog directory.

After setting up a /etc/apparmor.d/local/mariadbd with the content

# Site-specific additions and overrides for usr.sbin.mysqld.
# For more details, please see /etc/apparmor.d/local/README.
@{HOME}/.config/cqrlog/database/ r,
@{HOME}/.config/cqrlog/database/** rwk,
@{HOME}/.config/cqrlog-2.5/database/ r,
@{HOME}/.config/cqrlog-2.5/database/** rwk,

and restarting apparmor with sudo systemctl reload apparmor, everything now works again.

I hope, this information can help anyone, who also stuck in cqrlog not starting anymore after a recent upgrade and have difficulties finding the reason.

If you have contact to the Debian package maintainer for cqrlog, this seems to be a hint for preventing this problem in upcoming upgrades or fresh installations.

Best regards
Frank, DL8ABG