1. Topics
  2. Troubleshooting wsprdaemon under Ubuntu with KiwiSDR?

Troubleshooting wsprdaemon under Ubuntu with KiwiSDR?

Frank
 

Rob, thanks very much for the off-list assist. Very happy to have the skimmer running now.


On Wed, Nov 2, 2022 at 04:22 PM, Rob Robinett wrote:
If you don't see spots being uploaded within6 minutes, then you can enable the remote access channel feature of WD and I can look at your installation.  Email me instructions.
 
Rob Robinett
 

Hi Frank,

I haven't updated v2.10 for over a year and Debian/Ubuntu updates last summer have broken a large number of Linux applications, including recent versions of WD 3.0.5.  So it is possible that your 2.10 installation is suffering from the same Linux bug as 3..5 users.  That Linux bug causes the kiwirecorder sessions to fail after a second or less and then WD retries the connection to the Kiwis.

So the first thing I suggest is that you upgrade your WD installation to the latest version by executing:

cd ~/wsprdaemon
./wsprdemon.sh -z
git pull
./wsprdemon.sh -a

You can then watch WD uploading to wsprnet.org by executing:

./wsprdemon.sh -l n

If you don't see spots being uploaded within6 minutes, then you can enable the remote access channel feature of WD and I can look at your installation.  Email me instructions.

73,

Rob



On Wed, Nov 2, 2022 at 1:26 PM Frank <gio@...> wrote:
Earlier this year I set up wsprdaemon under Ubuntu 20.04.4 LTS running on an Intel NUC, receiving WSPR spots from a KiwiSDR. It ran normally for several months, but in the summer I needed to take it down due to antenna issues. Today I attempted to restart it, but I'm not seeing any spots getting to WSPRnet.

The KiwiSDR appears to be running normally, with 12 receivers shown under username wsprdaemon_v2.10.

When I power-on the Intel NUC, I see several ACPI BIOS errors reported. Some are "Could not resolve symbol [\SB.PR00._CPC1], AE_NOT_FOUND", followed by errors of the form "ACPI Error: Aborting method". However, Ubuntu then appears to start normally.

After Ubuntu started the first time, it said there are updates available involving about 600MB of files, and asked if I wanted to proceed. I chose to postpone updates so that I could test whether the configuration worked ok using the last software known to be good.

Running top I see a number of processes listed where user wsprdae+ is running python3, others involving wsprdaemon.sh.

However, when I visit wsprnet.org or wspr.rocks I see no spots for my callsign K6FOD more recent than a number of overnight 630M spots from wsjt-x on a different computer, which ended around 1300 UTC.

Being midday here I suppose it's possible that I'm just not hearing wspr beacons on the higher HF bands, which are the ones with open propagation at this hour. But it seems surprising there's nothing at all there. Can anyone offer suggestions for further troubleshooting at this point?

Thanks,

Frank



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896
Frank
 

Earlier this year I set up wsprdaemon under Ubuntu 20.04.4 LTS running on an Intel NUC, receiving WSPR spots from a KiwiSDR. It ran normally for several months, but in the summer I needed to take it down due to antenna issues. Today I attempted to restart it, but I'm not seeing any spots getting to WSPRnet.

The KiwiSDR appears to be running normally, with 12 receivers shown under username wsprdaemon_v2.10.

When I power-on the Intel NUC, I see several ACPI BIOS errors reported. Some are "Could not resolve symbol [\SB.PR00._CPC1], AE_NOT_FOUND", followed by errors of the form "ACPI Error: Aborting method". However, Ubuntu then appears to start normally.

After Ubuntu started the first time, it said there are updates available involving about 600MB of files, and asked if I wanted to proceed. I chose to postpone updates so that I could test whether the configuration worked ok using the last software known to be good.

Running top I see a number of processes listed where user wsprdae+ is running python3, others involving wsprdaemon.sh.

However, when I visit wsprnet.org or wspr.rocks I see no spots for my callsign K6FOD more recent than a number of overnight 630M spots from wsjt-x on a different computer, which ended around 1300 UTC.

Being midday here I suppose it's possible that I'm just not hearing wspr beacons on the higher HF bands, which are the ones with open propagation at this hour. But it seems surprising there's nothing at all there. Can anyone offer suggestions for further troubleshooting at this point?

Thanks,

Frank
1 - 3 of 3