It seems to me, that the wsprnet.org website is still not under control ...
The only real problem with this is, that nobody knows, as there is no clear announcements from the system administrators, when there is any maintenance work....

However it COULD be different as well:
- At 14h utc I change antenna configuration here according to the wsprdaemon.conf  definition. It is one of the several times per day where changes are made with the different antennas and Kiwism switching ant directions, etc...
- After WD made the changes as specified in wsprdaemon.conf the wsprnet.org website does not accept spots any more.....no spot uploads at all! 

Instead  in of the folders:
home/wsprdaemon/uploads.d/wsprnet.d/spots.d/ON5KQ_JO10os/kiwi-names/
in each kiwi-name lots of .txt files are written - every 2min a txt file...

To my understanding these are the files, which are waiting for upload and which are NOT uploaded... Naturally they do not appear anywhere on VK7JJs website...

Already now there are 30 files written for my spots decoded locally for the last hour, but not accepted by wsprnet,org....building up, and writing and writing .... no uploads at all!
What should I do ??

In the tmp folder I can check the curl log:
/tmp/wsprdaemon/uploads.d/wsprnet.d/curl.log
It confirms the latest upload was accepted an hour ago.... since then nothing was uploaded...

What should I do ? keep it running ??
Will it be possible to upload the spots later on ? However it will be many many many spots...

Does anyone know, if wsprnet.org is 'partly out of service' ??

Is my spot rate of up to 2500 spots/hour I have seen in the past too much somewhere ? Should I disconnect a few antennas, so spot rate becomes lower ?

Do I need to restart the PC and restart WD?
As I said, it is difficult to know, what to do, if there is no information about, what happens at the server side...

Ulli, ON5KQ

Remark:
Unfortunately my infrastructure here is not able to quickly allow on the fly changes so someone can log-in from outside, as other Internet services have to run permanently.
I therefore cannot reconfigure routers as the routers will not store new settings without complete reboot of the system. Another bug of the hardware I found, as it fails to store settings on the fly...
Time to through out such failing hardware, I know.... I am already in the process to purchase necessary replacements.

Error is cleared.
Thank you Stu.

TI4JWC

Try,
sudo apt install python3-numpy

Stu

Rob, "APi repo" ?  Is that something you or I need to work on?

John

--

I finally got a good install of Ubuntu 20.04. I removed all the unnecessary apps that leaves me with 7 G mem.
When installed wsprdaemon I got the error "Package python-numpy has no installation candidate. 

Do I need to install python-numpy ?

Happy new year to everybody...

As I was focused on family matters today, I didn't pay attention to what happened with the wsprdaemon-receivers. This afternoon however I was astonished of rather less spots than usual reported - especially 40m and up was lacking considerably.
At first I thought some problem with the antenna or feed system occurred, however I found a rather unusual error message I have never seen before.

I checked the file
wsprdaemon/uploads.d/wsprnet.d/spots.d/uploads.log

It showed the following message:
-----------------------------------------------------
tr: write error: Broken pipe
tr: write error: Broken pipe
tr: write error
/home/on5kq/wsprdaemon/wsprdaemon.sh: line 3420: echo: write error: Broken pipe
-----------------------------------------------------


I stopped wsprdaemon with
wsprdaemon.sh -z

Note: before stopping wsprdaemon only the first line was showing in the upload.log file.... The next three lines were added after I stopped wsprdaemon

Then I restarted WD again with
wsprdaemon.sh -a
and as result all works normal again now.

However according to Phil's website there was a 90min gap, where there was no upload at all from ON5KQ
Strange also, that there was nothing stored locally on my PC, not yet uploaded, but waiting for upload.

I want to report it, as it might be important to help the system get more robust (wsprnet.org <--> wsprdaemon.org <--> VK7JJs site and others

I have no idea where this problem came from... may be another glitch at wsprnet.org ??

Ulli, ON5KQ

I reinstalled the Ubuntu Full version and all installed. wsprdaemon only needs me to edit the config file.
I will need to clean out all the extra apps and folders to get some space back.
Thanks for the help again.

john

I had instilled the Lite version of Desktop. I will try again tomorrow with the Full version.

Rob I tried that even with the --fix-missing switch but it still failed for some libraries.

--

I installed Ubuntu 20.04 on AtomicPi , added new user wsprdaemon, set the su level, but when I do the git clone https:github.com..........
the command I get the error  git not found.

Ideas for the new Ubuntu?

TI4JWC

Thank you Stu.
The common  passwd root command worked well.
Now I am on to my next problem: I cannot set a static IP4 address. I have used the Preference | Network connections pannels
but the system does not honor my settings. I still have a DHCP assignment. I have posted this issue over on the Atomicpi forum but
I am hoping there are more active users here that might know the magic required. I tried to use the root ID but I get
"mesg: ttyname failed: inappropriate loctl for device".


John TI4JWC

Hi John, That is specific to that board, perhaps see
https://dlidirect.com/community/champ/forums/1778-atomic-pi-user-forum/topics/4873-root-password-is-absolutely-required
73 Stu M0AQY

I would like to use Atomic Pi to run Wsprdaemon. I am having problems getting started.
Atonic Pi comes with Lubuntu 18.04, the current version is 20.04. I have not found any documentation for 18.04.
I have been able to change the startup password. When I try to set a static IP I am asked for the Root password.
I have tried the common I know. null, and Root did not work.  Does anyone know the startup Root PW?


John
TI4JWC

John,

By the sound of things you are well ahead of me with the RSP integration. Still planning to give Openwebsdr a try although I need a second Pi for this really,

In the short term I now have WSJT-X and SDRUNO running on an old laptop, with frequency hopping enabled to pick up a few bands not covered by my Kiwi.  Will try something a bit cleverer in due course, but right now I'm told I need to tidy the garage...

Regards,

          Rob 

                 Rob

After dabling with WSL I decided to see if wsprdaemon would install and run under Win 10 pro VM with Ubuntu 20.04.
The answer is it does install and run but here I did not have great success uploading spots.

Long story short, don't try unless you have a specific reason, or are happy to lose an hour or two.

The issue here was that as I was seeing no spots while it was hitting the CPU hard, to the point of difficulty using Win10, I decided to stop wsprdaemon but it didn't like to stop (usual -z) might just have been CPU but it seemed to lock. In the end I terminated the WSL ubuntu and set it to not run in the background *.

I went back to the other Ubuntu VM but the Kiwi's were showing the wrong IP (the one I just stopped) a few network checks and switch reboots later I realised (*) Win 10 had fired up another WSL instance and even though I had renamed conf file (.c0nf) it was running in the background (cached service?) grabbing the slots before the real Ubuntu could get them. I'm not 100% I didn't have two instances of the same Ubuntu running at once, if that is even possible.

I'm only posting this as a cautionary tale, it does install but the WSL overhead seems to be quite heavy and it is a bit harder to tame.

For someone locked to Windows who wants to try a few wsprdaemon slots on physical Win10 it might be fine, I expect the reporting issue was a network problem which should be fixable.

Merry Christmas to all
Stu

Rob Garth

I am following your lead in the same effort to get my RSP2Pro to work 6 Meters. I installed the version 7 PI image on  a 8G Pi4. I learned the hard way to not use Etcher to build the image. The new image files have a card builder included. Just run the image download file and it does the build to the card. I have the CubicSDR working with my 2Pro. I see that there are Soapy info included in the CubicSDR start up. I also have WSJT-X 2.2.2 installed but have not found a common Rig setting to get linked. I am off to read the CubicSDR manual now. Poor Rob R has had a "Hair-on-Fire week". I am watching rot a new version of wsprdaemon.

John
TI4JWC  N0URE

--

Many Thanks Rob, I will resist the temptation to play with it until then...

BTW, was I right that OpenWebSDR is too different to Kiwi for Wsprdaemon to be able to talk to it as if it were a kiwi?

Regards,
               Rob