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
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
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
HI Frank!
Just wrote a message:
https://www.cqrlog.com/comment/13482#comment-13482
But you resolved the main problem!
Thanks!
I was also editing /etc/apparmor.d/local/mariadbd file but without further knowledge of Debian based systems I did not succeed.
Well, I was on the right track anyway...
--
Saku
OH1KH
Tested and works!
it seems that I only missed on line with my edit
@{HOME}/.config/cqrlog/database/** rwk,
I think those cqrlog-2.5/database lines are not needed if only base install has been made.
--
Saku
OH1KH
I still get the error reported by the OP.
Last portion of mysql.err:
2026-10-14 11:31:01 0 [Note] Starting MariaDB 11.8.6-MariaDB-5ubuntu0.1 from Ubuntu source revision 9bfea48ce1214cc4470f6f6f8a4e30352cef84e7 server_uid GAc7My1HFtqBuYNyiMOoxLtuYOk= as process 141370
2026-10-14 11:31:01 0 [ERROR] mysqld: File '/home/bog/.config/cqrlog/database/' not found (Errcode: 13 "Permission denied")
2026-10-14 11:31:01 0 [ERROR] mysqld: Aria engine: log initialization failed
2026-10-14 11:31:01 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2026-10-14 11:31:01 0 [Warning] --innodb-file-per-table is deprecated and will be removed in a future release
2026-10-14 11:31:01 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2026-10-14 11:31:01 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2026-10-14 11:31:01 0 [Note] InnoDB: Number of transaction pools: 1
2026-10-14 11:31:01 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2026-10-14 11:31:01 0 [Note] InnoDB: Using io_uring
2026-10-14 11:31:01 0 [Note] InnoDB: innodb_buffer_pool_size_max=80m, innodb_buffer_pool_size=80m
2026-10-14 11:31:01 0 [Note] InnoDB: Initialized memory pressure event listener
2026-10-14 11:31:01 0 [Note] InnoDB: Completed initialization of buffer pool
2026-10-14 11:31:01 0 [ERROR] InnoDB: File ./ib_logfile0 was not found
2026-10-14 11:31:01 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2026-10-14 11:31:01 0 [Note] InnoDB: Starting shutdown...
2026-10-14 11:31:01 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2026-10-14 11:31:01 0 [Note] Plugin 'FEEDBACK' is disabled.
2026-10-14 11:31:01 0 [Note] Plugin 'wsrep-provider' is disabled.
2026-10-14 11:31:01 0 [ERROR] Failed to initialize plugins.
2026-10-14 11:31:01 0 [ERROR] Aborting
Warning: Internal memory accounting error of 208 bytes
73,
Bruce
N7CEE
Hallo Bruce,
from the messages, the access to your database directory is forbidden (see
2026-10-14 11:31:01 0 [ERROR] mysqld: File '/home/bog/.config/cqrlog/database/' not found (Errcode: 13 "Permission denied")).The apparmor-messages appeared in my case not in mysql.err but in the kernel output which can be obtained by "dmesg" (or "sudo dmesg"). There was an entry saying something like "apparmor blocked the start of mysql" directly after I tried to start cqrlog. From there I found (with the help of chatgpt) the way to add the apparmor-rules I proposed above.
Are you sure that apparmor is the reason for the forbidden access to your DB directory?
73 de Frank, DL8ABG
Hi Bruce !
I have just played with Ubuntu 26.04
https://www.cqrlog.com/comment/13652#comment-13652
https://www.cqrlog.com/comment/13653#comment-13653
I assume Kubuntu is mostly same.
Today I took closer look to /etc/apparmor.d/mariadbd file because I did not manage to start Cqrlog so that logs would be in ~/.confgi/cqrlog folder.
Using Mariadb running at localhost:3306 or external SQL server worked ok.
/etc/apparmor.d/mariadbd file looked out different that I expect. I had to make changes in two places using command console:
sudo nano /etc/apparmor.d/mariadbd
After saved the file I made:
That said "files are changed" and suggested to run:
After that I was able to start Cqrlog and selecet the 1st option that makes logs to ~/.config/cqrlog folder.
How ever as said in earlier messages:
GTK2 version didi not work at all while QT5 and QT6 versions started but stacked always all windows in the middle of the screen.
Using LXDE or LXQT window managers (Ubuntu defaults to GNOME) all Cqrlog windows opened to places I had set them in previous run.
Does this give any help?
--
Saku
OH1KH