I've decided to switch from Ubuntu to CentOS 7, and I successfully installed cqrlog v. 1.9.1 and all its dependencies on the CentOS system. I thought I could just copy the contents of ~/.config/cqrlog from the Ubuntu system to the CentOS system. However, when I do that, the CentOS cqrlog fails to start, complaining that it can't connect to the mysql db. If I launch cqrlog and let it create a fresh config, it works fine, and I can load QSOs, etc.
I suspect this is caused by the fact that CentOS 7 has mariadb instead of mysql. I see that support was added for that in cqrlog 1.9.0, but I wonder oi what I'm trying to do is supported, or is there a better way to do it?
I tried manually exporting/importing my QSOs, but I'm unable to do that because of some problem with the way my data is in my log, and some limitations of cqrlog. Although I have the same QTH profiles defined in both cqrlog instances, and I exported ADIF data with all fields including profile, when I import the ADIF file, no profile is selected for any of the QSOs.
So then I tried to do a separate export for each of 4 profiles, using a filter. However, I see that many of my records have no profile assigned, and I see no way to filter on records with no profile. If I make no selection in the profile field when defining the filter, it selects no records. I created a sql query in the sql console with "where profile = ''". This seems to select the records as desired, but then I can only export a csv file, and not ADIF. I should go through my data anyway and assign a profile to records that are missing it, but it will take me a while. So in the meantime, I wonder if there is a way to do one of the following:
1. Re-use the ~/.config/cqrlog contents from my Ubuntu installation in my CentOS installation
or
2. Export/import ADIF data such that the profile field is respected after te import
or
3. Create an ADIF export file that includes only QSOs with no profile assigned.
Thanks Petr, for your work on cqrlog, the best logging program by far.
Hi,
run cqrlog from console with --debug=1 parameter. I suppose MySQL will have some trouble to read the data but I suppose it won't be hard to solve it.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Thanks, Petr. Here's the output when launching with --debug=1. Let me know if there's anything else I can do to characterize the problem.
$ cqrlog --debug=1
**** DEBUG LEVEL 1 ****
Loading libssl: /usr/lib64/libssl.so.1.0.1e
Loading libcrypto: /usr/lib64/libcrypto.so.1.0.1e
Loading libmysqlclient: /usr/lib64/mysql/libmysqlclient.so.18
**************************
MySQL version: 5.5
**************************
**********************************
MySQL version assigned: 5.500000000000000000E+00
**********************************
Loaded 89360 LoTW users
Loaded 95510 eQSL users
Loaded 46102 SCP calls
*
User home directory: /home/mal/
Program home directory: /home/mal/.config/cqrlog/
Data directory: /home/mal/.config/cqrlog/database/
Memebers directory: /opt/cqrlog-1.9.1/usr/share/cqrlog/members/
ZIP code directory: /opt/cqrlog-1.9.1/usr/share/cqrlog/zipcodes/
Binary dir: /opt/cqrlog-1.9.1/usr/bin/
Share dir: /opt/cqrlog-1.9.1/usr/share/cqrlog/
TConnection to MySQL: 5.5
*
Trying to connect to database
160102 21:21:54 mysqld_safe Logging to '/home/mal/.config/cqrlog/database//mysql.err'.
160102 21:21:54 mysqld_safe Starting mysqld daemon with databases from /home/mal/.config/cqrlog/database/
160102 21:21:54 mysqld_safe mysqld from pid file /home/mal/.config/cqrlog/database//localhost.localdomain.pid ended
Server connect failed.
Trying:1
Trying to connect to database
Server connect failed.
Trying:2
Trying to connect to database
Server connect failed.
Trying:3
Trying to connect to database
Server connect failed.
Trying:4
Trying to connect to database
Server connect failed.
Trying:5
Trying to connect to database
Server connect failed.
Trying:6
Trying to connect to database
Server connect failed.
Trying:7
Trying to connect to database
Server connect failed.
Trying:8
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Closing dDXCC
Closing dData
Closing ini file ...
Mark K4XML Reston, VA USA
I originally copied the config files from an Ubuntu system running cqrlog v. 1.9.0 to cqrlog v. 1.9.1 on CentOS 7. In that case, cqrlog on CentOS was able to start up, but some parts of the system configuration were not copied to the CentOS instance, such as Station info, QTH Profiles, and export columns. Perhaps this gives a hint where the problem is.
Mark K4XML Reston, VA USA
Here's the mysql.err log file. It's complaining about using innodb tables, but I don't know why it doesn't have that probelem when creating a fresh config. I see in that case that innodb storage type is specified in mysql.cnf.
$ cat mysql.err
160102 23:56:45 mysqld_safe Starting mysqld daemon with databases from /home/mal/.config/cqrlog/database/
160102 23:56:45 [Note] /usr/libexec/mysqld (mysqld 5.5.44-MariaDB) starting as process 4492 ...
160102 23:56:45 InnoDB: The InnoDB memory heap is disabled
160102 23:56:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160102 23:56:45 InnoDB: Compressed tables use zlib 1.2.7
160102 23:56:45 InnoDB: Using Linux native AIO
160102 23:56:45 InnoDB: Initializing buffer pool, size = 80.0M
160102 23:56:45 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
InnoDB: Possible causes for this error:
(a) Incorrect log file is used or log file size is changed
(b) In case default size is used this log file is from 10.0
(c) Log file is corrupted or there was not enough disk space
In case (b) you need to set innodb_log_file_size = 48M
160102 23:56:45 [ERROR] Plugin 'InnoDB' init function returned error.
160102 23:56:45 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160102 23:56:45 [Note] Plugin 'FEEDBACK' is disabled.
160102 23:56:45 [ERROR] Unknown/unsupported storage engine: innodb
160102 23:56:45 [ERROR] Aborting
160102 23:56:45 [Note] /usr/libexec/mysqld: Shutdown complete
160102 23:56:45 mysqld_safe mysqld from pid file /home/mal/.config/cqrlog/database//localhost.localdomain.pid ended
Mark K4XML Reston, VA USA
Thank you, this helps a lot!
To solve this problem, open ~/.config/cqrlog/database/mysql.cnf and just after [mysqld] add this:
innodb_log_file_size=5242880
save the changes and try to run cqrlog again. It should work.
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Thanks, Petr. I missed that earlier error message in the log. That's exactly what I needed, except I had to set it to 50331648 not 5242880. The latter is the size it was configured for, and the former is the size it detected.
Anyway it's ported to CentOS 7 now with all the data and settings intact. Thanks for your help.
Mark K4XML Reston, VA USA