CQRlog error connecting to database. Expecting 5.5 got 5.7

13 posts / 0 new
Last post
PA3GOS
CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi,

I have been almost inactive due to severe qrm but nevertheless I'd like to have CQRlog running for the occasional QSO.

Recently, I upgraded my Mint 17.3 to 18.3 and I can't seem to get CQRlog running.
Something in the line of the title comes up and, basically, that's it.

Here are the last 20 lines of mysql.err:

181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
181221 14:54:45 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
181221 14:54:45 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
181221 14:54:45 [Note] Reading of all Master_info entries succeded
181221 14:54:45 [Note] Added new Master_info '' to hash table
181221 14:54:45 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.36-MariaDB-0ubuntu0.16.04.1' socket: '/home/tjalling/.config/cqrlog/database/sock' port: 64000 Ubuntu 16.04

And here is the console output of DEBUG level 1:

tjalling@tjalling-System-Product-Name ~ $ cqrlog --debug=1

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

SSL libraries:
/lib/x86_64-linux-gnu/libssl.so.1.0.0
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
**************************
MySQL version: 5.5
**************************
**********************************
MySQL version assigned: 5.5
**********************************
Loaded 104157 LoTW users
Loaded 107353 eQSL users
Loaded 43261 SCP calls
*
User home directory: /home/tjalling/
Program home directory: /home/tjalling/.config/cqrlog/
Data directory: /home/tjalling/.config/cqrlog/database/
Memebers directory: /home/tjalling/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
TConnection to MySQL: 5.5
*
56 us states loaded
/usr/sbin/mysqld --defaults-file=/home/tjalling/.config/cqrlog/database/mysql.cnf --datadir=/home/tjalling/.config/cqrlog/database/ --socket=/home/tjalling/.config/cqrlog/database/sock --port=64000
Trying to connect to database
181221 14:04:22 [Note] /usr/sbin/mysqld (mysqld 10.0.36-MariaDB-0ubuntu0.16.04.1) starting as process 5409 ...
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:1
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:2
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:3
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:4
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:5
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:6
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:7
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.24).
Trying:8

I am out of ideas. Maybe uninstall CQRlog and reïnstall but I am afraid of losing my log. Unfortunately, my two back-ups were erased by human error.

oh1kh
CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi!

It seems to be endless story with Ubuntu database problems. As fedora user I have never had any database problems with cqrlog (yet ! :-O )

Debug reports 5.5 found but how ever it ends up to 5.7.
This seems similar as problems here before. Here is Petr's advice from an earlier thread:

It seems that after the upgrade there are both version of libmysql-client libraries 5.5 and 5.7. Use synaptic or uninstall libraries using apt remove libmysqlclient-5.5 or something like that.

About logs:
Set your file manager to show hidden files and folders. Then you can find folder .config under your home directory. (home/yourusername/.config).
There is folder cqrlog. If you copy that with all it's files and subfolders you have complete backup of your cqrlog with all logs.
(Unless you are using an external mysql server for logs, that I understand you are not. I.E "Save log data to local machine" is selected.)

--
Saku
OH1KH

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi Saku,

Thank you so much for at least backing up my files once again.

I will see to fix the problem with the tips you gave one of these days.
To be honest, I never had one of these before. And I've been using Linux Mint for quite a bunch of years now.
I did find some similar problems but, so far, none was the same as mine. At least at first glance.
Of course I will report back. Might take a couple of days though.

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi,

Well, I've been busy with this for many hours. Tried to delete broken packages to no avail.
MySQL, MariaDB, and so on.
Could not even get them reinstalled again.

Finally I am at a point where CQRlog is reinstalled but now there is a connection failure to MySQL.

I am desperate. Tried everything I could find and more. I will attach the .err log as a .txt file.
Hopefully someone can shed a bright light on this.

Thanks in advance.
Tjalling.

File: 

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Here is the Debug (level 1) output from the terminal.

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

SSL libraries:
/lib/x86_64-linux-gnu/libssl.so.1.0.0
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20.3.11
**************************
MySQL version: 5.7
**************************
**********************************
MySQL version assigned: 5.7
**********************************
Loaded 104157 LoTW users
Loaded 107353 eQSL users
Loaded 43261 SCP calls
*
User home directory: /home/tjalling/
Program home directory: /home/tjalling/.config/cqrlog/
Data directory: /home/tjalling/.config/cqrlog/database/
Memebers directory: /home/tjalling/.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/tjalling/.config/cqrlog/database/mysql.cnf --datadir=/home/tjalling/.config/cqrlog/database/ --socket=/home/tjalling/.config/cqrlog/database/sock --port=64000
Trying to connect to database
mysqld: [ERROR] Could not open required defaults file: /home/tjalling/.config/cqrlog/database/mysql.cnf
mysqld: [ERROR] Fatal error in defaults handling. Program aborted!
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
Closing dDXCC
Invalid file handle
Closing dData
Closing ini file ...

At the end, where the "closing" thins are, is when I closed CQRlog entirely.

oh1kh
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi!
These mysql issues are always very complex.

Now, as you have backups, have you tried to start from scratch ?
Rename folder ~/.cqnfig/cqrlog to bak .

mv ~/.cqnfig/cqrlog ~/.cqnfig/cqrlog-bak

Then start cqrlog and see if it works when it starts with creating completely new database.
If it works, then it is just a question how to get old logs to adif and then imported to this new one.

As another test you could try to make external log database to your existing mysql server that is running at your pc. Could it work?
If you can not do this, then there is something wrong with mysql install.
Follow this message for testing it: https://www.cqrlog.com/comment/6776#comment-6776

--
Saku
OH1KH

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi Saku,

Yes, I have been busy all weekend far as long as I could.
I removed everything, including mysql, mariadb and CQRlog.
Several times too. Using Synaptic, apt, apt-get, including options like purge, autoremove -f and so on.
My system keeps telling me I hold back two broken packages but I got to a point where I could reinstall CQRlog clean.
Of course I keep a copy of the original ./config/cqrlog stashed on another HDD at all times.

As you can see, CQRlog finds mysql 5.7 now but does not connect to several reasons.
Mysql won't even start properly.

This is what I get when using sudo mysql:

tjalling@tjalling-System-Product-Name ~ $ sudo mysql
[sudo] wachtwoord voor tjalling:
ERROR 1524 (HY000): Plugin 'unix_socket' is not loaded
tjalling@tjalling-System-Product-Name ~ $

I have been googling and trying the best I could but to no avail.

For some reason it seems no one seems to really know what might be going on.

I even tried aptitude. A nice little GUI in the terminal, but I can't quite figure that one out either.

Anyway, even trying to start from scratch seems to have magic involved.....

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Oke, a huge step further now.

I removed every single file that had anything to do with both mysql and mariadb.
Then I tried to reinstall but, again, to no avail. Used apt-get -f install, then uninstalled mysql-client, mysql-common and rebooted.
Finally I got everything installed without errors. I fired up cqrlog and to my surprise, it came up.
Unfortunately only once.. Second time not so much. Got the same "connection failed" or something like it, again.
Brought up the terminal and gave cqrlog --debug=1

Here is the lengthy result:

tjalling@tjalling-System-Product-Name ~ $ cqrlog --debug=1

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

SSL libraries:
/lib/x86_64-linux-gnu/libssl.so.1.0.0
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20.3.11
**************************
MySQL version: 5.7
**************************
**********************************
MySQL version assigned: 5.7
**********************************
Loaded 124164 LoTW users
Loaded 119318 eQSL users
Loaded 38979 SCP calls
*
User home directory: /home/tjalling/
Program home directory: /home/tjalling/.config/cqrlog/
Data directory: /home/tjalling/.config/cqrlog/database/
Memebers directory: /home/tjalling/.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/tjalling/.config/cqrlog/database/mysql.cnf --datadir=/home/tjalling/.config/cqrlog/database/ --socket=/home/tjalling/.config/cqrlog/database/sock --port=64000
Trying to connect to database
mysqld: [Warning] World-writable config file '/home/tjalling/.config/cqrlog/database/mysql.cnf' is ignored.
2018-12-25T00:11:22.477282Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-12-25T00:11:22.478315Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.24-0ubuntu0.16.04.1) starting as process 18989 ...
2018-12-25T00:11:22.481510Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-12-25T00:11:22.481527Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-12-25T00:11:22.481532Z 0 [Note] InnoDB: Uses event mutexes
2018-12-25T00:11:22.481536Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-12-25T00:11:22.481540Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-12-25T00:11:22.481547Z 0 [Note] InnoDB: Using Linux native AIO
2018-12-25T00:11:22.481740Z 0 [Note] InnoDB: Number of pools: 1
2018-12-25T00:11:22.481819Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-12-25T00:11:22.483060Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-12-25T00:11:22.491190Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-12-25T00:11:22.492550Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-12-25T00:11:22.503965Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-12-25T00:11:22.517561Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-12-25T00:11:22.517629Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-12-25T00:11:22.578685Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-12-25T00:11:22.579554Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-12-25T00:11:22.579565Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-12-25T00:11:22.581768Z 0 [Note] InnoDB: 5.7.24 started; log sequence number 6659545
2018-12-25T00:11:22.581899Z 0 [Note] InnoDB: Loading buffer pool(s) from /home/tjalling/.config/cqrlog/database/ib_buffer_pool
2018-12-25T00:11:22.582045Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysqld: Table 'mysql.plugin' doesn't exist
2018-12-25T00:11:22.582139Z 0 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2018-12-25T00:11:22.582485Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2018-12-25T00:11:22.582547Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2018-12-25T00:11:22.582556Z 0 [Note] Server hostname (bind-address): '*'; port: 64000
2018-12-25T00:11:22.582588Z 0 [Note] IPv6 is available.
2018-12-25T00:11:22.582595Z 0 [Note] - '::' resolves to '::';
2018-12-25T00:11:22.582611Z 0 [Note] Server socket created on IP: '::'.
2018-12-25T00:11:22.583222Z 0 [Note] InnoDB: Buffer pool(s) load completed at 181225 1:11:22
2018-12-25T00:11:22.586475Z 0 [Warning] Insecure configuration for --pid-file: Location '/home/tjalling/.config/cqrlog/database' in the path is accessible to all OS users. Consider choosing a different directory.
2018-12-25T00:11:22.586566Z 0 [Warning] Failed to open optimizer cost constant tables

2018-12-25T00:11:22.586672Z 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
2018-12-25T00:11:22.586687Z 0 [ERROR] Fatal error: Failed to initialize ACL/grant/time zones structures or failed to remove temporary table files.
2018-12-25T00:11:22.586733Z 0 [ERROR] Aborting

2018-12-25T00:11:22.586761Z 0 [Note] Binlog end
2018-12-25T00:11:22.586798Z 0 [Note] Shutting down plugin 'ngram'
2018-12-25T00:11:22.586804Z 0 [Note] Shutting down plugin 'partition'
2018-12-25T00:11:22.586807Z 0 [Note] Shutting down plugin 'BLACKHOLE'
2018-12-25T00:11:22.586811Z 0 [Note] Shutting down plugin 'ARCHIVE'
2018-12-25T00:11:22.586815Z 0 [Note] Shutting down plugin 'MyISAM'
2018-12-25T00:11:22.586824Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
2018-12-25T00:11:22.586828Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-12-25T00:11:22.586832Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-12-25T00:11:22.586835Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-12-25T00:11:22.586839Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-12-25T00:11:22.586842Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-12-25T00:11:22.586846Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-12-25T00:11:22.586849Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-12-25T00:11:22.586852Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-12-25T00:11:22.586856Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-12-25T00:11:22.586860Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-12-25T00:11:22.586863Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-12-25T00:11:22.586866Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-12-25T00:11:22.586870Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-12-25T00:11:22.586873Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-12-25T00:11:22.586877Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-12-25T00:11:22.586880Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
2018-12-25T00:11:22.586884Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
2018-12-25T00:11:22.586888Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-12-25T00:11:22.586892Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-12-25T00:11:22.586896Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-12-25T00:11:22.586900Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-12-25T00:11:22.586904Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-12-25T00:11:22.586908Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-12-25T00:11:22.586911Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-12-25T00:11:22.586915Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-12-25T00:11:22.586918Z 0 [Note] Shutting down plugin 'INNODB_CMP'
2018-12-25T00:11:22.586922Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-12-25T00:11:22.586925Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-12-25T00:11:22.586928Z 0 [Note] Shutting down plugin 'INNODB_TRX'
2018-12-25T00:11:22.586931Z 0 [Note] Shutting down plugin 'InnoDB'
2018-12-25T00:11:22.586975Z 0 [Note] InnoDB: FTS optimize thread exiting.
2018-12-25T00:11:22.587094Z 0 [Note] InnoDB: Starting shutdown...
2018-12-25T00:11:22.687375Z 0 [Note] InnoDB: Dumping buffer pool(s) to /home/tjalling/.config/cqrlog/database/ib_buffer_pool
2018-12-25T00:11:22.687592Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 181225 1:11:22
TMySQL57Connection : Server connect failed.
Trying:1
2018-12-25T00:11:24.196619Z 0 [Note] InnoDB: Shutdown completed; log sequence number 6659564
2018-12-25T00:11:24.198312Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-12-25T00:11:24.198325Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-12-25T00:11:24.198373Z 0 [Note] Shutting down plugin 'CSV'
2018-12-25T00:11:24.198377Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
2018-12-25T00:11:24.198380Z 0 [Note] Shutting down plugin 'MEMORY'
2018-12-25T00:11:24.198383Z 0 [Note] Shutting down plugin 'sha256_password'
2018-12-25T00:11:24.198386Z 0 [Note] Shutting down plugin 'mysql_native_password'
2018-12-25T00:11:24.198507Z 0 [Note] Shutting down plugin 'binlog'
2018-12-25T00:11:24.198618Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

Trying to connect to database
TMySQL57Connection : Server connect failed.

Hope to make more progress tomorrow or so.

oh1kh
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

HI!
Does your mysql now start ok from console, or do you still get unix socket error?
I would focus first to console mysql operations.

When you can log in there you can start play with cqrlog.
Before that it is quite useless to try to make progress with cqrlog.

Can you use synaptic GUI with Mint? It is quite good and I have managed to use it rather easily, even when being Fedora user for years.

Remember google is your friend. Specially with "common" mysql problems.
Usually just error txt is enough for search words.

--
Saku
OH1KH

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi,

Thank you for replying.
Yes, mysql is up and running. I used Synaptic GUI as well as many commandline commands.
Even manually removed leftovers. Of course, only the ones I was sure I could safely remove.

That's when I got to the point where I could finally install mysql without errors. And all other dependencies.
I even had to enter a new password for mysql. Used "cqrlog" of course. That is what CQRlog uses to log into mysql.
And google did help me a lot with the errors too. I learned quite a bit as I went on too.

Also, I don't focus on CQRlog itself as long as things are not 100% configured properly.
I will chime in again when there's more. Thanks for putting me on the right track.

Tjalling PA3GOS.

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi,

CQRlog is up and running again. After a lot of time figuring things out,

The only thing missing is my log. I tried to copy the old database folder back while I had renamed the working, empty, one.
But then I get a connection error again.
Then I got things back to "the new original" and CQRlog starts perfectly but no QSO's of course.
Last thing I tried was to only rename cqrlog_main.ibd and copy my old one back in.
To no avail... Another connection error. Changed it back so CQRlog will start.

Now I have to find a way to get my log back into place.
This is what you wrote:

"Then start cqrlog and see if it works when it starts with creating completely new database.
If it works, then it is just a question how to get old logs to adif and then imported to this new one."

So this is what should be done..... Now the how. I keep trying.

Tjalling PA3GOS

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi,

I have an idea. My entire log is uploaded to hamqth.com
Now, is there a way to download my log from there? I have been searching but did not see such an option.

Would be great to restore my log in CQRlog.

Thanks in advance.

Tjalling PA3GOS

PA3GOS
RE: CQRlog error connecting to database. Expecting 5.5 got 5.7

Hi again,

Everything is solved now. I was able to download an adif file from Clublog.
Fortunately CQRlog has an option to add all extra info, like name etc. from Hamqth.com

Thanks for helping.

Tjalling PA3GOS