I can't get CQR log to start. I get the "Database problem" dialog box. I am running Linux Mint 19.3. CQR log used to run fine, but I haven't used it in a while. When it failed to start, I attempted a new install and did not get any errors during the install process. However, it fails on startup. Can someone help me out? Here are the last few lines from the log file:
InnoDB: No valid checkpoint found.
InnoDB: A downgrade from MariaDB 10.2.2 or later is not supported.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
2022-07-05 10:07:54 140115315571840 [ERROR] Plugin 'InnoDB' init function returned error.
2022-07-05 10:07:54 140115315571840 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-07-05 10:07:54 140115315571840 [Note] Plugin 'FEEDBACK' is disabled.
2022-07-05 10:07:54 140115315571840 [ERROR] Unknown/unsupported storage engine: innodb
2022-07-05 10:07:54 140115315571840 [ERROR] Aborting
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: The InnoDB memory heap is disabled
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Using Linux native AIO
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Using SSE crc32 instructions
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Completed initialization of buffer pool
2022-07-05 10:19:57 139746053241984 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: No valid checkpoint found.
InnoDB: A downgrade from MariaDB 10.2.2 or later is not supported.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
2022-07-05 10:19:57 139746053241984 [ERROR] Plugin 'InnoDB' init function returned error.
2022-07-05 10:19:57 139746053241984 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-07-05 10:19:57 139746053241984 [Note] Plugin 'FEEDBACK' is disabled.
2022-07-05 10:19:57 139746053241984 [ERROR] Unknown/unsupported storage engine: innodb
2022-07-05 10:19:57 139746053241984 [ERROR] Aborting
Hi!
It looks like your database engine has changed. MariaDB is required and it looks like you have had that before "A downgrade from MariaDB 10.2.2 or later is not supported."
Check database engine version with command line console.
You should see "MariaDB" there somewhere, not "Mysql".
In case it shows Mysql you should install MariaDB database engine that uninstalls Mysql.
--
Saku
OH1KH
I ran the version command, and this is what I get.
mysql --version
mysql Ver 15.1 Distrib 10.1.48-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
When I run sudo systemctl status mariadb, I get:
● mariadb.service - MariaDB 10.1.48 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset:
Active: active (running) since Tue 2022-07-05 10:05:59 MST; 24h ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Main PID: 7442 (mysqld)
Status: "Taking your SQL requests now..."
Tasks: 27 (limit: 4915)
CGroup: /system.slice/mariadb.service
└─7442 /usr/sbin/mysqld
Jul 05 10:05:58 fred systemd[1]: Starting MariaDB 10.1.48 database server...
Jul 05 10:05:59 fred mysqld[7442]: 2022-07-05 10:05:59 140134039297152 [Note] /u
Jul 05 10:05:59 fred systemd[1]: Started MariaDB 10.1.48 database server.
It SEEMS that MariaDB is running okay. But CQRlog fails out whenever I try to start it. Here are the last lines of the mysql.err log. I have no idea what to do now. Can anyone help?
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: The InnoDB memory heap is disabled
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Using Linux native AIO
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Using SSE crc32 instructions
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Completed initialization of buffer pool
2022-07-06 10:24:24 140210839125120 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: No valid checkpoint found.
InnoDB: A downgrade from MariaDB 10.2.2 or later is not supported.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
2022-07-06 10:24:24 140210839125120 [ERROR] Plugin 'InnoDB' init function returned error.
2022-07-06 10:24:24 140210839125120 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-07-06 10:24:24 140210839125120 [Note] Plugin 'FEEDBACK' is disabled.
2022-07-06 10:24:24 140210839125120 [ERROR] Unknown/unsupported storage engine: innodb
2022-07-06 10:24:24 140210839125120 [ERROR] Aborting
I tried looking at the web site (dev.mysql.com...) listed in the error file, but I can't figure out what they are talking about. Any help would be greatly appreciated as I'd really like to get CQRLOG working again. Thanks~
HI!
Looks weird!
Why would MariaDB error log direct to Mysql web pages ?
Are you absolute sure that you do not have MySql lying there somewhere?
Open command console and start cqrlog with:
cqrlog --debug=1
Within first abt 100 line s you should find lines like:
MySQLProcess.Executable: /usr/sbin/mysqld Parameters: --defaults-file=/home/saku/.config/cqrlog/database/mysql.cnf
--datadir=/home/saku/.config/cqrlog/database/
--socket=/home/saku/.config/cqrlog/database/sock
--port=64000
Trying to connect to database
2022-07-08 9:42:12 0 [Note] /usr/sbin/mysqld (mysqld 10.5.16-MariaDB) starting as process 22151 ...
TMySQL57Connection : Server connect failed.
Trying:1
select * from tables where table_schema = 'cqrlog_common'
Note the line having "starting as process" There should be mention about MariaDB.
Is there?
--
Saku
OH1KH
No, it seems to be trying to connect to mysql. What should I do? Should I explicitly try to remove MySQL, even though I have MariaDB installed?
56 us states loaded
Grid map created
/usr/bin/mysqld
MySQLProcess.Executable: /usr/sbin/mysqld Parameters: --defaults-file=/home/fred/.config/cqrlog/database/mysql.cnf
--datadir=/home/fred/.config/cqrlog/database/
--socket=/home/fred/.config/cqrlog/database/sock
--port=64000
Trying to connect to database
2022-07-10 8:27:17 139727776943232 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB-0ubuntu0.18.04.1) starting as process 31504 ...
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
Well, you have MariDB starting there.
Now it looks weird. What has happened during mean time if Cqrlog has started before? Many linux updates?
Make quick test if Cqrlog starts from clean.
There are two ways to do it.
1)
Save your /home/fred/.config/cqrlog/ folder to some safe place (if you have log with qsos there) then delete the folder and start Cqrlog.
2)
Make copy of Cqrlog binary with another name and start the copy from console. It will do another "/home/fred/.config/cqrlog_new_name" folder for it.
sudo cp /usr/bin/cqrlog /usr/bin/cqrlogX
cqrlogX
In either case; Did cqrlog start now with new empty log ?
if it started:
If you used 1) and have full adif backup of your log(s) you can import them and fix the preferences and continue to use Cqrlog.
if you used 2) and have full adif backup of your log(s) you can delete /home/fred/.config/cqrlog/ start Cqrlog again and after start adif import logs and fix the preferences and continue to use Cqrlog. You may remove new named cqrlog binary and it's folder if you like.
If it did not start:
Then restore the original folder /home/fred/.config/cqrlog/ back (if you used test 1) ) and the it is time to try things in link
https://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
As you now have backup copy of /home/fred/.config/cqrlog/ enter to /home/fred/.config/cqrlog/database folder and delete all
ibdataX, ib_logfileX and mysql.err files where "X" may be some number ( usually 1 or 0)
Try to start Cqrlog again. Does it start now?
If not, check and remove those files again and then go /home/fred/.config/cqrlog/database/cqrlog001 folder and remove all files with extension ".frm" (you may have to adjust your file browser view to "detailed" to see the extensions of file names)
Try to start Cqrlog again. Does it start now?
If not I am quite out of ideas...
--
Saku
OH1KH
edit to msg #6
Actually if you tested clean start using way 1) or 2) and it did not work then there is no mind to continue other tests until you can start Cqrlog from clean.
So do not go further and consider first to find out why the clean start does not work.
Maybe starting cqrlog with --debug=1 parameter and checking what it shows now and what is in mysql.err file
--
Saku
OH1KH
You solved my problem. I just renamed the config file and was able to start CQRLog cleanly. I'll just import my QSOs into the new log from backup, and everything should be fine.
Thanks again for your help!
I meant SAKU, not "sake." Sorry for that. Thanks again!