Hi
Updated to latest version 1.2.2 and noticed, that dxclusterwin. somehow
stops receiving spots after random time. If I give to cluster
forinstance sh/u command, I get reply, but spots sill stays away?
With 1.2.1 version this didn't happen. Anyone else noticed? During
cqww contest had to restart cqrlog several times, getting spots
working again. Disconnecting and reconnecting didn't help.
And I compared, if our cluster (OH1RCF) had some
troubles, by connecting there with another client, I got spots ok
with that. Using Fedora 15.
Another thing is, that this new version looses mysqld connect every
now and then, more randomly? Didn't notice this behaviour at 1.2.1 version.
I could use somekind of debugmode for this also, just need info, how
to set cqrlog into debug mode?
Jarmo
Arrgh!
Just found similar from Bugs forum.
My bad..
Jarmo
<p>Jarmo</p>
Hi Jarmo,
when I was fixing bugs for version 1.2.2 I tried the DX cluster but didn't find anything wrong. I use it every day and getting spots without any problem.
CQRLOG has debug mode activated. Please run it from console and please post here what it writes down after crash. Thank you!
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr
Sorry for time gone. I have been now running cluster window succesfully without any
hickups. And propably found reason. When I connect and set up trxcontroll to my kenwood, all kind of slowlyness and stops happens. Trx in still not working. But when I get trxcontrol away, everything works perfect. I had some troubles with mysql, I upgraded into Fedora 16 and there was bug, that caused mysqld not starting. Noticed, when lost some qso's. Now seems to work, exept radiocontrol. Have been little busy to debug, but next week probably I spend some time to investigate more.
73 de Jarmo
<p>Jarmo</p>
DX CLUSTER command line history feature solvable?
Many thanks!
Viktor