Your one small log clearly shows a permission denied error. Fix that and
things should clear up.
On Friday, May 24, 2024 at 6:54:11 PM UTC-7 Rich Strle wrote:
It doesn't seem to like the 9.9 Mb Log file...
--
You received this message because you are subscribed to the Google Groups
It doesn't seem to like the 9.9 Mb Log file...
--
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 on
I set debug=2 and restarted weewx. I looked through the log file and didn't
see where the ftp report was running. Would the Ftp process how up in the
log as started?
Grasping at straws I added the ftpgenerator to the skins.conf file. That
didn't do anything productive.
I ran weectl report
Google Groups can be very flaky. I got a notice that your messages were
quarantined, but then when I went to release them, they were gone.
On Fri, May 24, 2024 at 7:23 AM Rich Strle wrote:
> When I try to post a response I keep getting a 'message is to long
> error...' I hope I didn't make a
You should see 'something' related to rsync in your logs unless you
massively messed up your RSYNC section or its location in weewx.conf
For example - I took a clean system and enabled RSYNC then added the
log_failure and log_success lines to make it explicitly log
failure/success..
When I try to post a response I keep getting a 'message is to long
error...' I hope I didn't make a naughty list : )
On Thursday, May 23, 2024 at 6:25:20 PM UTC-5 Tom Keffer wrote:
> There are some bugs in the Python libraries, but as far as I know, they
> only affect FTPS, and you're using a
run the command as user weewx on the weewx box, i hasten to clarify
⊣GE⊢
> On 24 May 2024, at 10:39 PM, Graham Eddy wrote:
>
> on source box running weewx, run $ ssh websvr hostname (where websvr is rsync
> target host)
--
You received this message because you are subscribed to the Google
verify that ssh passwordless login is actually working:
on source box running weewx, run $ ssh websvr hostname (where websvr is rsync
target host)
and you should see it print websvr’s hostname
but it might prompt you interactively to update known_hosts, if they are new
keys...
⊣GE⊢
> On 24 May
I thought that was the problem also, but I believe I have it correct with:
/etc/passwd:
weewx:x:988:984::/var/lib/weewx:/sbin/nologin
[root@weewx weewx]# sudo -u weewx /usr/bin/bash
bash-4.4$ pwd
/var/www/html/weewx
bash-4.4$ cd
bash-4.4$ pwd
/var/lib/weewx
bash-4.4$ ls -la
total 156828
Just did a little more digging. The user is now weewx, with its home directory as /var/lib/weex. You need to put the SSH keys for your rsync server in a subdirectory .ssh under that.Took me a while to find that!Kind regardsGeoff17 Westcroft Road Holsworthy, EX22 6BYPhone: +44 (0)1409
I think I had this problem when I updated to v5. IIRC, the weewx user has
changed, and I needed to put the SSH keys into the home directory for that
user.
HTH
Geoff Cusick
On Friday 24 May 2024 at 12:56:10 UTC+1 Chris Eidem wrote:
> I failed to include it in my snippet. Here is the entire,
Here is the skin.conf file for good measure:
[weewx@weewx Rsync]# pwd
/etc/weewx/skins/Rsync
[weewx@weewx Rsync]# cat skin.conf
###
# Copyright (c) 2012 Will Page
#
# With credit to Tom Keffer
I failed to include it in my snippet. Here is the entire, non-edited RSYNC
section in my weewx.conf:
[[RSYNC]]
# rsync'ing to a webserver is treated as just another report
skin = Rsync
# If you wish to use rsync, you must configure passwordless ssh
using
#
Unless I missed it, I see nothing rsync related in your logfile snippet.
For starters, I think you need "skin = Rsync" in your [[RSYNC]] section.
If you edited weewx.conf be sure to restart weewx afterward so it takes
effect.
Also add "log_failure = true" and "log_success = true" to your
14 matches
Mail list logo
