You are here

Beta version with new CQ-monitor/Map mode

20 posts / 0 new
Last post
oh1kh
Beta version with new CQ-monitor/Map mode

Completely rewritten Cq-monitor/ Wsjtx map with Lazarus standard components. Does not use richmemo unit any more. Seems that previously slowly crowing cpu load is now away. This version can also be compiled with Lazarus v2.0 rcXX
Changes should show up to user with very minimal changes. (if any).

All credits of this change goes to Andreas, DL7OAP, who wrote whole monitor core using stringGrid component.

We have been busy last days with testing this new monitor. Now it seems to work quite well and it is time to get a bit more users to test it and report possible bugs.
When it is confirmed to work ok, it will find it's way as pull request to official version.

Beta test binary 2.3.0-209 with install instructions can be found from usual place http://www.saunalahti.fi/~sakny/bin/cqrlog2/
Sources are can be found from https://github.com/OH1KH/cqrlog-devel, look branch "newmonitor".
Sources against official 002 are in https://github.com/OH1KH/cqrlog, look branch "newmonitor" also there.

We like to hear your comments!

PY1ZRJ
Beta version with new CQ-monitor/Map mode

Hi,

I'm running OpenSUSE Tumbleweed, running a stable CQRLOG rpm from a Community Repository (home:dl8fcl:afu) and after latest Tumbleweed software updates, I get the known CQRLOG error "Invalid type cast".

So I decided to give a try with the binary Beta version available here http://www.saunalahti.fi/~sakny/bin/cqrlog2/ and such annoying error as disappeared!

I'm not totally sure if the CQRLOG Beta binary could have any relations with "Invalid type cast" error or not, but I would like to report my result here.

Thanks and regards,

Marco, PY1ZRJ

oh1kh
Beta version with new CQ-monitor/Map mode

Hi!
I have not seen that kind of error ever so there is not any fix specially made for that.
If understood ok beta binary now works.

So be happy...!

If understood wrong, please advise when the error appears (when using beta binary).

--
Saku
OH1KH

PY1ZRJ
Beta version with new CQ-monitor/Map mode

Saku,

I meant that when using the "Stable" cqrlog binary I get the error, while if I use the "Beta" cqrlog binary the "Type Cast Error " doesn't appears.

Regards,

Marco

oh1kh
Beta version with new CQ-monitor/Map mode

Fine !
Just wanted to make sure that I understood ok.

While testing new 2.3.0-212 (now released) I got same error and I know now what kind of situation causes that and how it is fixed. At least at that point where it was in beta.

But similar parts of source code exist in many places of cqrlog source. It may be that somewhere still is this kind of bug. (I hope not...)

--
Saku
OH1KH

PA3HGC
Beta version with new CQ-monitor/Map mode

Hi,

Just upgraded from 2.3.0-211 to 2.3.0-212 (64 bit). Everything seems to work on my Ubuntu 18.04.2 LTS PC with 4.15.0-46-generic x86_64 kernel.

Upgrading to 2.3.0-213 however gives me the following message: "Error during connection to database: TMySQL57Connection : Server connect failed." On 2.3.0-212 and lower I do not get this error. Any idea? For the time being, I revert to 2.3.0-212.

Thanks and regards,
Guenter
PA3HGC

oh1kh
Hi!

Hi!
Thanks fro report.
No ideas right away. For me (Fedora 28) it works ok. Have you checked this message chain? https://www.cqrlog.com/node/2223

That comes first in to my mind.

--
Saku
OH1KH

DO1YHJ
Database Error

Hi,

same problem here with Mint 19 and mysql (mariadb). Beta 213 did not connect to the running Database, Beta 212 did without restarting anything. I only changed the cqrlog Binary, nothing else.

73 de Heinz-Juergen

DO1YHJ
Database Error

Hi,

i checked syslog as described in #7, no apparmor error. The fix didn't work also. Beta 213 did not connect to the running database.

73 de Heinz-Juergen

oh1kh
Database Error

Hi!
Open console and type:
sudo tail -f /var/log/syslog

Open cqrlog and see if any messages like in https://www.cqrlog.com/node/2223 appear when cqrlog is starting.

If no similar messages are seen in syslog then start cqrlog from console with:
cqrlog debug=1 > /tmp/debug.txt
And add file /tmp/debug.txt to your next message.

I just downloaded 213.zip and copied binary from that to my own pc and it works here normally (Fedora 28)

--
Saku
OH1KH

DO1YHJ
Database Error

Hi,
this is the console output when starting Beta 213 with debug level:

meier@Linux-NUC /tmp $ cqrlog debug=1 > /tmp/debug213.txt
2019-03-17 13:13:53 140129104899200 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB-0ubuntu0.18.04.1) starting as process 2710 ...
2019-03-17 13:13:53 140129104899200 [Warning] Can't create test file /var/lib/mysql/Linux-NUC.lower-test
/usr/sbin/mysqld: One can only use the --user switch if running as root
2019-03-17 13:13:53 140129104899200 [ERROR] mysqld: File '/var/lib/mysql/aria_log_control' not found (Errcode: 13 "Permission denied")
2019-03-17 13:13:53 140129104899200 [ERROR] mysqld: Got error 'Can't open file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2019-03-17 13:13:53 140129104899200 [ERROR] Plugin 'Aria' init function returned error.
2019-03-17 13:13:53 140129104899200 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2019-03-17 13:13:53 140129104899200 [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.

2019-03-17 13:13:53 140129104899200 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: Using Linux native AIO
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: Using SSE crc32 instructions
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-17 13:13:53 140129104899200 [Note] InnoDB: Completed initialization of buffer pool
2019-03-17 13:13:53 140129104899200 [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode
2019-03-17 13:13:53 140129104899200 [ERROR] InnoDB: The system tablespace must be writable!
2019-03-17 13:13:53 140129104899200 [ERROR] Plugin 'InnoDB' init function returned error.
2019-03-17 13:13:53 140129104899200 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-03-17 13:13:53 140129104899200 [Note] Plugin 'FEEDBACK' is disabled.
2019-03-17 13:13:53 140129104899200 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
/usr/sbin/mysqld: Too many arguments (first extra is ' --defaults-file=/home/meier/.config/cqrlog/database/mysql.cnf --datadir=/home/meier/.config/cqrlog/database/ --socket=/home/meier/.config/cqrlog/database/sock --port=64000').
2019-03-17 13:13:53 140129104899200 [ERROR] Aborting

And this is in the debug file:

Cqrlog Ver:2.3.0 (213) Date:2019-03-16
**** DEBUG LEVEL 1 ****

SSL libraries:
libssl.so
libcrypto.so
Loaded 127477 LoTW users
Loaded 121262 eQSL users
Loaded 38264 SCP calls
*
User home directory: /home/meier/
Program home directory: /home/meier/.config/cqrlog/
Data directory: /home/meier/.config/cqrlog/database/
Memebers directory: /home/meier/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
*
56 us states loaded
/usr/bin/mysqld
MySQLProcess.Executable: /usr/sbin/mysqld --defaults-file=/home/meier/.config/cqrlog/database/mysql.cnf --datadir=/home/meier/.config/cqrlog/database/ --socket=/home/meier/.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
Closing dDXCC
Closing dData

File: 
DO1YHJ
Database Error

Hi,
with Beta 212 console output:
meier@Linux-NUC /tmp $ cqrlog debug=1 > /tmp/debug212.txt
2019-03-17 13:19:47 140375251532928 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB-0ubuntu0.18.04.1) starting as process 3801 ...
rig_open: error = IO error

Debug File with Beta 212 is attached

File: 
PA3HGC
Database Error

Hi!
Very similar on Ubuntu 18.04.2 here: No apparmor error in syslog. The fix linked in #7 does not work either. Beta 213 does not connect to the running database whereas I have no such trouble with Beta 212.

Please find below the console output when starting Beta 213 with debug level:

pa3hgc@intense-PC:~$ cqrlog debug=1 > /home/pa3hgc/tmp/debug.txt
2019-03-17 14:22:19 140604790336640 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB-0ubuntu0.18.04.1) starting as process 3480 ...
2019-03-17 14:22:19 140604790336640 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4186)
2019-03-17 14:22:19 140604790336640 [Warning] Can't create test file /var/lib/mysql/intense-PC.lower-test
/usr/sbin/mysqld: One can only use the --user switch if running as root
2019-03-17 14:22:19 140604790336640 [ERROR] mysqld: File '/var/lib/mysql/aria_log_control' not found (Errcode: 13 "Permission denied")
2019-03-17 14:22:19 140604790336640 [ERROR] mysqld: Got error 'Can't open file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2019-03-17 14:22:19 140604790336640 [ERROR] Plugin 'Aria' init function returned error.
2019-03-17 14:22:19 140604790336640 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2019-03-17 14:22:19 140604790336640 [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.

2019-03-17 14:22:19 140604790336640 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: Using Linux native AIO
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: Using SSE crc32 instructions
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-17 14:22:19 140604790336640 [Note] InnoDB: Completed initialization of buffer pool
2019-03-17 14:22:19 140604790336640 [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode
2019-03-17 14:22:19 140604790336640 [ERROR] InnoDB: The system tablespace must be writable!
2019-03-17 14:22:19 140604790336640 [ERROR] Plugin 'InnoDB' init function returned error.
2019-03-17 14:22:19 140604790336640 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-03-17 14:22:19 140604790336640 [Note] Plugin 'FEEDBACK' is disabled.
2019-03-17 14:22:19 140604790336640 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
/usr/sbin/mysqld: Too many arguments (first extra is ' --defaults-file=/home/pa3hgc/.config/cqrlog/database/mysql.cnf --datadir=/home/pa3hgc/.config/cqrlog/database/ --socket=/home/pa3hgc/.config/cqrlog/database/sock --port=64000').
2019-03-17 14:22:19 140604790336640 [ERROR] Aborting

Here is the contents of the 213 debug txt file:

Cqrlog Ver:2.3.0 (213) Date:2019-03-16
**** DEBUG LEVEL 1 ****

SSL libraries:
libssl.so
libcrypto.so
Loaded 126926 LoTW users
Loaded 120957 eQSL users
Loaded 38264 SCP calls
*
User home directory: /home/pa3hgc/
Program home directory: /home/pa3hgc/.config/cqrlog/
Data directory: /home/pa3hgc/.config/cqrlog/database/
Memebers directory: /home/pa3hgc/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
*
56 us states loaded
/usr/bin/mysqld
MySQLProcess.Executable: /usr/sbin/mysqld --defaults-file=/home/pa3hgc/.config/cqrlog/database/mysql.cnf --datadir=/home/pa3hgc/.config/cqrlog/database/ --socket=/home/pa3hgc/.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
Closing dDXCC
Closing dData

Thanks! - Guenter

File: 
PA3HGC
Database Error with Beta 213

Hi!
Just for the sake of completeness here the console output with Beta 212:

pa3hgc@intense-PC:~$ cqrlog debug=1 > /home/pa3hgc/tmp/debug.txt
2019-03-17 14:58:20 139740302560384 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB-0ubuntu0.18.04.1) starting as process 4821 ...

and the attached debug.txt file with Beta 212.

Thanks! - Guenter

File: 
oh1kh
Database Error with Beta 213 - do not use

HI!

I got several reports of 213 defunct, as you can expect number 13 is not good ;-(

It has something to do about fixing "command line is deprecated" warnings from cqrlog source.

Sad thing is that I have Fedora 28 (x64) and Ubuntu 18.04.2 LTS (i386) and both are running version 213 without problems !

Before releasing 213 I found error in LoTW export when cqrlog was calling tqsl. It has "parameter error" although command line that should start tqsl was copied from debug dump and pasted to cosole and lit WORKED. But not when it was initiated from inside cqrlog.

This seem to be same problem, mysql is called with right parameters but it does not start.

And while writing this I got idea why my computers work:
I call "real" mysql server from port 3306 with my programs, I do not use "save log data to local machine" that initiates new mysql instance and uses it from port 64000.

I look after this.
Be patient and look for 214.

--
Saku
OH1KH

PA3HGC
Beta 214

Hi!

Beta 214 seems to work fine on Ubuntu 18.04.2 LTS 64-bit.

Thank you for fixing the issues.

Vy 73,
Guenter PA3HGC

DO1YHJ
Beta 214

Second that.
Beta 214 is up and running. :-)

tnx

73 de Heinz-Juergen

PY1ZRJ
Version 2.30(214)

Hello Saku,

I'm running Beta 212 on openSUSE Tumbleweed 64 bits and it works flawlessly, jointly with WSJT-X.

Which are the main differences/changes among 212 and 214, which is the latest Beta available?

It is worth to update to 214?

Tks, 73 de PY1ZRJ

oh1kh
Version 2.30(214)

HI!

I'm just about to release 215 for testing within few hours, I hope.

You can always check the differences by downloading the zip file and extracting it.
There you find a text file README.OH1KH that is a log of changes.

--
Saku
OH1KH

PY1ZRJ
Version 2.30(214)

Thanks Saku,

Understood now, I will read the README.OH1KH of future releases.

Best regards,

Marco PY1ZRJ