New computer, can't get pskreporter to work, probably a user error

[RD Powers]

Hi,

I have just installed SparkSDR on a new computer running linux (Debian 11) and while SparkSDR is displaying decoded spots just fine, I am not seeing them on pskreporter.info.  Even worse, if I watch the network with tcpdump 'udp port 4739' I do not see any spots being sent from this PC to pskreporter, yet when I run wsjt-x I do.

I do have the blue checkmark next to 'Psk Reporter' checked.  Is there anything else I should check?  I'm pretty confident it's a user error, I just can't figure out which one.  It did work on my previous system.  

Version is 2.0.33.0 and I also fell back to 2.0.17.0 to see if that fixed it, and it did not.

It's driving me crazy!

Regards,
RDP

[ahop...@googlemail.com]

Hi RDP,

Is there anything in the log files?  I can't think of anything else that has to be set.

73 Alan M0NNB

[RD Powers]

I didn't see anything related to pskreporter either in stdout or the logs under ~/.config/m0nnb/SparkSDR or in /var/log either.

I looked at which files the SparkSDR process had open using 'lsof' and I didn't see a UDP connection for port 4739.

This suggests to me that for some reason it isn't opening the pskreporter connection, rather than it has it open and isn't sending data.

I'll keep trying stuff to see what happens, and maybe even restart the old computer to see if I can learn anything from it.

I don't think it's a firewall issue since wsjt-x is working.

[Sdr Stack]

Use a max of 6 characters in your gridsquare. WSRPNet will toss out reports if you use more than this, I think PSKReporter has a higher limit than 6 but I think there's still a point where it causes it to break.

[ahop...@googlemail.com]

Hi,

just looked through the code, It won't try to upload if either your callsign or locator are blank in the general settings, so that is worth checking. 

73 Alan M0NNB

[Roger David Powers]

Yes, that was not set. 

Now it is working again, which is great.

I don't think I'll forget that setting next time, LOL.  I said it was going to be a user error, and I was right about that at least.

One more thing I learned by watching tcpdump output is that it waits five minutes before writing to pskreporter.info (and then every five minutes thereafter), so one needs to be more patient than wsjtx which writes a lot more frequently (I can check if it matters).

Thanks for the tips!
RDP

--
You received this message because you are subscribed to a topic in the Google Groups "SparkSDR" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sparksdr/K6p8DY_ynIE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sparksdr+u...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/sparksdr/2909d20c-452e-413c-8a9a-f18f00d6ea08n%40googlegroups.com

.

[Ed Stroh]

I'm having this issue myself but both my call and grid square are entered, yet PSKreporter still shows nothing. I've got hundreds of spots but none seem to have been reported. Can someone please help me troubleshoot this?

Running version 2.0.33.0

[Ed Stroh]

Correction: I am seeing some reports on PSKR but far from all of them. Of the nearly 1K spots I've tallied in the last hour only 133 seem to have uploaded. Is this normal? Am I missing something obvious?

[ahop...@googlemail.com]

Hi Ed,

pskreporter ignores spots of the same callsign on a given band if they are closer than 20minutes so I think it is probably ok.  To reduce traffic spark tries not to send anything that pasreporter will filter out.

73 Alan M0NNB

[Ed Stroh]

Hi Alan,

Thanks for explaining. That makes perfect sense. I think I was misinterpreting the total spot count for unique spots rather than individual ones incl. repeats of the same call.