wsprdaemon not uploading spots on just one band


Rob Robinett
 

Since the "./wsprdaemon.sh: line 5740: setup_systemctl_deamon: command not found" error didn't appear after your most recent '-a', and you are posting spots, then your setup is OK.
I'm glad you find WD useful.

Rob

On Tue, Mar 1, 2022 at 11:56 AM Chris Wilson <chris@...> wrote:
Apologies again, I am not sure how to anonymize it, do I star out most of the IP address? However, before I waste any more of your valuable time, those  errors were from before my recreating the directory, and after recreating the wsprdaemon directory I only saw the wspdeamon error, and no longer the unbound variable one. Can I stop the daemon and start it again to see if all errors really have now been resolved? If so what command after ./wsprdaemon.sh -z should I make to prove all is now fixed please Rob? Sorry if this is becoming a Linux for Dummies thread... :) Whatever, the spots are now worth all the effort, this is an amazing add on to the Kiwi software :)

--
Best Regards, Chris Wilson  2E0ILY







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


Chris Wilson
 

Apologies again, I am not sure how to anonymize it, do I star out most of the IP address? However, before I waste any more of your valuable time, those errors were from before my recreating the directory, and after recreating the wsprdaemon directory I only saw the wspdeamon error, and no longer the unbound variable one. Can I stop the daemon and start it again to see if all errors really have now been resolved? If so what command after ./wsprdaemon.sh -z should I make to prove all is now fixed please Rob? Sorry if this is becoming a Linux for Dummies thread... :) Whatever, the spots are now worth all the effort, this is an amazing add on to the Kiwi software :)

--
Best Regards, Chris Wilson  2E0ILY


Rob Robinett
 

Hi Chris,

The  "./wsprdaemon.sh: line 5740: setup_systemctl_deamon: command not found" error is a known bug which only prevents WD from starting automatically at server boot time.

But the "/wsprdaemon.sh: line 752: RECEIVER_LIST: unbound variable" error suggests that your config file remains corrupted.  You can post an anonymized version of it it you want me to review it.

73,

Rob  

On Tue, Mar 1, 2022 at 8:00 AM Chris Wilson <chris@...> wrote:
I have it working now, not sure what was wrong, there were spaces, but I added more and still the same error, so I deleted the wsprdaemon directory and loaded afresh. I got an odd log error, that I think,(but appreciate that's dangerous given my lack of Linux knowledge) that there may be a typo somewhere in the code. Anyway I changed deamon to daemon in two places in the wsprdaemon.sh file, and the error went. I am now uploading more spots than I can ever recall, so a great result, and of course thanks for everyone's patient guidance. I have bought a  Lenovo micro PC the same as Rob suggested, and an ssd drive, so can put this rather overly large one back as a spare in due course.

This was the error message:

chris@wsprdaemon:~/wsprdaemon$ ./wsprdaemon.sh -a
wsprdaemon.sh Copyright (C) 2020  Robert S. Robinett
This program comes with ABSOLUTELY NO WARRANTY; for details type './wsprdaemon.sh -h'
This is free software, and you are welcome to redistribute it under certain conditions.  execute'./wsprdaemon.sh -h' for details.
wsprdaemon depends heavily upon the 'wsprd' program and other technologies developed by Joe Taylor K1JT and others, to whom we are grateful.
Goto https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to learn more about WSJT-x

./wsprdaemon.sh: line 752: RECEIVER_LIST: unbound variable
./wsprdaemon.sh: line 5740: setup_systemctl_deamon: command not found
Watchdog daemon with pid '19178' is now running
chris@wsprdaemon:~/wsprdaemon$



--
Best Regards, Chris Wilson  2E0ILY







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


Chris Wilson
 

I have it working now, not sure what was wrong, there were spaces, but I added more and still the same error, so I deleted the wsprdaemon directory and loaded afresh. I got an odd log error, that I think,(but appreciate that's dangerous given my lack of Linux knowledge) that there may be a typo somewhere in the code. Anyway I changed deamon to daemon in two places in the wsprdaemon.sh file, and the error went. I am now uploading more spots than I can ever recall, so a great result, and of course thanks for everyone's patient guidance. I have bought a Lenovo micro PC the same as Rob suggested, and an ssd drive, so can put this rather overly large one back as a spare in due course.

This was the error message:

chris@wsprdaemon:~/wsprdaemon$ ./wsprdaemon.sh -a
wsprdaemon.sh Copyright (C) 2020 Robert S. Robinett
This program comes with ABSOLUTELY NO WARRANTY; for details type './wsprdaemon.sh -h'
This is free software, and you are welcome to redistribute it under certain conditions. execute'./wsprdaemon.sh -h' for details.
wsprdaemon depends heavily upon the 'wsprd' program and other technologies developed by Joe Taylor K1JT and others, to whom we are grateful.
Goto https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to learn more about WSJT-x

./wsprdaemon.sh: line 752: RECEIVER_LIST: unbound variable
./wsprdaemon.sh: line 5740: setup_systemctl_deamon: command not found
Watchdog daemon with pid '19178' is now running
chris@wsprdaemon:~/wsprdaemon$



--
Best Regards, Chris Wilson  2E0ILY


Erwin - PE3ES - F4VTQ
 

I checked on the 9 characters with VK7JJ, Phil told me it was a left over from the old website and he corrected it on the "spot". So no boundary of 9 characters anymore on wspr rocks !

Cheers
Erwin


Rob Robinett
 

It is hard to tell from your email, but it appears that some spaces are missing between fields in your KIWI_0 line.
As the error message says, WD expects 5 space-separated fields on each RECEIVER_LIST line
 
Also, your ID is very long and some spot query sites might have problems with that.  just put /K at the end.

On Mon, Feb 28, 2022 at 3:04 PM Chris Wilson <chris@...> wrote:
OK, nearly there I hope, but maybe due to line wrapping issues copying my wsprdaemon.conf file from the Pi PC to the desktop has gone wrong. I get this error:

hris@wsprdaemon:~/wsprdaemon$ ./wsprdaemon.sh -s
wsprdaemon.sh Copyright (C) 2020  Robert S. Robinett
This program comes with ABSOLUTELY NO WARRANTY; for details type './wsprdaemon.sh -h'
This is free software, and you are welcome to redistribute it under certain conditions.  execute'./wsprdaemon.sh -h' for details.
wsprdaemon depends heavily upon the 'wsprd' program and other technologies developed by Joe Taylor K1JT and others, to whom we are grateful.
Goto https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to learn more about WSJT-x

': not a valid identifierprdaemon.conf: line 3: declare: `
ERROR: configuration file '/home/chris/wsprdaemon/wsprdaemon.conf' contains 'RECEIVER_LIST' which has fewer than the required 5 fields
chris@wsprdaemon:~/wsprdaemon$


This is the line it's complaining about but I cannot see my error, can someone put me straight there please? Thanks.

declare RECEIVER_LIST=(
"KIWI_0 192.168.178.29:8073 2E0ILY/KIWI IO82qv NULL"
)   
### This table defines a schedule of configurations which will be applied by '-j a,all' and thus by the watchdog daemon when it runs '-j a,all' ev ery odd two minutes
### The first field of each entry in the start time for the configuration defined in the following fields
### Start time is in the format HH:MM (e.g 13:15) and by default is in the time zone of the host server unless ',UDT' is appended, e.g '01:30,UDT'
### Following the time are one or more fields of the format 'RECEIVER,BAND'
### If the time of the first entry is not 00:00, then the latest (not necessarily the last) entry will be applied at time 00:00
### So the form of each line is  "START_HH:MM[,UDT]   RECEIVER,BAND... ".  Here are some examples:
declare WSPR_SCHEDULE_simple=(
   "00:00                       KIWI_0,2200 KIWI_0,630 KIWI_0,160 KIWI_0,80 KIWI_0,40 KIWI_0,10 KIWI_0,17"
)
### This array WSPR_SCHEDULE defines the running configuration.  Here we make the simple configuration defined above the active one:
declare WSPR_SCHEDULE=(
"${WSPR_SCHEDULE_simple[@]}"
)

--
Best Regards, Chris Wilson  2E0ILY







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


Chris Wilson
 

OK, nearly there I hope, but maybe due to line wrapping issues copying my wsprdaemon.conf file from the Pi PC to the desktop has gone wrong. I get this error:

hris@wsprdaemon:~/wsprdaemon$ ./wsprdaemon.sh -s
wsprdaemon.sh Copyright (C) 2020 Robert S. Robinett
This program comes with ABSOLUTELY NO WARRANTY; for details type './wsprdaemon.sh -h'
This is free software, and you are welcome to redistribute it under certain conditions. execute'./wsprdaemon.sh -h' for details.
wsprdaemon depends heavily upon the 'wsprd' program and other technologies developed by Joe Taylor K1JT and others, to whom we are grateful.
Goto https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to learn more about WSJT-x

': not a valid identifierprdaemon.conf: line 3: declare: `
ERROR: configuration file '/home/chris/wsprdaemon/wsprdaemon.conf' contains 'RECEIVER_LIST' which has fewer than the required 5 fields
chris@wsprdaemon:~/wsprdaemon$


This is the line it's complaining about but I cannot see my error, can someone put me straight there please? Thanks.

declare RECEIVER_LIST=(
"KIWI_0 192.168.178.29:8073 2E0ILY/KIWI IO82qv NULL"
)
### This table defines a schedule of configurations which will be applied by '-j a,all' and thus by the watchdog daemon when it runs '-j a,all' ev ery odd two minutes
### The first field of each entry in the start time for the configuration defined in the following fields
### Start time is in the format HH:MM (e.g 13:15) and by default is in the time zone of the host server unless ',UDT' is appended, e.g '01:30,UDT'
### Following the time are one or more fields of the format 'RECEIVER,BAND'
### If the time of the first entry is not 00:00, then the latest (not necessarily the last) entry will be applied at time 00:00
### So the form of each line is "START_HH:MM[,UDT] RECEIVER,BAND... ". Here are some examples:
declare WSPR_SCHEDULE_simple=(
"00:00 KIWI_0,2200 KIWI_0,630 KIWI_0,160 KIWI_0,80 KIWI_0,40 KIWI_0,10 KIWI_0,17"
)
### This array WSPR_SCHEDULE defines the running configuration. Here we make the simple configuration defined above the active one:
declare WSPR_SCHEDULE=(
"${WSPR_SCHEDULE_simple[@]}"
)

--
Best Regards, Chris Wilson  2E0ILY


Rob Robinett
 

Hi Chris,

Your i5 with 4 GB RAM is almost certainly an OK platform.  After installing Ubuntu, you will need to enable sharing to support remote access using the realvnc viewer on your PC.  If you want ssh access, install the openssh-server on your server.

Use the Raspberry Pi imager program (or other program) running on your PC to copy to a USB stick or uses another program to write the Ubuntu image file to a CDROM.  Boot your PC to the USB or CDROM and follow the instruction on your PC';s screen

Rob

On Mon, Feb 28, 2022 at 7:30 AM Chris Wilson <chris@...> wrote:
I am 99% sure the spare PC is the same as one I am running for something else, so it's an i5-3470  but not a t suffix. RAM is almost certainly also 4gig, would that do for now Rob? If it will do I am downloading the recommended Ubunto Desktop version as I type, is installing the daemon exactly the same as on a Pi, or different please? Can I run it headless after installing and setting up, using VNC to see it and do any jobs, over the LAN, as I do with the Pi? Thanks Rob.

--
Best Regards, Chris Wilson  2E0ILY







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


Erwin - PE3ES - F4VTQ
 
Edited

Or run it from your wsprdaemon dir with the standard linux approach

./wsprdaemon.sh -a (or -s/ -z whatever you want to do)

I tend to forget that ever so often...

Yes headless would be no problem for that setup, also with Remote Desktop Connection accessible from a Windows machine or xrdp from a Raspberry Pi


Chris Wilson
 

I am 99% sure the spare PC is the same as one I am running for something else, so it's an i5-3470 but not a t suffix. RAM is almost certainly also 4gig, would that do for now Rob? If it will do I am downloading the recommended Ubunto Desktop version as I type, is installing the daemon exactly the same as on a Pi, or different please? Can I run it headless after installing and setting up, using VNC to see it and do any jobs, over the LAN, as I do with the Pi? Thanks Rob.

--
Best Regards, Chris Wilson  2E0ILY


Rob Robinett
 

I think Ubuntu will run fine on a i5 / 4G PC.
The odroid is the next step up from a Pi, but I think it will cost you more than a used Thinkcentre class PC and have less performance although the odroid is almost certainly more power efficient.
The Thinkcentre Tiny consumes 9W at idle and at most 33W when all CPU cores are busy,

On Mon, Feb 28, 2022 at 7:02 AM Chris Wilson <chris@...> wrote:
OK, thanks Rob, I know where to head now, I have a spare i5 machine, I will fire it up and see what version i5 is in it and how much RAM (probably only 4 gig, is that enough? Are there any SFF boards like a pepped up Pi that have enough oomph? Electric prices have gone absolutely crazy and the wife, probably quite rightly, blames "all that junk constantly humming away upstairs" for a lot of each quarterly bill.

I'll check out this spare PC and post the processor and RAM details, if I may, for your critiquing?

--
Best Regards, Chris Wilson  2E0ILY also 2E0ILY/KIWI on wspr net







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


WA2TP - Tom
 

Thank you for the clarification.
Unfortunately, wspr rocks is limited to call signs of 9 characters or less.

On Feb 28, 2022, at 10:02 AM, Chris Wilson <chris@...> wrote:
OK, thanks Rob, I know where to head now, I have a spare i5 machine, I will fire it up and see what version i5 is in it and how much RAM (probably only 4 gig, is that enough? Are there any SFF boards like a pepped up Pi that have enough oomph? Electric prices have gone absolutely crazy and the wife, probably quite rightly, blames "all that junk constantly humming away upstairs" for a lot of each quarterly bill.

I'll check out this spare PC and post the processor and RAM details, if I may, for your critiquing?

--
Best Regards, Chris Wilson 2E0ILY also 2E0ILY/KIWI on wspr net



Chris Wilson
 

OK, thanks Rob, I know where to head now, I have a spare i5 machine, I will fire it up and see what version i5 is in it and how much RAM (probably only 4 gig, is that enough? Are there any SFF boards like a pepped up Pi that have enough oomph? Electric prices have gone absolutely crazy and the wife, probably quite rightly, blames "all that junk constantly humming away upstairs" for a lot of each quarterly bill.

I'll check out this spare PC and post the processor and RAM details, if I may, for your critiquing?

--
Best Regards, Chris Wilson  2E0ILY also 2E0ILY/KIWI on wspr net


Chris Wilson
 

I use 2E0ILY/KIWI for the multi band wsprdaemon uploads from my Kiwi. Plain 2E0ILY is direct from another PC and receiver, as is 2E0ILY/RPIT and 2E0ILY/AFED occasionally, a Red Pitaya and an Afedri on LF only

Thanks for looking though, I should perhaps of made that clear, sorry.

--
Best Regards, Chris Wilson  2E0ILY


Rob Robinett
 

Hi Chris.

To execute WD from a terminal window run:   ~/wsprdaemon/wsprdemon.sh 
Your logs include TIMEOUT lines, so that is definitely your problem.
Almost any i-5 or i-7 computer will be far more powerful than a Pi.  The WD V3.0 servers sun on Ubuntu 20.04 LTS and I test WD client installations on that OS.
It is possible to run WD in an Ubuntu virtual machine on Windows, but part of my goal for WD is for it to run very, very reliably, like a refrigerator, and a virtual machine environment doesn't provide that.
I am using some Lenovo Thinkcentre Tiny M93p at some sites which I purchased used on ebay for $100-200, for example:  




On Mon, Feb 28, 2022 at 3:16 AM Chris Wilson <chris@...> wrote:
Not having much luck with this command, here is what i have been trying, what am I doing wrong here please?

pi@raspberrypi:~ $ wsprdaemon.sh -s
bash: wsprdaemon.sh: command not found
pi@raspberrypi:~ $ sudo wsprdaemon.sh -s
sudo: wsprdaemon.sh: command not found
pi@raspberrypi:~ $ ./wsprdaemon.sh -s
bash: ./wsprdaemon.sh: No such file or directory
pi@raspberrypi:~ $ cd wsprdaemon
pi@raspberrypi:~/wsprdaemon $ wsprdaemon.sh -s
bash: wsprdaemon.sh: command not found
pi@raspberrypi:~/wsprdaemon $ ./wsprdaemon -S
bash: ./wsprdaemon: No such file or directory
pi@raspberrypi:~/wsprdaemon $


CPU usage looks OK from the Pi's Task Manager, it can go 100% for about 8 seconds but comes back down. Spots are still pretty random with many time slots totally empty. As other bands seem OK I don't think it's my (slow) internet connection. Thanks again for the help.

--
Best Regards, Chris Wilson  2E0ILY







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


WA2TP - Tom
 

Hi Chris,

I just did a two week search of your uploaded spots on wspr rocks, and the only spots that I see for any band, have been uploaded by kiwi decoder.

I do not see any WD uploads from 2E0ILY.

When did you say your WD setup stopped working?

Tom
WA2TP

On Feb 28, 2022, at 6:16 AM, Chris Wilson <chris@...> wrote:

Not having much luck with this command, here is what i have been trying, what am I doing wrong here please?

pi@raspberrypi:~ $ wsprdaemon.sh -s
bash: wsprdaemon.sh: command not found
pi@raspberrypi:~ $ sudo wsprdaemon.sh -s
sudo: wsprdaemon.sh: command not found
pi@raspberrypi:~ $ ./wsprdaemon.sh -s
bash: ./wsprdaemon.sh: No such file or directory
pi@raspberrypi:~ $ cd wsprdaemon
pi@raspberrypi:~/wsprdaemon $ wsprdaemon.sh -s
bash: wsprdaemon.sh: command not found
pi@raspberrypi:~/wsprdaemon $ ./wsprdaemon -S
bash: ./wsprdaemon: No such file or directory
pi@raspberrypi:~/wsprdaemon $


CPU usage looks OK from the Pi's Task Manager, it can go 100% for about 8 seconds but comes back down. Spots are still pretty random with many time slots totally empty. As other bands seem OK I don't think it's my (slow) internet connection. Thanks again for the help.

--
Best Regards, Chris Wilson 2E0ILY





Chris Wilson
 

Not having much luck with this command, here is what i have been trying, what am I doing wrong here please?

pi@raspberrypi:~ $ wsprdaemon.sh -s
bash: wsprdaemon.sh: command not found
pi@raspberrypi:~ $ sudo wsprdaemon.sh -s
sudo: wsprdaemon.sh: command not found
pi@raspberrypi:~ $ ./wsprdaemon.sh -s
bash: ./wsprdaemon.sh: No such file or directory
pi@raspberrypi:~ $ cd wsprdaemon
pi@raspberrypi:~/wsprdaemon $ wsprdaemon.sh -s
bash: wsprdaemon.sh: command not found
pi@raspberrypi:~/wsprdaemon $ ./wsprdaemon -S
bash: ./wsprdaemon: No such file or directory
pi@raspberrypi:~/wsprdaemon $


CPU usage looks OK from the Pi's Task Manager, it can go 100% for about 8 seconds but comes back down. Spots are still pretty random with many time slots totally empty. As other bands seem OK I don't think it's my (slow) internet connection. Thanks again for the help.

--
Best Regards, Chris Wilson  2E0ILY


Chris Wilson
 

I'll run the WD command in a bit, when I have finished a couple of jobs. But the overloading sounds like it may well be the issue, however there are long gaps, an hour or more, where NOTHING decodes (or maybe uploads). Could that happen if it was simply overloading? I don't suppose the wsprdaemon will run on a Windows PC will it? If I dedicate a somewhat elderly PC to Linux what's the easiest distro to install and use please? Thanks for all the help, much appreciated.

--
Best Regards, Chris Wilson  2E0ILY


Hans V alphen
 

Hello,

I think I see similar problems in my setup using a RPI3 and during the evening and night it seems to lose many spots.

In the logfile from wsprdaemon I see messages like this:
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0002.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0022.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0026.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0116.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0150.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0202.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0206.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0220.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0238.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0258.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0336.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0342.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0344.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0402.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0410.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0422.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0444.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0450.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0510.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0528.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0540.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0600.wav': No such file or directory
/home/pi/wsprdaemon/wsprdaemon.sh: line 4921: kill: (8145) - No such process
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0616.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0622.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0642.wav': No such file or directory
/home/pi/wsprdaemon/wsprdaemon.sh: line 4921: kill: (22277) - No such process
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0716.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80/220228_0816.wav': No such file or directory
stat: cannot stat '/tmp/wsprdaemon/recording.d/Kiwi_0/80eu/220228_0822.wav': No such file or directory

in the /tmp/wsprdaemon/recording/xxxx/decode.log I see
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165: 26340 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165:  4696 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165:  7651 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165:  9148 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165: 24271 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165:   941 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165:  2352 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165:  3794 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}
/home/pi/wsprdaemon/wsprdaemon.sh: line 2165:  5190 Killed                  timeout ${WSPRD_TIMEOUT_SECS-110} nice ${WSPRD_CMD} -c ${wsprd_cmd_flags} -f ${wspr_decode_capture_freq_mhz} ${wsprd_input_wav_filename} > ${WSPRD_DECODES_FILE}

and also in the log at /tmp/wsprdaemon/recording.d I see:
Sun Feb 27 17:58:42 UTC 2022:   1 overload events (OV) were reported in the last 600 seconds
stat: cannot stat '220227_1758.wav': No such file or directory
stat: cannot stat '220227_1832.wav': No such file or directory
stat: cannot stat '220227_2326.wav': No such file or directory
stat: cannot stat '220227_2344.wav': No such file or directory
stat: cannot stat '220228_0002.wav': No such file or directory
stat: cannot stat '20220228T001000Z_3568600_usb.wav': No such file or directory
stat: cannot stat '220228_0010.wav': No such file or directory
stat: cannot stat '20220228T003600Z_3568600_usb.wav': No such file or directory
stat: cannot stat '220228_0036.wav': No such file or directory
stat: cannot stat '220228_0146.wav': No such file or directory
stat: cannot stat '220228_0538.wav': No such file or directory
stat: cannot stat '20220228T054000Z_3568600_usb.wav': No such file or directory
stat: cannot stat '220228_0540.wav': No such file or directory
stat: cannot stat '220228_0612.wav': No such file or directory
stat: cannot stat '220228_0738.wav': No such file or directory


For me this all looks like the RPI3 is not able to handle the tasks and it's  severe overloaded. At the time of this I was only having a wsprdaemon task for 80 mtr and 80 mtr EU running.
The first day I was running wspdaemon on my system I used 5 bands to decode wspr but that also crashed quite rapidly so that's why I now only used 80 mtr band but this also is not working out.

I was considering use of an RPI4 but first off all these are all sold out and not available for a half year and second I now begin to think that it will not have enough power to handle the wsprdaemon task for all bands which I would like to handle.

Could you please advice me what kind of machine (computer hardware) I should use to get this running,  mny Tnx

73's  Hans DL/PA0EHG

 


Rob Robinett
 
Edited

It is likely that with the recent excellent 40M conditions your server can't decode all the signals on 40M in the 120 seconds of a WSPR cycle.
 
On the desktop of a Pi you can add a 'CPU usage' panel to the task bar at the top of the screen and then watch how busy the CPU is.  It should jump to 100% usage at second 5 of each wspr cycle and then drop down to less than 50% for 10 second or more at the end of each cycle.  If it's 100%, 
 
You can also try adding this line to the top of your wsprdaemon.conf file:

CORRECTION:  I found the Pi 4 at my Maui site was running 100% and so I needed to make this change and found I had mis-typed it.  The correct line to add is:

WSPRD_CMD_FLAGS="-C 500 -o 3 -d"
 
It causes WD to execute the 'wsrpd' decoder with '-o 3' instead of the default '-o 4';  it will find fewer spots but will run faster.
 
Most top spotting sites are now running WD on x86 servers in order to handle their decoding burdens which will only increase with improved propagation as sunspots increase.   
 
 

On Sun, Feb 27, 2022 at 2:41 PM KD2OM <steve@...> wrote:
You might have to enter wsprdaemon.sh -s  My system has a shortcut.
Sorry I forgot that some users might not have that. If you are in the
actual wsprdaemon directory you might need to enter it as ./wsprdaemon.sh -s

Steve

On 2/27/22 22:34, Chris Wilson wrote:
> I am embarrassed to say I am not sure what you are asking me to do. I have used VNC to log on to the remote Pi and opened the Linux equivalent of a dos box command prompt. Typing wd -s gives a command not found, as it does if I enter the wspdaemon directory before typing that. But I don't think this is what you intend me to do at all, sorry.... I am really naive about Linux.
>






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