Propagation Window stopped working

17 posts / 0 new
Last post
DO1YHJ
Propagation Window stopped working

Since a few Days the Propagation Window stopped working. There is no content inside the Window, only the Background Color appears. Starting cqrlog from Terminal gives a "Wrong image format" on opening the Propagation Window.

Heinz-Juergen DO1YHJ

oh1kh
Propagation Window stopped working

Hi Heinz-Juergen!

Same note here!
If you set preferences/propagation/Show as text information then cqrlog will load xml text information and place it to file ~/.config/cqrlog/solar.xml
If you the open it with text editor you can see interesting contents.

Lines like:
www.hamqsl.com/solarxml.php
Website Security - Access Denied
Mozilla/4.0 (compatible; Synapse)
Bad bot access attempt.

The first line is the line cqrlog requests from web site. If you copy it to your web browser and try with it reply is an xml data of solar conditions. I.E. it works with your browser. Even when it comes for same IP address that your cqrlog uses.

I think the key is how cqrlog introduces itself "Mozilla/4.0 (compatible; Synapse)" that causes blocking to activate.
I try to look if that can be changed so that it introduces itself as Firefox, or some other common browser and look if that changes things.

Same happens, I think, when you request propagation as image. It is just not so easy to debug than text mode.

--
Saku
OH1KH

oh1kh
Propagation Window stopped working

Hi!
There is a quick fix!
It was just so that I guessed. You need a hex editor for fixing. I used program mc

Start
sudo mc
To have root privileges
Locate the binary file /usr/bin/cqrlog and do a copy (F5) to file /usr/bin/cqrlog_save for restoring if edit goes wrong.
Open file /usr/bin/cqrlog for edit (F4) you see "garbage"
Seek string (F7) Mozilla/4.0  with "Case sensitive" cheked. You should find:

Press key "Ins" to change insert mode to replace mode. Move cursor (click with mouse or use arrow keys) over "c" of word "compatible" and start writing: 

X11; Linux x86_64 and two spaces. Be sure that you are in overwrite mode and not inserting any characters so that file length does not change.

Save edited file (F2) and test.

For me it started to work immediately.

--
Saku
OH1KH

dj4qv
Solution worked wunderfully

Had the same problem, Saku your solution worked like a charm! TU! One small remark: after installing mc I had to check "use internal editor" under options menue to use the proper editor.

vy 73!
Wolfgang

--
Wolfgang
DJ4QV

n1kx
Propagation Window stopped working

Thanks for the fix, Saku. I had been wondering if it was something specific to my setup, so I checked here to see if there were any others with the same problem. I was quite happy to see there was already a fix!

Dave
N1KX

sp3rxo
sp3rxo's picture
cqrprop

Hi,
Just checked that Saku's trick working with cqrprop app as well.

<p>SlaveckM, SP3RXO</p>

WG9L
Propagation Window stopped working

Saku,

Okay, I screwed this up, big time. Editing the hex file for cqrlog should be treated with extreme care, as I messed it up and am not sure how to recover.

I'm not very experienced on Linux commands, but attempted your solution using Midnight Commander (mc version 3.36.2). I was following along, as best I could and was able to replace the text string Mozilla/4.0 with X11; Linux x86_64 and two spaces, and then did a ^O or Write Out - then I quit the program. I tried to start CQRLOG, but it just sits and won't start. I did make a copy of the original cqrlog file from /usr/bin and copied it to my desktop. I can start CQRLOG by double clicking on the copy on my desktop, but I receive several error messages, but the program does start, however some things don't look right and it is not working correctly. How can I get back to where CQRLOG was at least working, but without the propagation window. I can live without that, I suppose.

Thanks,
Bob, WG9L

File: 

WG9L
Propagation Window stopped working

Additional image - 1 of 2

File: 

WG9L
Propagation Window stopped working

Additional image - 2 of 2

File: 

oh1kh
Propagation Window stopped working

Hi Bob!

Do not worry. You did copy of /usr/bin/cqrlog before editing to your desktop. All you need now is to copy that desktop file back to folder /usr/bin
If you do it with command console command it is something like:
sudo cp ~/Desktop/cqrlog /usr/bin
Or you can start mc:
sudo mc
and navigate to /usr/bin (other part of mc display) and to your desktop (the second part of mc display) and there select the file cqrlog and press F5 and OK.
It should copy cqrlog to /usr/bin. When file cqrlog has right folder you get rid of those errors. Try to start and see it is working.
After that try the edit again.
As said in message thread by Dj4QV, Wolfgang,  you must set "internal edit" of mc active first. Otherwise it uses external editor that may spoil the binary file. From your picture I can see you edited file with "nano" editor and that does not work for this.

To do this press F9 and from top menu "left-file-command-selections-right" select "selections" (2nd from right) and from opening window you see at the top "configuration" select it and from opening window top right check "Use internal edit" and then press OK"

Then you should get white on blue editor when you edit the file.
As you still have the cqrlog file on Desktop you do not need to make another copy, just start editing the /usr/bin/cqrlog file again.

 

--
Saku
OH1KH

WG9L
Propagation Window stopped working

Okay, Saku...
YOU ARE THE MAN !

These suggestions did work for me. Thanks to you and Wolf's information to change to the internal editor in MC. That solved the problem (and the colors showed in blue and white - just like your example - mine was black and white - that was probably a clue that I was not using the internal editor in mc, not to mention that at the top left corner of the editor, it clearly showed "nano"). I am VERY glad that I had the original cqrlog file copy. It really saved me this time. I now have CQRLOG working properly once again, and I can see the propagation information in the window. But why did this happen in the first place?

I went to N0NBH's web site (http://www.hamqsl.com/solar.html) and see that he made some changes recently with regards to Firewall and SSL security issues. Perhaps these were the cause of the propagation window information going away?? This problem of not seeing the propagation window fill with information only started recently but had never been a problem before.

Is this something that needs to be addressed by a new binary file update of CQRLOG, or is this an external issue because of N0NBH's website changes? It seems to me that "any" new user of CQRLOG would be irritated that some part of the program does not work, and that may cause them to give up using CQRLOG and try something else. I am using CQRLOG Ver 2.5.2 (001).

One additional comment:
After replacing my corrupted cqrlog file in /usr/bin with my original copy from the desktop, the TRX window in CQRLOG showing control of my rig did not communicate with the radio anymore. I traced it to the USB port assignment. It had changed from /dev/ttyUSB1 to /dev/ttyUSB2. That is strange.

All working again. Thanks to you and Wolf for the help and suggestions.

Bob, WG9L

oh1kh
Propagation Window stopped working

HI Bob!

Glad to hear that you got it working!
You can also reinstall cqrlog again. That would also done the same job. Reinstalling does not touch your logs and settings at ~/.config/cqrlog folder.

New firewall settings are counting word Synapse as a spammer and rejects it as "Bad bot access attempt"
Now when this "user agent" string is changed it looks like normal linux browser from the web site view. If it is blocked then there is no use to keep web site open if browsers can not access to it.
If I remember right (could be wrong) cqrlog updates information once in hour so it should not be any reason to block tries out.
But as the Synaptic is a communication library it can, and certainly has been, used for all kinds of programs that may make continued qrm for web site.

This problem has been fixed in latest (source) version: Commits on Oct 4, 2021 "fix for hamlib interface" https://github.com/ok2cqr/cqrlog/commits/master includes the fix.
Synaptic code is also open and it has clearly marked "user agent" that are designed so that user can change this. If this kind of problem continues it is very easy to generate new "user agent" string and add for example users callisgn to it. Then everyone has different "user agent" string that makes filtering a bit harder.

Sometimes Linux has some "windoze properties" with usb devices and physical port and port names are swapped.
For that there are two things that help.
If you have new hamlib (>= 4.0) you can use device name by id. You will find it from /dev/serial/by-id/ folder. That should always be same for same device. I is just quite long. for my IC7300 it is /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03003483-if00-port0
The other way is to create symlink.
It means that every time device is connected linux OS check the name and other parameters of device and they can be used as trigger to create own name for serial port.
The system that handles this is called "udev" You can find instructions how to create it from Google with words "udev symlink usb"
in my linux it is a line:
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60" ,ATTRS{serial}=="IC-7300 03003483", SYMLINK+="icom7300"

in file:

/etc/udev/rules.d/92-persistent-usb.rules

When IC7300 is plugged serial port named /dev/icom7300 appears always. Not depending on what usb socket the plug is pushed.

--
Saku
OH1KH

DO1YHJ
TNX for the quick Fix. Did

TNX for the quick Fix. Did the Job. :-)

73 de Heinz-Juergen DO1YHJ

sp3rxo
sp3rxo's picture
CQRPROP

Hi,
Same story with Martin's cqrprop app https://github.com/ok2cqr/cqrprop. I am using it to display propagation data on my pulpit screen but is not working now.

<p>SlaveckM, SP3RXO</p>

sp3rxo
sp3rxo's picture
*pulpit screen I mean desktop

*pulpit screen I mean desktop screen :)

<p>SlaveckM, SP3RXO</p>

ok2cqr
ok2cqr's picture
CQRPROP

It should work again, I released a new version a few days ago.

73 Petr, OK2CQR

PA1SBM
PA1SBM's picture
when you look at the debug

when you look at the debug log it says:

wrong image format

hope that helps for a fix in future release

greets
Alex
PA1SBM