Issue after updating mariadb in Ubuntu 20.04

3 posts / 0 new
Last post
EA4HEA
Issue after updating mariadb in Ubuntu 20.04

Hi

I am using CQRLOG (001) under Ubuntu 20.04 successfully since quite long but today I updated Ubuntu with the usual sudo apt-get update ..... and I realised that both mariadb server and client had new versions.
Since the update, CQRlog does not work. Afater starting it all screens appears but is blocked, no interaction with any menu can be made.

Pease read below the output of the debug mode, a server connection failed error appears. The output is cut becasuse it never end, it is a continuos read of VFO from the radio although the software does not respond. Please help!!!

Best regards

OS:
Linux version 5.8.0-53-generic (buildd@lcy01-amd64-012) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021
SSL libraries:
libssl.so
libcrypto.so
Loaded 157153 LoTW users
Loaded 142322 eQSL users
Loaded 35508 SCP calls
/home/jorge/.config/cqrlog/database/jorge-IdeaPad-3-15IIL05.pid
p.Executable: kill Parameters: 4238

kill: (4238): No existe el proceso
*
User home directory: /home/jorge/
Program home directory: /home/jorge/.config/cqrlog/
Data directory: /home/jorge/.config/cqrlog/database/
Memebers directory: /home/jorge/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
*
56 us states loaded
Grid map created
/usr/bin/mysqld
MySQLProcess.Executable: /usr/sbin/mysqld Parameters: --defaults-file=/home/jorge/.config/cqrlog/database/mysql.cnf
--datadir=/home/jorge/.config/cqrlog/database/
--socket=/home/jorge/.config/cqrlog/database/sock
--port=64000

Trying to connect to database
2021-05-14 21:08:58 0 [Note] /usr/sbin/mysqld (mysqld 10.3.29-MariaDB-0ubuntu0.20.04.1) starting as process 2858 ...
TMySQL57Connection : Server connect failed.
Trying:1
select * from tables where table_schema = 'cqrlog_common'

SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr

use cqrlog001

use cqrlog001

use cqrlog001
(...)

EA4HEA
Issue after updating mariadb in Ubuntu 20.04

After some investigation I tried to check mariadb and I got the following output:

sudo systemctl status mariadb
‚óŹ mariadb.service - MariaDB 10.3.29 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-05-15 08:46:14 CEST; 28s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 7070 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 7071 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 7073 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery>
Process: 7120 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Main PID: 7120 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"

may 15 08:46:13 jorge-IdeaPad-3-15IIL05 systemd[1]: Starting MariaDB 10.3.29 database server...
may 15 08:46:13 jorge-IdeaPad-3-15IIL05 mysqld[7120]: 2021-05-15 8:46:13 0 [Note] /usr/sbin/mysqld (mysqld 10.3.29-MariaDB-0ubuntu0.2>
may 15 08:46:14 jorge-IdeaPad-3-15IIL05 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
may 15 08:46:14 jorge-IdeaPad-3-15IIL05 systemd[1]: mariadb.service: Failed with result 'exit-code'.
may 15 08:46:14 jorge-IdeaPad-3-15IIL05 systemd[1]: Failed to start MariaDB 10.3.29 database server.

oh1kh
Issue after updating mariadb in Ubuntu 20.04

Hi!
Your first message dump looks ok until continued "use cqrlog001". It is normal that you get one or several "server connect failed" at the start of cqrlog. Cqrlog will try up to 10 times to connect before fail and it depends your PC speed how fast it is when starting new mysql server thread that cqrlog needs for itself.

Your mariadb mysql server service is not actually needed by cqrlog. When you use "save log data to local machine" cqrlog starts a new mysql server for it's own use and does not use system wide mariadb service.

How ever if the system wide mysql mariadb service fails to start it maybe tells that something can be wrong with installation or update.
It is quite difficult to say what is wrong with that amount of information.

Start study by copying your cqrlog folder with all files and folders to backup using console or your favorite file browser. Your file browser must have "show hidden files and folders" enabled to find cqrlog folder.
you can do backup copy with console command:
cp -a ~/.config/cqrlog ~/.config/cqrlog_backup

It is also recommended to copy ~/.config/cqrlog_backup to external drive or USB stick, just for sure.

When backup is completed you can try something.

Have you tried "utils/repair database" at "database connection" window that starts first when starting cqrlog?

If that does not help then you could rename original ~/.config/cqrlog to something like ~/.config/cqrlogX
mv ~/.config/cqrlog ~/.config/cqrlogX

When you start cqrlog after renamed the folder it thinks you have never used cqrlog before and should ask to create a new log (clean first install).
If that works and you can add qsos to new log then the problem is not in Mariadb.

Then it must be in your cqrlog data folder. Perhaps you did apt upgrade while using cqrlog? It should not fail, but it might do so.
You can now close cqrlog and remove the test folder and rename original folder back.

rm ~/.config/cqrlog
mv ~/.config/cqrlogX ~/.config/cqrlog

Then how to fix corrupted cqrlog data folder is a bigger question. But we have to start by sorting first out is the MariaDB working ok.

--
Saku
OH1KH