More mysql errors on Ubuntu 16.04

6 posts / 0 new
Last post
KG5HBL
More mysql errors on Ubuntu 16.04

Upgraded to Ubuntu 16.04 and downloaded new CQRLOG:
Open the terminal and put there this:

sudo add-apt-repository ppa:ok2cqr/ppa && sudo apt-get update
sudo apt-get install cqrlog

APT will download and install cqrlog with all necessary dependencies.

Run with
$ cqrlog --debug=1

**** 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.18
**************************
MySQL version: 5.5
**************************
**********************************
MySQL version assigned: 5.5
**********************************
Loaded 101655 LoTW users
Loaded 105163 eQSL users
Loaded 44840 SCP calls
*
User home directory: /home/lou/
Program home directory: /home/lou/.config/cqrlog/
Data directory: /home/lou/.config/cqrlog/database/
Memebers directory: /usr/share/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/lou/.config/cqrlog/database/mysql.cnf --datadir=/home/lou/.config/cqrlog/database/ --socket=/home/lou/.config/cqrlog/database/sock --port=64000
170905 10:02:42 [Note] /usr/sbin/mysqld (mysqld 10.0.31-MariaDB-0ubuntu0.16.04.2) starting as process 4249 ...
Trying to connect to database
TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.19).

get error> Error during connection to database: TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (5.7.19).

Last few lines from:mysql.err file

170905 10:02:43 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
170905 10:02:43 [Note] Server socket created on IP: '::'.
170905 10:02:43 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
170905 10:02:43 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
170905 10:02:43 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
170905 10:02:43 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
170905 10:02:43 [Note] Reading of all Master_info entries succeded
170905 10:02:43 [Note] Added new Master_info '' to hash table
170905 10:02:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.31-MariaDB-0ubuntu0.16.04.2' socket: '/home/lou/.config/cqrlog/database/sock' port: 64000 Ubuntu 16.04

ok2cqr
ok2cqr's picture
Re: More mysql errors on Ubuntu 16.04

It seems there are multiple version of MySQL on the system. Please remove the old version and leave only 5.7.

73 Petr

KG5HBL
Re: More mysql errors on Ubuntu 16.04

You were correct, Petr.
Part of the old version was still lingering in there. Was able to delete it and reload new version.
All is well.

Thanks,
73 Lou

G3SQU
G3SQU's picture
Ubuntu 16.04 installation

Just done a reinstall of CQRLOG after complete removal, and also reinstalled MySQL and am getting an error on opening CQRLOG:

TApplication.HandleException TMySQL57Connection : Error executing query: Can't create database 'cqrlog_common'; database exists

I've looked for multiple versions of MySQL and get this:

mysql: /usr/bin/mysql /usr/lib/mysql /etc/mysql /usr/share/mysql /usr/share/man/man1/mysql.1.gz

Can you advise?

Chris G3SQU

KG5HBL
Hi Chris,

Hi Chris,
I would suggest asking Petr. My error came from an old version of CRQLOG. I searched for the older version using Synaptic - then I deleted the old version.
That fixed my problem.
You also might try rebooting - sometimes that fixes things.

73
Lou KG5HBL

G3SQU
G3SQU's picture
Ubuntu 16.04 installation

Thanks Lou

After many trials and tribulations I appear now to have a stable installation. I think part of my problem may have come from using files from an earlier installation - I haven't been using CQRLOG for over a year as I had problems when I upgraded to 14.06 LTS and gave up. Was just trying it out again as I am now running 16.04. The forking of MySQL with Mariadb seems to have created a lot of problems for a lot of people.

I managed to cope with the my_loc field setting for imported QSOs with some judicious use of the SQL Console - I hadn't used the feature before and haven't used SQL for 20 years, but it has sorted out a lot of my other issues as well so I am quite pleased to have returned to the fold. It's just mindboggling how everybody needs to tweak the program to their personal taste - I wouldn't be Petr for all the DX in the world!

73 Chris