Hi!
I have observed that the DX-cluster (web-version) stops every day at the same time, 10.14z. It will not re-connect automatically or manually, it is stuck in "connecting". The only ways to get it working is to re-start the CQRLOG program or to press "connect" again after a longer time (works when I see that it has stopped hours ago).
Other internet services seem to run fine before, during and after 10.14z. I have changed my router a few months ago for other reasons, this problem is the same. I am connected to it with LAN cable (no wi-fi). I use CQRLOG version 2.4.0 on Ubuntu 18.04 LTS. I have had this kind of problem on earlier CQRLOG versions on earlier Ubuntu versions as well. Not sure if it has been daily interruptions earlier.
Is there some way to track this problem? I guess something happens in my internet connection, probably outside my local network that CQRLOG does not like.
Not a big problem, just got curious.
BR Mikael SM6VJA
HI Mikael!
This is interesting. I have never head "timed" dropouts before. Telnet DXCluster seems to drop for some users (randomly) and also 24/7 running cqrlogs may have "hickups" at midnight when database rotates it's logs.
Does it happen if you open PC and cqrlog just two minutes before that time, or needs it longer run time before that time to happen?
Do you have another computer to test if it stops also there?
Can you use mobile internet from PC during that time to see does it have same effect ?
Perhaps you could look at system logs (where are they in Ubuntu, Fedora uses /var/log/messages) to see if that time something else happens at same time.
--
Saku
OH1KH
Hello Saku!
Usually I start the computer in the morning and then start CQRLOG + cluster. Then the last cluster spots have the time stamp 10.14z.
Thanks for the suggestion, I will try them all and get back when time permits.
BR Mikael SM6VJA
Mikael SM6VJA