Hi,
after upgrading from Kubuntu 19.10 to 20.04 another problem occurs.
The DX-Cluster Window "Telnet" does not work or stops after a few lines. The telnet connection in the Linux console works fine.
After a restart of CQRLOG spots appear in the "telnet" window. After some time, however, the window freezes. After a restart the "telnet" window works again, but then freezes again after some time.
The DX-Cluster Window "Web" in CQRLOG works as well.
73, Wolfgang
DL2KI
28.05.2020:
A compilation of the current source code does not change the behaviour.
The Telnet DX cluster is especially interesting for those OM's that are QRV in CW. There they can connect the reverse beacon net via Telnet.
This makes it much easier to track CW activity, especially at close range, than via the regular DX cluster.
Currently I use the RBN display via the web browser as a workaround. Of course the bandmap and "Callsign alert" will not work with this.
73, Wolfgang
DL2KI
Hi,
here now an extract of the debug data and a picture of the frozen telnet window.
In the data file you find the lines of the telnet window in the lines 67 to 150.
Please rename the file to "_cqrlog.zip".
73, Wolfgang
DL2KI
File:
Hi!
I suspect that spot rate from reverse beacon is so high that it is causing problems that are not seen in "normal" DXCluster connection. There is a limit of lines in telnet dx cluster. I just do not remember how big it was. A couple thousand lines perhaps.
Then I do not know what happens when limit is reached. Of course program should handle this and drop the oldest ones away, but who knows if there lays a bug somewhere.
Why do you connect reverse beacon with telnet dx cluster? Have you tried the RBN monitor? (NewQSo/Window/RBNmonitor) It connects to reverse beacon and you have filter there to set some limits to rbn spots.
I guess you are not interested in all rbn spots. Telnet DXCluster does not have filter and so all spots are printed out.
There is difference how display routine is made between Telnet DXCluster and RBN monitor.
--
Saku
OH1KH
Hi!
At the moment CQ WW WPX CW is running and I have kept now both RBN monitor (filter: source EU) and Telnet DXCluster connected to reversebeacon.net for about 15 minutes.
Both running still OK.
Besides I have also wsjtx and cqrlog's wsjt-x remote (with CQ monitor) open and it is workin ok, too.
The only thing to notice is that telnet DXCluster spot rate is so high that there is no joy using it. You can't read nothing. Speed is so high.
With RBNmonitor and source EU filter you are able to catch something even when spot rate there is also very high.
File:
--
Saku
OH1KH
Hi Saku,
thanks for the feedback.
It's not the spot rate. It was 4860 at the time of analysis.
I've already described the telnet window's behavior at too high a spot rate here. https://www.cqrlog.com/node/1925
As you can see in the debug log, the spots continue to run after the telnet window is frozen. Apparently, internal processing continues after the window is frozen.
Maybe it is a problem in the program section of the telnet window or a problem with the SQL database. The problem with the club log upload could also be related to this.
Also, the telnet window with "telnet.reversebeacon.net" worked normally before the upgrade. It is the same problem as when I upgraded from Kubuntu 18.04LTS to 18.10. As far as I remember, I completely reinstalled the operating system at that time. https://www.cqrlog.com/node/2198
When using "hamqth.com 7300" as a telnet source, the problem also occurs.
The cause of the problem therefore does not seem to be directly related to the spot rate.
I use the telnet window because of "Callsign alert" and the insertion of the data into the band map (show only active band)
I'm going to try it with the RBN monitor. It would be better if the bug in the program would be fixed.
Clublog-Upload I disabled once and do this with a small script after closing CQRLOG. But even this is surely only a workaround.
73, Wolfgang
DL2KI