"TMySQL57Connection : Server connect failed." on startup with CQRLOG 2.3.0 on Ubuntu 18.10

7 posts / 0 new
Last post
WZ4Q
"TMySQL57Connection : Server connect failed." on startup with CQRLOG 2.3.0 on Ubuntu 18.10

I've installed the latest version using the "complete application directory" package on my Ubuntu 18.10 system. However, when I run cqrlog, I see an error related to mysql. Please see below for debug output. Any direction that anyone can provide in troubleshooting the issue is appreciated.

CQRLOG Debug Output

Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 9 ****

SSL libraries:
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20.3.13
**************************
MySQL version: 5.7
**************************
**********************************
MySQL version assigned: 5.7
**********************************
Loaded 118377 LoTW users
Loaded 115544 eQSL users
Loaded 40133 SCP calls
*
User home directory: /home/pburton/
Program home directory: /home/pburton/.config/cqrlog/
Data directory: /home/pburton/.config/cqrlog/database/
Memebers directory: /home/pburton/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
TConnection to MySQL: 5.7
*
56 us states loaded
/usr/sbin/mysqld --defaults-file=/home/pburton/.config/cqrlog/database/mysql.cnf --datadir=/home/pburton/.config/cqrlog/database/ --socket=/home/pburton/.config/cqrlog/database/sock --port=64000
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:1
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:2
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:3
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:4
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:5
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:6
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:7
Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:8
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
End dmDXCC
Complete end dmDXCC
Closing dDXCC
Closing dData

DL7OAP
Hi,

Hi,

my guess: ubuntu apparmor denies the acces to mysqld

please try this installation routine:
https://www.cqrlog.com/comment/7452#comment-7452

or have a look into your syslog direct after the mysql error. what is mentioned there (i think it will be apparmor warnings):
tail -100 /var/log/syslog

you can try a small correction like this:
sudo sh -c "echo '@{HOME}/.config/cqrlog/database/ r,' >> /etc/apparmor.d/local/usr.sbin.mysqld"
sudo sh -c "echo '@{HOME}/.config/cqrlog/database/** rwk,' >> /etc/apparmor.d/local/usr.sbin.mysqld"
sudo service apparmor restart

here cqrlog works with 18.04, 18.10, 19.04 and daily build of 19.10. so there is hope it will run ;-)

55 & 73 de DL7OAP, Andreas

DL2KI
Hallo Andres,

Hallo Andres,

nichts für ungut, aber mit Software für Anwender hat das alles nichts mehr zu tun. CQRLOG hat sich zur Software für Systemadministratoren und Datenbankexperten entwickelt. Wir sind aber alle Funkamateure, die nichts weiter wollen als ihrem Hobby nachgehen.

Ich nutze CQRLOG noch und kann mit Deiner Beschreibung ja noch halbwegs was anfangen, aber viele schreckt das nur noch ab. Alles nur noch "herumdoktern" an Symptomen.

Sehr schade.

73, Wolfgang
DL2KI

oh1kh
Linux and free software

Hamradio operators should be (and are) above average people technical level. You must pass an examination to get licence. If you can understand radio technology you have also better changes to understand a bit of computers and programs, too.

Selecting Linux for operating system also indicates that user is willing to spent a bit more time and skills to get things going. Otherwise selection would be Windows and commercial programs that both have organized support help desks.

Most common problem for open software is the lack of proper installation instructions and user help documents. Hobby programmers like programming, not manual writing.

In case they do proper instructions, users do not read them. That has been proved so many times.

And if, in very rare cases, user reads instructions he will try to transform or skip some parts to reach the final faster.

If all these cases are passed we still have problem with so many different distributions of Linux and that users will try to use installation instructions made for one version to their own linux that is not just the same version that instructions are for.

There should be a statement:
"By selecting Linux as operating system, and free of charge open software for programs you accept that you may need to work a bit harder to get everything work"

--
Saku
OH1KH

DL2KI
Hi Saku,

Hi Saku,

wrong answer!

73, Wolfgang
DL2KI

yo3hjv
Another failed installation

Hi,
I installed and used CQRLog without problems on a Raspbery4 and use it with success.
Moving my radio stuff on a Thinkpad with Linuxmint Vanessa I first installed CQRlog and opted to use the database from the first installation, on the Raspberry (via IP).
And it worked fine... untill I wanted to have the database locally.
Did something without results then uninstalled from Thinkpad, deleted
~/.config/cqrlog
/usr/share/cqrlog

I saw another user installed MySQL, tried that too (thought CQRLog use embedded SQL) .
Still not working..

I have no ideea. I am not an advanced Linux user but trying to learn.

This is the error message from installer; please enlight me with some hints. Thank you!

2022-11-08T16:53:12.014315Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.31-0ubuntu0.22.04.1) starting as process 3514
2022-11-08T16:53:12.027886Z 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.
2022-11-08T16:53:12.027936Z 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.
2022-11-08T16:53:12.088568Z 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: d49fcaba-5f85-11ed-9d52-6c8814feda38.
2022-11-08T16:53:12.164809Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2022-11-08T16:53:12.164980Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2022-11-08T16:53:12.165007Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-11-08T16:53:12.165695Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.31-0ubuntu0.22.04.1) (Ubuntu).
2022-11-08T16:55:49.093688Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.31-0ubuntu0.22.04.1) starting as process 4110
2022-11-08T16:55:49.095461Z 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.
2022-11-08T16:55:49.095477Z 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.
2022-11-08T16:55:49.102518Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2022-11-08T16:55:49.102771Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2022-11-08T16:55:49.102796Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-11-08T16:55:49.103629Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.31-0ubuntu0.22.04.1) (Ubuntu).
2022-11-08T16:59:34.856262Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.31-0ubuntu0.22.04.1) starting as process 4539
2022-11-08T16:59:34.858546Z 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.
2022-11-08T16:59:34.858566Z 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.
2022-11-08T16:59:34.867101Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2022-11-08T16:59:34.872505Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2022-11-08T16:59:34.872545Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-11-08T16:59:34.873208Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.31-0ubuntu0.22.04.1) (Ubuntu).
2022-11-10T09:51:44.422025Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.31-0ubuntu0.22.04.1) starting as process 56985
2022-11-10T09:51:44.581460Z 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.
2022-11-10T09:51:44.581488Z 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.
2022-11-10T09:51:44.843603Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2022-11-10T09:51:44.843989Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2022-11-10T09:51:44.844016Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-11-10T09:51:44.863147Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.31-0ubuntu0.22.04.1) (Ubuntu).

oh1kh
Another failed installation

HI !
The reason appears in your message in the last line. "complete (mysqld 8.0.31-0ubuntu0.22.04.1) (Ubuntu)"

It is sad to see how many times the same problem appears again and again just because of Ubuntu packet maintainers do not fix it.

See this message: https://www.cqrlog.com/comment/10877#comment-10877

--
Saku
OH1KH