CQRLOG failure due to database connection

10 posts / 0 new
Last post
KI4IO
CQRLOG failure due to database connection

Running Linux Mint 22.3
trying to install (I have my old logs)
I've been following this thread:
https://www.cqrlog.com/node/6159
and I get to #4

mariadb - access denied

Do I have to try and access using root?

Jerry
KI4IO

oh1kh
CQRLOG failure due to database connection

HI Jerry!

mariadb - access denied means you do not have database user access ok.

At "Database connect" window if you use "Save log data to local machine" you do not need to worry about database user or connection settings.

But if you want to use external MariaDB server that can be in same PC running at port 3306 or exist elsewhere in local network or internet you need to have database username with password and privileges to use that database server.
Database username and password are separate than you Linux username and password.

You should not use root account for anything else than creating a database user before running Cqrlog in case you want to use external SQL server.

Have you checked this message ? https://www.cqrlog.com/comment/11126#comment-11126

--
Saku
OH1KH

KI4IO
CQR log failure

I do use "save log data to a local machine".

Prior to getting that window, I get:
MySQL server connect failed
and
MySQL could not be started, please check if the MySQL server is installed properly

also
I do not want a fresh start - I'd like to have CQRLOG running with all my old logs.

Jerry

oh1kh
CQR log failure

Ok Jerry.
I assume you have then upgraded your Mint.

First you could try to find files called ib_logfileX where X can be any number. They exist in ~/.config/cqrlog/database

They are safe to remove and may help in some cases.
How ever make backup first from folder ~/.config/cqrlog

If that does not help you could try to download script from my github
https://github.com/OH1KH/CqrlogImproved/blob/devel/tools/new-cqrlog-appa...
Run that with sudo and it should add a new line to etc/apparmor file that is needed with new (u)buntu variants to allow MariaDB run in user's folder.
See: https://www.cqrlog.com/node/6161

If that doesn't help and you have fresh backup from ~/.config/cqrlog you could delete the folder from computer and try fresh start of cqrlog.
If you can create first empty log by that it confirms that your MariaDB installation works and the problem is in the old folder data that may be written with pevious version of MariaDB.

On the other hand if you can not create first empty log it shows that you have problem with MariaDB installation and need to fix it and when that is working restore your old ~/.config/cqrlog and try again.

--
Saku
OH1KH

KI4IO
ib_logfile

I found the file ib_logfileX but it's not clear what you want me to do with it. Remove it? Why?

Jerry

oh1kh
ib_logfile

HI Jerry!

Yes, Ib_logfiles should be safe to remove. How ever, good backups are always priority when making changes.
Try to remove the file, or files,if there are more than one.

After that, if it does not help, focus to next chapter of my previous message; the apparmor fixing.

--
Saku
OH1KH

KI4IO
script

that github script....is that it on lines 7, 8, and 9?

Thanks
Jerry
KI4IO

oh1kh
script

 

 

 

Once downloaded set execution bit with console command
chmod a+x new-apparmor-fix.txt

and execte

sudo ./new-apparmor-fix.txt

 

--
Saku
OH1KH

KI4IO
err file

Before I launch that script - here's the last 20 lines from the err file

File: 

oh1kh
err file

Ok!
Before launch try fist clean start.

Backup your ~/.config/cqrlog folder to usb stick or somewhere safe place.
Once done and checked that cqrlog folder exist in your backup device and have same subfolders than your hard disk, do delete the ~/.config/cqrlog from hard disk.
Then do clean start and look if you can get first empty log created and that it is usable.

If that happens then you have no need to run the script and the problem exist in your .config/cqrlog folder that you did backup and move away.

Easiest way to do all this is use file manager. Just modify it's settings so that it shows hidden files and folders. Then you can see ~/.config/cqrlog folder.

If that is successful you can again remove ~/.config/cqrlog (now the one that have clean start log without qsos) and restore your backup from usb stick or where ever it exist.
But then we are back in start point and next thing is how we can make the old log start up again. But anyhow one step forward as we know Cqrlog will run in your system, at least when started from scratch.

--
Saku
OH1KH