Ahoi
Now using version 1.6.0. Otherwise working suberb, BUT... when leaving Cqrlog untouched for some hours, I click from cluster window some call, I get message Lost connection to Mysql server etc. This problem comes every time, example I have cqrl
on over night and in the morning I try to do that, I get error message.
Have to restart cqrl again. Anyone else...?
Jarmo
Yes
This is exactly what is happening to me. Petr is looking into it.
73
Benny K5KV
Same here, after some hours of no use mysql seems to have stopped, ie cqrlog has lost connection and complains.
73 de Olaf - LA3RK
Olaf Devik LA3RK
Why would you leave CQRlog on If you are not using it? Just kinda wondering.
Tom K8WDX
Hi
In my case, I have cluster on all the time, because I'm sysop, so naturally have log on also, Solution for this, is not, closing cqrlog, it is obvious, that there is some kind of bug, wether mysql or cqrlog, but bug anyway..
<p>Jarmo</p>
Just had the mysql error. CQRLOG had been running overnight in morning when typing a call in call field to check log, cqrlog warned about no mysql connection. Following appeared from console after selecting cancel to kill program:
(cqrlog:26448): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
WARNING: TLCLComponent.Destroy with LCLRefCount>0. Hint: Maybe the component is processing an event?
Closing ini file ...
[TGtk2WidgetSet.Destroy] WARNING: There are 2 TimerInfo structures left, I'll free them
An unhandled exception occurred at $000000D7 :
EAccessViolation :
$000000D7
$08192623
$0808A57A
$0805DEFF
The following appeared just before cancel was selected, basically a dump of adresses and info that mysql server has gone away.
TApplication.HandleException : Error executing query: MySQL server has gone away
Stack trace:
$083960CF
$08449BB7
$0844AF01
$0841169F
$08411F47
$083982D2
$08411105
$080CEF76
$080D567A
$082565ED
$08256626
$08256EC0
$08258E67
$0806C26A
$08255C3D
$08330957
$083062A9
Hope the above is to help for someone. Would love to see this problem disappear. It is becoming a nuisance.
73 de Olaf - LA3RK
Olaf Devik LA3RK
Hi Olaf,
thank you for bugreport! I know where is the problem and it should be fixed in new version of CQRLOG.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com