No need to change the user login shell even (*usermod*)... just use the
shell option on *su*.

sudo su - weewx --shell=/usr/bin/bash



On Wed, May 21, 2025 at 12:10 PM vince <vinceska...@gmail.com> wrote:

> I always forget 'sudo su'.  Thanks.
>
> Just tested this on debian12 - the shell needs to be temporarily changed
> from nologin to bash first....
>
> sudo usermod -s /usr/bin/bash weewx              # temporarily change the
> shell to a valid one
> sudo su weewx                                    # now this will work
>
> (do anything requiring running as user weewx)
>
> sudo usermod -s /usr/bin/nologin weewx           # reverse the temporary
> change
>
> On debian12 it was 'not' necessary to set a weewx password.
>
> On Wednesday, May 21, 2025 at 4:18:01 AM UTC-7 matthew wall wrote:
>
>> you can become the weewx user without entering a password:
>>
>> sudo su weewx
>>
>> or you can set a password for the weewx account:
>>
>> sudo passwd weewx
>>
>>
>> > On May 21, 2025, at 01:09, James Barber <jbar...@gmail.com> wrote:
>> >
>> > Thank you so much for a quick reply. I have tried logging in ..... su
>> weewx..... and it asks for a password. This weewx user was created by the
>> apt install so I don't know the password and "weewx" ain't it hah. I
>> searched for the password to no avail :(. I could try making a new user
>> weewx and set my own password ?
>> > --
>> > James Barber, MD
>> > Douglas, GA
>> > Cell: (912) 292-4064
>> >
>> >
>> > On May 21, 2025 12:00:15 AM EDT, 'John Kline' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>> > Steps 6 and 7 need to be performed as user weewx.
>> > The test in step 8 should be performed as user weewx.
>> >
>> > I believe you are correct that this would have just worked had you
>> upgraded from 4.1; but I believe you would be running as root, not pi.
>> >
>> >> On May 20, 2025, at 8:46 PM, James B <jbar...@gmail.com> wrote:
>> >>
>> >> I ran RSYNC with 4.10 with no problems. I've read and re-read the
>> RSYNC docs for 4.10, 5.0, and 5.1
>> >> No success so I really appreciate any help. Ironically it looks like
>> from the 5.0 documentation, if I had upgraded
>> >> from 4.10 rather than a clean 5.1 install, the installer would have
>> kept my user "pi" and not "weewx", and i think i wouldn't
>> >> have these problems. I think my problem is the daemon user is "weewx"
>> and I can't set up permissions for ssh with "weewx".
>> >>
>> >> What I've done so far:
>> >> ___________________________________________________
>> >> 1. made fresh SD card with bookworm
>> >> 2. logged in as user "pi"
>> >> 3. fresh weewx install using apt install
>> >> 4. set up weewx.conf:
>> >> [[RSYNC]]
>> >> enable = true
>> >> server = ZZZ.1and1-data.host
>> >> user = XXX
>> >> path = YYY/
>> >> 5. ps aux | grep "weewx" (shows user weewx running weewxd)
>> >> weewx 6460 1.9 8.8 364336 81720 ? Ssl 12:46 10:30 python3
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> >> 6. ssh-keygen
>> >> 7. ssh-copy-id x...@zzz.1and1-data.host
>> >> 8. ssh'd to remote_server (success)
>> >> 9. rsync'd test files to remote_server (success)
>> >> 10. cp ~/.ssh/*.* /var/lib/weewx/.ssh
>> >> 11. sudo chown weewx:weewx /var/lib/weewx/.ssh/*.*
>> >> -rwxrwx--- 1 weewx weewx 560 May 20 12:23 id_rsa.pub
>> >> -rw------- 1 weewx weewx 364 May 19 22:18 known_hosts
>> >> -rwxrwx--- 1 weewx weewx 142 May 20 12:23 known_hosts.old
>> >> 12. weectl report run RSYNC (WORKS from user pi without error YAY)
>> >> 13. running weewx via systemd, NO JOY. Here's the error message:
>> >> weewxd[6460]: ERROR weeutil.rsyncupload: rsync reported errors.
>> Original command: ['rsync', '--archive', '--stats', '-e', 'ssh',
>> '/var/www/html/weewx/', 'x...@zzz.1and1-data.host:YYY']
>> >> weewxd[6460]: ERROR weeutil.rsyncupload: **** Permission denied,
>> please try again.
>> >> weewxd[6460]: ERROR weeutil.rsyncupload: **** Permission denied,
>> please try again.
>> >> weewxd[6460]: ERROR weeutil.rsyncupload: **** x...@zzz.1and1-data.host:
>> Permission denied (publickey,password).
>> >> weewxd[6460]: ERROR weeutil.rsyncupload: **** rsync: connection
>> unexpectedly closed (0 bytes received so far) [sender]
>> >> weewxd[6460]: ERROR weeutil.rsyncupload: **** rsync error: unexplained
>> error (code 255) at io.c(232) [sender=3.2.7]
>> >>
>> >> From reading the above posts, and looking everywhere i can, i am
>> pretty sure i haven't set up the weewx ssh key properly.
>> >> I can't find a config or .config file in my ~/.ssh directory, but
>> rsync works as user pi, so that doesn't seem to be the problem.
>> >>
>> >> How do I set up ssh for the weewx user? I copied my pi ssh files as
>> instructed above (and as mentioned by vince) but that didn't work.
>> >> Thank you so much for any help.
>> >>
>> >> On Sunday, June 2, 2024 at 11:39:00 AM UTC-4 vince wrote:
>> >> Agree. My error there. I keep forgetting the weewx accounts $HOME for
>> packaged installs is in an odd location. Thanks !
>> >>
>> >> On Sunday, June 2, 2024 at 6:07:15 AM UTC-7 PBudmark wrote:
>> >> As correctly stated in
>> https://groups.google.com/g/weewx-user/c/50VCTyL-Tpw/m/DgScCzIDAQAJ, the
>> home directory for weewx is /var/lib/weewx and not /home/weewx, so .ssh
>> need to go into /var/lib/weewx/.ssh
>> >>
>> >> On Sunday, June 2, 2024 at 4:32:07 AM UTC+1 Ben W. wrote:
>> >> Thanks, Vince!
>> >> I'm pretty sure I saw that link in my results, but the Ubuntu
>> reference resulted in my continue scrolling. I will try your suggestion
>> when I get back home!
>> >>
>> >> On Saturday, June 1, 2024 at 7:59:44 PM UTC-5 vince wrote:
>> >> If you google your exact error "Host key verification failed." and it
>> will return what's going on....
>> >>
>> >>
>> https://askubuntu.com/questions/45679/ssh-connection-problem-with-host-key-verification-failed-error
>> >>
>> >> The weewx-related answer is that you're using old notes that are still
>> expecting the 'root' user on the weewx system to be the local user, which
>> is no longer accurate. In v5 it is the 'weewx' user (upgrade guide link).
>> So it is very likely the host key of the remote computer is not known in
>> the /home/weewx/.ssh/known_hosts file. Simplest way around this would be do
>> append whatever is in your legacy /root/.ssh/known_hosts file to your
>> /home/weewx/.ssh/known_hosts file.
>> >>
>> >> On Saturday, June 1, 2024 at 5:34:36 PM UTC-7 Ben W. wrote:
>> >> Greetings!
>> >> ::
>> >>
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> an email to weewx-user+...@googlegroups.com.
>> >> To view this discussion visit
>> https://groups.google.com/d/msgid/weewx-user/d910463d-ab6a-4158-84fc-5edc1bb6e5e2n%40googlegroups.com.
>>
>> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to weewx-user+...@googlegroups.com.
>> > To view this discussion visit
>> https://groups.google.com/d/msgid/weewx-user/3BC3255B-0B08-4533-B3F3-A3CA86463758%40gmail.com.
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/weewx-user/7cb21a34-4535-4bca-be7e-d84fdad9c0a5n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/7cb21a34-4535-4bca-be7e-d84fdad9c0a5n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/CA%2Bz%2BvD4%3D6dkMm0bh%2BhU97XCaJF8%3Ds6fiPCkNGvN7tSA%2Bhhx9EA%40mail.gmail.com.

Reply via email to