Date
1 - 4 of 4
Not starting on reboot sudo password error
|
Installation per greenfield is not restarting after reboot.
I also found that the extended alias commands didn't stick, they are gone after reboot as well. This is what I get when starting wsprdaemon with ./wsprdaemon -a but it does start. [sudo] password for wsprdaemon: sudo: unable to read password: Input/output error 73 Steve KD2OM |
|
|
|
Erwin - PE3ES - F4VTQ
Greenfield in what environment? What OS, what hardware, what version etc. That would help to understand your issue.
What user used, what password set. Erwin |
|
|
|
Rob Robinett
The WS user, in your case "wsprdaemon", needs to have sudo permissions. That is by default the case on Pis, but not so on some Ubuntu distros. To test and fix that, as user "wsprdaemon" run the command 'groups' to see if that user is a member of the sudo group. If sudo is not listed, then as a user with sudo permissions (or as root) run 'usermod -aG sudo wsprdaemon" Then run "wda" to see if WD starts successfully To load the WD aliases: run "source ~/wsprdaemon/.wd_bash_aliases ", then run 'rci' to add that line to your bash startup so the WD aliases are available automatically. To enable WD to be run after each powerup or reboot, run "wd -A" (that is a capital "A") On Mon, Sep 12, 2022 at 8:50 AM KD2OM <steve@...> wrote: Installation per greenfield is not restarting after reboot. --
|
|
|
|
Sorry Erwin.
The installation is on an AtomicPi and is Ubuntu 20.04 LTS. Rob has straightened me out on the alias. I was using the instructions in github which don't quite agree with what actually needs to done. I think the reboot issue is fixed, the wd -A not -a fixed it on two of the APi, I am still working on the third. The password issue is something to do with sudo. My username is wsprdaemon and it does show up in the sudoer group. The AtomicPi has some idiosyncrasies compared to a RaspberryPi but are actually obtainable which Pi's are not. Steve KD2OM |
|
|