---------- Forwarded message --------- From: Mark Jessop <notifications@...> Date: Sun, Jan 30, 2022 at 1:15 PM Subject: Re: [rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue

FYI... ---------- Forwarded message --------- From: Mark Jessop <notifications@...> Date: Sun, Jan 30, 2022 at 2:53 AM Subject: [rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue

In the meantime I figured out to change the version wsprdaemon.sh asks for from 2.3.0 to 2.5.4. Seems to be running the new version fine now. .

I don't think WD 2.10k users suffer from that memory leak, perhaps because it uses the file in/out interface to wsprd. There are sites running WD untouched on a 1GB Pi4 for years without OS memory

How does someone upgrade wspr to V2.5?

Regardless of what OS or computer type you run, you should consider updating your wsprd executable to 2.5.x. As of that revision, a memory leak is fixed.

I may be the only one who uses one of those for WD, but just in case there are others... I compiled from source the latest version of wsprd and jt9 and have them running. An easy install and if

A second Raspberry is running the FiFiSDR Audio input devices: **** List of CAPTURE Hardware Devices **** card 1: FiFiSDR [FiFi-SDR], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0:

Well indeed. Edit the conf and rerun the script. E.

I have 2.10k working on my Raspberry Pi Buster It starts the test and finds the Audio Codec But what to do then ? Adjust the input gain and restart test? [-+q] => + amixer: Unable to find simple

This discussion stimulated me to resume WD 3.0 installation testing on my Pi4b running bullseye, but of course I immediately encountered the 'missing qt5' problem. However this thread on the Pi forum

There is an older message here for the same. I tried to solve it differently though as it appears that it is not necessary for wsprdaemon I commented that part out of the install script which seems to

I tried this on a brand new WD install but this does not work with an unmodified .conf file. Catch22 or should I simply do some standard input into the .conf file and run the command

Thanks for information. I am happy that these effects are not coming from an outside attack... I am sorry for the additional work which it causes/caused... regards, Ulli

I have been debugging the WD 3.0 server code and despite all me pre-testing I encountered bugs which caused noise and extended spot losses on the WD2 server which feeds Grafana and wspr.live. I

Hi Ulli, In installing WD 3.0 server on WD I have uncovered a number of problems, among the most worrisome is that a couple of WD client sites (not yours) are repeatedly uploading the same valid

Hello Ulli The problem you describe was an unexpected transient 'side-effect' of a change to new WD 3.0 software on the server. Later today I will see if I can fill the missing data. This was not

Last night from 01:00h to about 03:00h UTC the Grafana page (clickhouse database, wspr.live) doesn't show any noise date Later this night periodically the noisedata is missing for shorter periods of

See the attached clip. What does WD report?

root has no PW until you set it. ssh login is with user=debian pw=serial# until you change serial number. You then use su for root or sudo bash with work also