Problem with QRZ and HamQTH

8 posts / 0 new
Last post
DG5BQ
Problem with QRZ and HamQTH

Hello everybody,

I encounter problems when I log several QSOs. After every 3 or 4 QSOs cqrlog stucks for up to 3 minutes with increased cpu usage before letting me continue to do the log. After restart of cqrlog everything starts all over again.
A few days ago I discussed that with Petr and it looked like QRZ.com would be the problem. So I switched to hamQTH and it worked for a while. But today I encouter that problem no matter which service I use.

Does anyone else have that issue with version 2.5.2 on a raspberry pi 4?

I'm now thinking of reverting back to version 2.4 because it worked just fine. Does anyone know how to do that the easy way?

73,
Rico DG5BQ

PS: I installed cqrlog again manually according the discription in https://www.cqrlog.com/node/3124. Now it seems to work fine. Will report if it crashes again.

4x4fd
Qso's Name

Cqrlog does not retrive the name from qrz.com. (98%) of the time Nor from Hamqth

DG5BQ
Pulled up again

I thought I had solved the problem. But I was wrong.
Everything seems to work fine in normal mode. But the problem described above accurs once I switch to „offline“ for logging QSOs made in the past.

Anyone any idea?

oh1kh
Problem with QRZ and HamQTH

Hi Rico!
Few things come into my mind.

Have you pinpointed that the stop is actually caused by qrz/hamqth? Do you have any other windows open? (Dxcluster rbn etc...)
if you open console and give command:

sudo tcpdump -X host Hamqth.com

or use qrz.com instead if you have configured that you can see responses from HamQTH.com when you enter a new call to NewQSO and jump to next field.

See how response is related to your view in Newqso. If something happens on console after a while of waiting and then you NewQSO releases it is a network problem. You should get several packets from HamQTH right after moving away from call column of new qso.
If it hapens so, then no more traffic in console and after a while Newqso releases (without anything happening in console) then it is a problem inside RPi, or cqrlog.

In my PC I see "freezing" sometimes when closing a window (mainly preferences). Then everything stops and if moving a window then it leaves traces that after few seconds clears away and everything works normally. I could imagine this happen also with RPi if it is very busy when writing to SD card.

--
Saku
OH1KH

DG5BQ
Hi Saku,

Hi Saku,

thx for your reply.

I just tested out what you recommended.

I did several logs. Everything worked fine until I started to change my locator on each QSO. (I have to do so because I work as aeronautical mobile)
Again after about 3 logs cqrlog freezed for about 3-4 minutes. Here is what happened in the terminal window: After I hit the TAB key to come from the callsign field to the next one nothing happened in the terminal window. After 3-4 minutes of freeze the data came up in the terminal and cqrlog was released again.

Anything I should try next?

73 de Rico
DG5BQ

oh1kh
Problem with QRZ and HamQTH

HI Rico!

To confirm that I understood ok you first set locator with ctrl+L then enter callsign and move to next field with Tab key. After few calls you do not see this kind of line in tcpdump when you have pressed tab to move away from callsign column ?

15:56:13.188322 IP hamtpad.36992 > hamqth.com.http: Flags [P.], seq 1:206, ack 1, win 502, options [nop,nop,TS val 1792262234 ecr 3366765730], length 205: HTTP: GET /xml.php?id=77d06c4354847571963ba4571249a2b4828bac83&callsign=OH1KH&prg=CQRLOG HTTP/1.0

Here I have logged my own call and this tcp dump is the equest that cqrlog sends to hamqth. In your similar line(s) you will see "callsign=" and the call you have entered.
This tcp packet have some other packets (in my case three) before it as Rpi must find HamQTH.com and open the connection for request.
This happen immediately you move away from callsign field. If no output at all at that point (not a single line) it is some kind of trouble within cqrlog, or Rpi.

I did many tests with random my_locators (different for every qso) but did not get this kind of error with my Fedora 33 PC. I have to prepare my RPi for more testing as it seems to be RPi specific problem.

--
Saku
OH1KH

oh1kh
Problem with QRZ and HamQTH

Sorry Rico!

No luck with my RPi 4. It works flawlessly with the procedure you described.

Do you have a metal case for your RPi? And do you use RPi's internal WiFi?
In that case it may completely loose WiFi connection easily. Metal case drops internal WiFi adapters range to less than half compared with no case at all.

I have weak WiFi at my hamshack and I have to use external USB WiFi adapter (Edup) to get Wifi working. When plugging in that it will produce two wifis both connected to my router. How ever this makes unusable situation as internal Wifi can connect but does not carry traffic properly. That is why it must be disabled (wlan0) to get only USB dongle carried connect that then starts to work very good.

If you do not see any tcpdump packets at all when jumping away from callsign with TAB key it can be possible that your RPi can not reach your WiFi router at that point. Reconnect may then take some time.

So please check your Wifi if you are using it. If you are using wired ethernet then this can not happen.

--
Saku
OH1KH

DG5BQ
One more thing:

One more thing:
While waiting the CPU usage is increased.