Hi,
If I leave cqrlog (1.9.0 on 32bit Fedora/Intel) connected to dx cluster (VE7CC), the program crashes usually within two hours. I left it running with debugging enabled and this is what I see at the end of the output:
DX de UA4M-#: 3507.0 R5WW CW 29 dB 23 WPM CQ 2011Z
Enter critical section On Receive
Leave critical section On Receive
DX de AC0C-#: 14052.0 N1DN CW 05 dB 15 WPM CQ 2011Z
Enter critical section On Receive
Leave critical section On Receive
DX de SK3W-#: 7014.6 OZ2TF CW 15 dB 26 WPM CQ 2011Z
Enter critical section On Receive
Leave critical section On Receive
DX de DF4UE-#: 21025.5 DL1VDL CW 09 dB 26 WPM CQ 2011Z
Enter critical section On Receive
Leave critical section On Receive
DX de DF4UE-#: 14070.7 9A6KSF PSK31 14 dB CQ 2011Z
Enter critical section On Receive
Leave critical section On Receive
DX de PY2KC: 7135.0 PY3VV RS LSB 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de DJ9IE-#: 3578.2 DK2SC CW 45 dB 21 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de HB9DCO-#: 10104.1 OH5XK CW 15 dB 25 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de HA6VH: 7022.0 SN0CIPHER 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de DL1EMY-#: 14025.6 9A15P CW 36 dB 20 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de K1TTT-#: 7077.4 WD8JMA RTTY 12 dB CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de PA0MBO-#: 14033.0 OH6NVC CW 42 dB 29 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de HA6PX-#: 7004.8 EW6BY CW 32 dB 24 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de ON5KQ-#: 14013.5 M0GLV CW 30 dB 26 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de DL1EMY-#: 7025.3 OK1JRU CW 21 dB 22 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de IK3STG-#: 14060.8 IT9QAU CW 34 dB 14 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de KH6DC: 14090.0 AH6DX HI QSO PARTY RTTY 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de WZ7I-#: 7053.4 WA8KOQ CW 21 dB 14 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de WZ7I-#: 14019.4 AA3B CW 24 dB 29 WPM CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de PY2TMV: 7137.0 PY2JOS CVA DX CONTEST.Cqinsg 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de DL9GTB-#: 21071.0 IZ5WRC PSK31 15 dB CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de HA6VH: 7023.5 OM2015TITANIC 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de HA6VH: 7023.5 OM2015TITANI 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de SM6FMB-#: 7041.3 2E0SQL PSK63 22 dB CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de PP5JD: 3750.0 PU5BOY 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de YV4DHS: 14101.0 R7RIB ROS Sebastopol Black sea 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de DF4UE-#: 3581.3 DF40YLH PSK31 13 dB CQ 2012Z
Enter critical section On Receive
Leave critical section On Receive
DX de KM3T-#: 10120.0 OZ1HDF CW 08 dB 21 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de KM3T-#: 14015.1 PC15SAIL CW 15 dB 23 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de DF7GB-#: 7023.5 OM2015TIT CW 21 dB 28 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de HA6PX-#: 7014.0 DJ3GS CW 27 dB 15 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de W3UA-#: 50100.1 K1QT CW 24 dB 26 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de W0LFA-#: 14056.2 NM1W CW 27 dB 16 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de K1TTT-#: 14051.1 W4FOA CW 12 dB 16 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de OE6TZE-#: 7008.9 S53A CW 33 dB 27 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de HB9DCO-#: 10114.0 EJ7NET CW 14 dB 27 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de HB9DCO-#: 7018.0 OZ/DL9LBR CW 14 dB 19 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de 5B4AGN-#: 21011.0 DL1BUG CW 24 dB 25 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de ZL2IFB: 14200.0 HL3AKL 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de OZ5W-#: 21022.0 XR3MIN CW 07 dB 20 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de K4XD-#: 7033.4 W2LB CW 30 dB 25 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de KM3T-#: 7028.5 KD8BBK CW 21 dB 32 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de SM6FMB-#: 7041.0 EA3KY PSK31 19 dB CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de KM3T-#: 14071.5 KW4JY PSK31 12 dB CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de W4KKN-#: 14011.3 F5LPY CW 13 dB 26 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de OE6TZE-#: 3515.0 DK65DARC CW 23 dB 21 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de K8ND-#: 7035.3 W2IQK CW 28 dB 18 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de HB9DCO-#: 7022.0 SN0CIPHER CW 27 dB 26 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de DL9GTB-#: 14070.9 IZ3XNJ PSK31 48 dB CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de JL1UTS: 7008.8 S53A 599 Loud as always 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de A61EK: 14244.0 8P6FX 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de KP3Z-#: 18077.0 KW7D CW 09 dB 22 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de HA1VHF-#: 21014.0 PY4TW CW 19 dB 31 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de DL9GTB-#: 14072.8 IK0OEF PSK63 37 dB CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de SK3W-#: 1816.0 DF1TL CW 16 dB 20 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de IK3STG-#: 10105.0 OZ1OM CW 15 dB 27 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de PY5JCT: 3765.0 PU5NBX CQ CVA CQ CVA 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de KM3T-#: 14072.4 KF2GQ PSK31 18 dB CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de E79D: 14210.5 T46BC CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de SM6FMB-#: 14072.4 M0AUI PSK31 12 dB CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de PY4EK: 7091.0 PP2FRS LSB 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de JA4ZRK-#: 3511.1 JG2IBE CW 25 dB 17 WPM CQ 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de VE3VEE: 14017.0 OM2015TITANIC 2013Z
Enter critical section On Receive
Leave critical section On Receive
DX de VE3VEE: 14017.0 OM2015TITANI 2013Z
Enter critical section On Receive
Leave critical section On Receive
1
2
3
4
5
6
Closing DXCluster window
Closing TRX
(cqrlog:16129): GLib-CRITICAL **: Source ID 17 was not found when attempting to remove it
(cqrlog:16129): GLib-CRITICAL **: Source ID 16 was not found when attempting to remove it
(cqrlog:16129): GLib-CRITICAL **: Source ID 49 was not found when attempting to remove it
(cqrlog:16129): GLib-CRITICAL **: Source ID 48 was not found when attempting to remove it
(cqrlog:16129): GLib-CRITICAL **: Source ID 54 was not found when attempting to remove it
(cqrlog:16129): GLib-CRITICAL **: Source ID 53 was not found when attempting to remove it
Control window
Closing GrayLine window
[FORMS.PP] ExceptionOccurred
Closing ini file ...
[FORMS.PP] ExceptionOccurred
Closing dDXCC
Deleting config file: 2cqrlog.cfg
Deleting config file: cqrlog.cfg
Closing dData
An unhandled exception occurred at $0807D581 :
EInOutError :
$0807D581
$080738B8
$081B0035
$0806E4C4
$0806E749
$0806E4C4
$0806E749
$081B57F3
$080905F5
I was also playing with the ARM (Raspi 2) version of cqrlog and I see similar crashing there. My computer is a bit old and slow (like Raspi 2), so there could be some timing related issue.
Any thoughts?
Thanks,
Jussi Eloranta (AA6KJ)
Sun, 2015-08-23 21:21
#1
cqrlog crash when connected to dx cluster
HI,
I also tried to compile cqrlog from github - still seeing the crash. I forgot to mention that the dialog that pops up says: "Cannot open a non-select statement."
Jussi (AA6KJ)
Hi Jussi,
it's great you can compile source code from github, it will help a lot. Please edit the Makefile and remove line with $(ST) src/cqrlog, compile and install cqrlog again. After it crashes, you should see more information. The " $(ST) src/cqrlog" remove debugging information from executable.
I had the same problem but it appeated only once :(. Thank you for all information!
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
HI,
And apparently sometimes the dialog just has ": Error executing query: MySQL server has gone away."
At worst times the crash happens in 15 min. but sometimes after several hours.
Jussi (AA6KJ)
A slightly different output with (debugging):
DX de DJ9IE-#: 21030.0 3B9FR CW 12 dB 29 WPM CQ 1351Z
Enter critical section On Receive
Leave critical section On Receive
DX de JE1SGH-#: 21026.0 LZ2RS CW 22 dB 20 WPM CQ d data on positi\
on:143
Deleted data on position:0
Deleted data on position:0
Invalid file handle
1351Z
Enter critical section On Receive
Leave critical section On Receive
1
2
3
4
5
6
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Hello, i have a problem like this, too. What happen if you close the DX-CLUSTER or BAND MAP and run Cqrlog again? My post: http://www.cqrlog.com/node/1452
Hi,
I left cqrlog running for a day without bandmap window (but connected to cluster) and no crash so far. So, it may be that the problem is related to the bandmap function. I will recompile and leave the symbols in as Petr suggested - hopefully it will give more info.
Jussi
Hi,
Unfortunately, still crashed without bandmap. It just happened to take longer that time. Ran it again and crashed within 1 hour (without bandmap). This time I had the symboks in but I don't quite see any additional information in the output:
DX de W4KKN-#: 14054.2 KP4RD CW 19 dB 15 WPM CQ 0135Z
Enter critical section On Receive
Leave critical section On Receive
DX de AA4VV-#: 14051.0 W6UT CW 26 dB 12 WPM CQ 0135Z
Enter critical section On Receive
Leave critical section On Receive
1
2
3
4
5
6
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
[FORMS.PP] ExceptionOccurred
Closing ini file ...
End dmDXCC
Complete end dmDXCC
Closing dDXCC
Deleting
(cqrlog:6241): GLib-CRITICAL **: Source ID 17 was not found when attempting to remove it
(cqrlog:6241): GLib-CRITICAL **: Source ID 16 was not found when attempting to remove it
(cqrlog:6241): GLib-CRITICAL **: Source ID 49 was not found when attempting to remove it
(cqrlog:6241): GLib-CRITICAL **: Source ID 48 was not found when attempting to remove it
(cqrlog:6241): GLib-CRITICAL **: Source ID 54 was not found when attempting to remove it
(cqrlog:6241): GLib-CRITICAL **: Source ID 53 was not found when attempting to remove it
config file: 2cqrlog.cfg
Deleting config file: cqrlog.cfg
Closing dData
[TGtk2WidgetSet.Destroy] WARNING: There are 1 TimerInfo structures left, I'll free them
Petr: where are those numbers 1 to 6 printed in (source file name & line?) I could try to add some debug prints but I would need to find the right place first. Probably somewhere in fDXCluster.pas ?
Jussi (AA6KJ)
I missed the following debug output when running with symbols:
Index_: 0
select * from call_alert where callsign = 'K5H'
Color: clBlack
Index_: 0
Spot nr. 1
ThSpot: DX de K5TLL: 18138.0 K5H 10th Anniversary Hurricane Kat 0107Z
ThColor: 0
TelThread.Execute - before Synchronize(@frmDXCluster.SynTelnet)
TelThread.Execute - after Synchronize(@frmDXCluster.SynTelnet)
TelThread.Execute - enter critical section
TelThread.Execute - leave critical section
Spot: DX de K3LR-#: 21033.1 K0FL ection On Receive
Leave critical section On Receive
DX de K3LR-#: 21033.1 K0FL CW 31 dB 21 WPM CQ 0107Z
Enter critical section On Receive
Leave critical section On Receive
DBPing - select * from cqrlog002.db_version
DBPing - select CW 31 dB 21 WPM CQ 0107Z
NOT found - L21AXR
SELECT * FROM cqrlog_common.bands where (b_begin <=21.0331 AND b_end >=21.0331) ORDER BY b_begin
* from cqrlog002.db_version
TApplication.HandleException : Error executing query: Lost connection to MySQL server during query
Stack trace:
$084103E5
$084614EF MYSQLERROR, line 272 of ./mysql/mysqlconn.inc
$084643AB TCONNECTIONNAME__ROLLBACK, line 1189 of ./mysql/mysqlconn.inc
$084434CF
$08374DD5
$08374D3F
$083685E4
$B6EB68D2
DX de N7ELL: 18153.0 XR44MIN 0107Z
Enter critical section On Receive
Leave critical section On Receive
DX de WA7LNW-#: 14045.7 K5J CW 34 dB 21 WPM CQ 0107Z
Enter critical section On Receive
Leave critical section On Receive
DX de NC7J-#: 14054.1 KP4RD CW 13 dB 14 WPM CQ 0107Z
With the web cluster interface (bandmap & propagation windows closed), I got:
TApplication.HandleException : Error executing query: Lost connection to MySQL\
server during query
Stack trace:
$084103E5
$084614EF MYSQLERROR, line 272 of ./mysql/mysqlconn.inc
$08464425 TCONNECTIONNAME__STARTDBTRANSACTION, line 1196 of ./mysql/mysqlco\
nn.inc
$084435EF
$08105DA4 AS
Hi, One thing that seems to affect the stability is the ping time for database connection refresh. If I change cDB_PING_INT from 300 to 300000 (in dData.pas) then things become much more stable. I wonder if there is some kind of race condition somewhere that becomes more probable with short database connection refresh times? Jussi Eloranta (AA6KJ)
Suffered similar "effect" when running wsjt-x remote with dx-custer and bandmap. I always tought that there is something in my part of code that causes crash.
Made similar change to cDB_PING_INT as Jussi suggests and so far I have not had any crash after that.
If it does not remove reason it makes crashes to happen lot more seldom than previously.
I'm also using Fedora 32bit/Intel based system.
Saku OH1KH
--
Saku
OH1KH
Forgot to mention that I'm using MariaDB from localhost:3306.
Using this poor mini laptop cqrlog opens faster if I use mysql running as daemon.
This mysql syncs also with another one running in my server machine so both databases are equal all the time.
I use servers database for running cqrweblog (DL8BH) for remote access with phone or tablet.
How ever using runtime mysql or mysql daemon seems not have any difference for this crash "feature".
Saku OH1KH
--
Saku
OH1KH
I added the ping because after a few hours connection to MySQL were lost. There is KeepAlive option but it didn't work.
I can disable the ping, maybe it will work without it. Recent versions of cqrlog use database more often than old versions.
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
It might be that if dx-cluster, bandmap (and wsjtx-cq monitor) is not in use DB is accessed so seldom that extra ping is needed.
But those are accessing DB so often that ping is not needed. Unless band is dead and ISP has also web failure at same time ;)
So it might be save to remove it. Or make it configurable via preferences.
DB is usually accessed via localhost, Very seldom via external IP.
I do not know/remember is there any tcp/ip parameter that could close the localchost IP connection if not in use. (localhost keep alive)
I have once had case in work-life where DB was always lost after some time. Reason was in separate Cisco ASA firewalling device that had too short keep alive time in tcp settings. But in that case clients and DB server were in separate IP addresses.
73
Saku
--
Saku
OH1KH
The database ping is now disabled. I hope it will better.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com