Date
1 - 12 of 12
Wsprdaemon won't run after a reboot
|
My Pi4 (recently upgraded to WD3) was running well until I accidentally shut the power off, and after it restarted it no longer connects to my two Kiwis. I've tried manually restarting using ./wsprdaemon.sh -a, and then when I check the status with the -s command I get error messages about "no running jobs" and several "line 622 printf errors" about invalid numbers.
Guessing there is a corrupted file somewhere from that accidental reboot, but I'm not sure where to start troubleshooting or how to fix it. I did try re-installing WD3, which did not have any impact. I also verified that the Pi4 can connect to both Kiwis using the Chrome browser from it's desktop environment. Any suggestions appreciated. |
|
|
|
WA2TP - Tom
If the aliases are installed try just running wda. Rob had set my test machine to sudo auto wd, which on reboot wd does automatically start.
However on my I9, this does not to appear to work because when I restart that server I still have to manually run wda.
On Jul 10, 2022, at 1:00 PM, Bruce KX4AZ <bruce@...> wrote:
|
|
|
|
WA2TP - Tom
If the aliases are installed try just running wda. Rob had set my test machine to sudo auto wd, which on reboot wd does automatically start.
However on my I9, this does not to appear to work because when I restart that server I still have to manually run wda.
On Jul 10, 2022, at 1:00 PM, Bruce KX4AZ <bruce@...> wrote:
|
|
|
|
John K5MO
Check that the IP addresses to the kiwis didn't get reassigned after the boot.? John K5MO On Sun, Jul 10, 2022 at 2:46 PM WA2TP - Tom <myis300@...> wrote:
|
|
|
|
On Sun, Jul 10, 2022 at 03:15 PM, John K5MO wrote:
The ip addresses are unchanged from what I had in the conf file, and I also opened a Chrome browser on the Pi4 to verify I could connect to both of them via the original ip addresses. I've been combing through the wsprdaemon directory to see if I can locate a log file of some kind that would show an error when trying to start the program. |
|
|
|
On Sun, Jul 10, 2022 at 02:46 PM, WA2TP - Tom wrote:
Tom, Thanks for replying to my post. I'm afraid my inexperience requires me to ask some questions that a typical user would laugh at... I'm not sure what 'aliases' means in this context; I will need to know exactly what I need to type at the command prompt. I tried 'wda', './wda.sh', 'wd -a' ,and './wd.sh -a' so far, all of which yield 'command not found' or 'no such file or directory' errors. I assume there is a log file somewhere that might give a clue as to why the wsprdaemon won't start up when asked to. It does accept the ./wsprdaemon.sh -a command with no complaints, but apparently something goes awry then. Bruce |
|
|
|
Jim Lill
run the command wsprdaemon.sh -A or ws -A not a but A On 7/10/22 13:00, Bruce KX4AZ wrote:
My Pi4 (recently upgraded to WD3) was running well until I accidentally shut the power off, and after it restarted it no longer connects to my two Kiwis. I've tried manually restarting using ./wsprdaemon.sh -a, and then when I check the status with the -s command I get error messages about "no running jobs" and several "line 622 printf errors" about invalid numbers. |
|
|
|
Rob Robinett
To load the aliases which I almost always use, execute: source ~/wsprdaemon/.wd_bash_aliases Then to automatically execute that each time you start a terminal session execute: rci After doing that, these are the aliases I commonly use: wds Display wsprdaemon status wda Start WD running all configured jobs wdz Stop all WD jobs wdle Repeatly scan all the log files and display newly logged error lines wdln Display the log of spots as they are uploaded to wsprnet.org The error and log files have not been prettified for end users, so you may find them perplexing On Sun, Jul 10, 2022 at 12:34 PM Bruce KX4AZ <bruce@...> wrote: On Sun, Jul 10, 2022 at 02:46 PM, WA2TP - Tom wrote: --
|
|
|
|
On Sun, Jul 10, 2022 at 04:20 PM, Rob Robinett wrote:
Thanks Rob - I successfully installed the aliases, though I still can't get wsprdaemon to start up (screenshot attached). Very perplexing since the system was running fine when the power cycle corrupted something. If there is a specific log or error file I should upload just let me know. Or if it would help I could send you the login credentials. |
|
|
|
Rob Robinett
PM me how to login On Sun, Jul 10, 2022 at 1:58 PM Bruce KX4AZ <bruce@...> wrote: On Sun, Jul 10, 2022 at 04:20 PM, Rob Robinett wrote: --
|
|
|
|
Hi Bruce,
I have fixed your problem which was due to several zero length WD status files (e.g. :~/wsprdaemon/watchdog_daemon.pid) which were expected to contain process IDs but had nothing in the file. Since I have never seen such empty .pid files before, my code didn't test for that condition. I guess they were zero length due to a uncontrolled shutdown of your Pi. Your Pi 4B is currently configured to decode 13 channels of only WSPR-2 and that consumes just about all of the Pi's CPU time. So if you want to add more receive channels you will need more CPU (e.g. a second Pi) or to turn down the intensity of 'wsprd's search for spots by adding this line to your conf file: WSPRD_CMD_FLAGS="-C 500 -o 3 -d" It is great to have your excellent receive site back online. Note: You have configured your reporter ID at 'KX4AZ-T', however due to some WD internals your spots are being uploaded as KX4AZ/T. |
|
|
|
Rob,
Can't thank you enough for figuring out exactly what the problem was, and getting the Pi restored to spotting again! I don't anticipate adding any more receive channels, but then again when I started WSPR spotting a few years ago, I never thought I'd end up with two Pis and three KiwiSDRs in two different states. So your information about taming the CPU load may be valuable, indeed. And maybe that would enable some tinkering with the FST4 mode. Bruce |
|
|
