[weewx-user] Weewx 5.01 ReportThread throws KeyError: 'skin'

[Maarten van der Hoeven]

Hi,

Nut sure this came up after the Weewx 5 upgrade, and it seems to not 
breaking any functionallity, but I want to find out why this is being 
reported (KeyError: 'skin').

Feb  9 08:44:56 weewx weewxd[1051]: Exception in thread ReportThread:
Feb  9 08:44:56 weewx weewxd[1051]: Traceback (most recent call last):
Feb  9 08:44:56 weewx weewxd[1051]:   File 
"/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
Feb  9 08:44:56 weewx weewxd[1051]: self.run()
Feb  9 08:44:56 weewx weewxd[1051]:   File 
"/usr/share/weewx/weewx/reportengine.py", line 194, in run
Feb  9 08:44:56 weewx weewxd[1051]: skin_dict['skin'])) as cwd:
Feb  9 08:44:56 weewx weewxd[1051]:   File 
"/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__
Feb  9 08:44:56 weewx weewxd[1051]: val = dict.__getitem__(self, key)
Feb  9 08:44:56 weewx weewxd[1051]: KeyError: 'skin'


Part of my weewx.conf, debug set to 1:

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Whether to log a successful operation
log_success = True

# Whether to log an unsuccessful operation
log_failure = True

# Each of the following subsections defines a report that will be run.
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
skin = Seasons
enable = true

[[SmartphoneReport]]
# The SmartphoneReport uses the 'Smartphone' skin, and the images 
and
# files are placed in a dedicated subdirectory.
skin = Smartphone
enable = false
HTML_ROOT = /var/www/html/weewx/smartphone

[[MobileReport]]
# The MobileReport uses the 'Mobile' skin, and the images and files
# are placed in a dedicated subdirectory.
skin = Mobile
enable = false
HTML_ROOT = /var/www/html/weewx/mobile

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
skin = Standard
enable = false

-- 
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/7833ec5c-fde8-4832-8920-6fc17ed34ad4n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[vince]

See if https://forums.raspberrypi.com/viewtopic.php?t=345917 helps any for 
your gpio issue.

Again here, what user and group is weewx running as? That user needs 
correct permissions to be able to access your attached hardware. My guess 
is that you need to add the weewx user to the same groups the default pi 
user is in.
On Thursday, February 8, 2024 at 1:57:38 PM UTC-8 Vetti52 wrote:

> After updating to from v5.0.0 to v5-0.1I got this log entry:
> Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Deactivated 
> successfully.
> Feb 05 14:59:07 raspbee systemd[1]: Stopped weewx.service - WeeWX.
> Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Consumed 27min 28.104s 
> CPU time.
> Feb 05 14:59:39 raspbee systemd[1]: Started weewx.service - WeeWX.
> Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: version is 0.6
> Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: Data will be uploaded to 
> https://stations.windy.com/pws/update
> Feb 05 15:00:25 raspbee weewxd[7015]: 2024-02-05 15:00:25 xCreatePipe: 
> Can't set permissions (436) for //.lgd-nfy0, Die Operation ist nicht erlaubt
> Feb 05 15:00:25 raspbee weewxd[7015]: 
> /usr/lib/python3/dist-packages/gpiozero/devices.py:295: PinFactoryFallback: 
> Falling back from lgpio: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
> '.>
> Feb 05 15:00:25 raspbee weewxd[7015]:   warnings.warn(
> Feb 05 15:00:26 raspbee weewxd.py[7015]: historygenerator.py: Generated 5 
> tables in 0.15 seconds
>
> Although since then Weewx runs fine,  I doubt, that everything works ok. 
> After reading this thread, I decided to chown root.weewx for .lgd.nfy0. 
> Hope, that is, what it should be.
> I did my upgrade from v4.10.2 according to the user guide for version 4, 
> thus install weewx, stop it, copy all files and directories back, as listed 
> in the user guide, just edited weewx.conf to match my old configuration 
> and started weewx. However, after detecting the "new" user guide for 
> version 5, I was no longer sure, that this was the proper way. With the 
> latest update to v5.0.1 there is some hope, that at least the permissions 
> are clean now. Except of this one.
> Pierre-Yves schrieb am Donnerstag, 8. Februar 2024 um 11:00:36 UTC+1:
>
>> Thanks a lot, very interesting !
>>
>> Yesterday, as I failed to have weewx 5.1 working properly, I reverted to 
>> 4.10.2.
>>
>> My configuration is very similar :
>> - BME280 sensor
>> - AS3953 lightning sensor
>> - SDR driver
>> - Seasons skin
>> - Belchertown skin
>>
>> I am tempted to give a new try...
>>
>> Pierre-Yves
>>
>> Le jeudi 8 février 2024 à 10:40:18 UTC+1, Mks Mk a écrit :
>>
>>> today tried to update my other raspberry pi to weewx v5.01 and this pi 
>>> is different than the main weather pi that we use:
>>> 1-bme280 sensor.
>>> 2-sdr
>>> 3-weewx-wxobs skin.
>>>
>>>
>>> after the weewx update we did the following:
>>> sudo usermod -aG dialout weewx
>>> sudo usermod -aG plugdev weewx
>>> sudo systemctl restart udev weewx
>>>
>>> but weewx v5.01 failed with following errors:
>>> -PermissionError: [Errno 13] Permission denied: '/dev/i2c-1', this error 
>>> related to bme280 sensor
>>> running this command "sudo usermod -aG i2c weewx" fixed the issue.
>>>
>>> -PermissionError: [Errno 13] Permission denied: 
>>> '/usr/share/php/wxobs_weewx.inc', this error related to weewx-wxobs skin
>>> we are using apache2, doing these changes fixed the issue (thanks to 
>>> *glennmckechnie*)
>>> mkdir /etc/weewx/wxobs-tmp
>>> chown weewx.weewx /etc/weewx/wxobs-tmp
>>> edited skin.conf located in /etc/weewx/skins/wxobs/ and uncommenting 
>>> line #30 and changing include_path = '/tmp' to become include_path = 
>>> '/etc/weewx/wxobs-tmp'
>>>
>>> weewx v5.01 is running ok now on this raspberry pi, hoping the above 
>>> step may help someone during the upgrade to weewx v5.01
>>>
>>> On Wednesday, February 7, 2024 at 7:59:59 PM UTC+3 Tom Keffer wrote:
>>>
 https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user


 On Wed, Feb 7, 2024 at 8:58 AM Tom Keffer  wrote:

> I'll add "plughw" to the troubleshooting section.
>
> -tk
>
> On Wed, Feb 7, 2024 at 8:16 AM Steve Gee  wrote:
>
>> I ended up adding the weewx user to the plughw group which fixed the 
>> problem with rtl_433 not starting:
>>
>> sudo adduser weewx plughw
>> sudo systemctl restart weewx.service
>>
>> On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František Slimařík 
>> wrote:
>>
>>> @Matthew:
>>>
>>> That makes sense yep. Thanks a lot for detailed explanation. I 
>>> cannot change port 80 on my hardware so I will review other options :)
>>>
>>> st 7. 2. 2024 v 8:08 odesílatel matthew wall  
>>> napsal:
>>>
 another option is to put a proxy in front of interceptor.  
 configure interceptor to listen on a high port, say 8080, then run 
 nginx 
 binding to port 80 as a reverse proxy to interceptor, proxying all 
 

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Tom Keffer]

I have no idea what ".lgd-fy0" is, but it should probably be owned by
weewx:weewx.

I'm not sure what "v4 upgrade process" you're referring to. You certainly
did not have to offload any files. Same with the v5 upgrade.

The owner of the weewxd process had changed from "root" to "weewx", but the
configuration file has not changed at all. A V4.10.2 config file can be
used without change in V5.

On Thu, Feb 8, 2024 at 1:57 PM Vetti52  wrote:

> After updating to from v5.0.0 to v5-0.1I got this log entry:
> Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Deactivated
> successfully.
> Feb 05 14:59:07 raspbee systemd[1]: Stopped weewx.service - WeeWX.
> Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Consumed 27min 28.104s
> CPU time.
> Feb 05 14:59:39 raspbee systemd[1]: Started weewx.service - WeeWX.
> Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: version is 0.6
> Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: Data will be uploaded to
> https://stations.windy.com/pws/update
> Feb 05 15:00:25 raspbee weewxd[7015]: 2024-02-05 15:00:25 xCreatePipe:
> Can't set permissions (436) for //.lgd-nfy0, Die Operation ist nicht erlaubt
> Feb 05 15:00:25 raspbee weewxd[7015]:
> /usr/lib/python3/dist-packages/gpiozero/devices.py:295: PinFactoryFallback:
> Falling back from lgpio: [Errno 2] Datei oder Verzeichnis nicht gefunden:
> '.>
> Feb 05 15:00:25 raspbee weewxd[7015]:   warnings.warn(
> Feb 05 15:00:26 raspbee weewxd.py[7015]: historygenerator.py: Generated 5
> tables in 0.15 seconds
>
> Although since then Weewx runs fine,  I doubt, that everything works ok.
> After reading this thread, I decided to chown root.weewx for .lgd.nfy0.
> Hope, that is, what it should be.
> I did my upgrade from v4.10.2 according to the user guide for version 4,
> thus install weewx, stop it, copy all files and directories back, as listed
> in the user guide, just edited weewx.conf to match my old configuration
> and started weewx. However, after detecting the "new" user guide for
> version 5, I was no longer sure, that this was the proper way. With the
> latest update to v5.0.1 there is some hope, that at least the permissions
> are clean now. Except of this one.
> Pierre-Yves schrieb am Donnerstag, 8. Februar 2024 um 11:00:36 UTC+1:
>
>> Thanks a lot, very interesting !
>>
>> Yesterday, as I failed to have weewx 5.1 working properly, I reverted to
>> 4.10.2.
>>
>> My configuration is very similar :
>> - BME280 sensor
>> - AS3953 lightning sensor
>> - SDR driver
>> - Seasons skin
>> - Belchertown skin
>>
>> I am tempted to give a new try...
>>
>> Pierre-Yves
>>
>> Le jeudi 8 février 2024 à 10:40:18 UTC+1, Mks Mk a écrit :
>>
>>> today tried to update my other raspberry pi to weewx v5.01 and this pi
>>> is different than the main weather pi that we use:
>>> 1-bme280 sensor.
>>> 2-sdr
>>> 3-weewx-wxobs skin.
>>>
>>>
>>> after the weewx update we did the following:
>>> sudo usermod -aG dialout weewx
>>> sudo usermod -aG plugdev weewx
>>> sudo systemctl restart udev weewx
>>>
>>> but weewx v5.01 failed with following errors:
>>> -PermissionError: [Errno 13] Permission denied: '/dev/i2c-1', this error
>>> related to bme280 sensor
>>> running this command "sudo usermod -aG i2c weewx" fixed the issue.
>>>
>>> -PermissionError: [Errno 13] Permission denied:
>>> '/usr/share/php/wxobs_weewx.inc', this error related to weewx-wxobs skin
>>> we are using apache2, doing these changes fixed the issue (thanks to
>>> *glennmckechnie*)
>>> mkdir /etc/weewx/wxobs-tmp
>>> chown weewx.weewx /etc/weewx/wxobs-tmp
>>> edited skin.conf located in /etc/weewx/skins/wxobs/ and uncommenting
>>> line #30 and changing include_path = '/tmp' to become include_path =
>>> '/etc/weewx/wxobs-tmp'
>>>
>>> weewx v5.01 is running ok now on this raspberry pi, hoping the above
>>> step may help someone during the upgrade to weewx v5.01
>>>
>>> On Wednesday, February 7, 2024 at 7:59:59 PM UTC+3 Tom Keffer wrote:
>>>
 https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user


 On Wed, Feb 7, 2024 at 8:58 AM Tom Keffer  wrote:

> I'll add "plughw" to the troubleshooting section.
>
> -tk
>
> On Wed, Feb 7, 2024 at 8:16 AM Steve Gee  wrote:
>
>> I ended up adding the weewx user to the plughw group which fixed the
>> problem with rtl_433 not starting:
>>
>> sudo adduser weewx plughw
>> sudo systemctl restart weewx.service
>>
>> On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František Slimařík
>> wrote:
>>
>>> @Matthew:
>>>
>>> That makes sense yep. Thanks a lot for detailed explanation. I
>>> cannot change port 80 on my hardware so I will review other options :)
>>>
>>> st 7. 2. 2024 v 8:08 odesílatel matthew wall 
>>> napsal:
>>>
 another option is to put a proxy in front of interceptor.
 configure interceptor to listen on a high port, say 8080, then run 
 nginx
 binding to port 80 as a reverse proxy to interceptor, 

Re: [weewx-user] Re: dpkg: error processing package weewx (--configure):

[Tom Keffer]

Daniel: slow down and give us a more complete picture of what you're trying
to do. You're mixing upgrade attempts with v4.10 runtime errors with
permission issues.

What are you trying to accomplish? Get v4.10.2 running, or upgrade? Let us
know, then give us a complete overview of what the problem is.



On Thu, Feb 8, 2024 at 7:38 AM Daniel Fourlas  wrote:

>
> Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__:
> Using Python 3.9.2 (default, Feb 28 2021, 17:03:44)
>[GCC 10.2.1 20210110]
> Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__:
> Located at /bin/python3
> Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__:
> Platform Linux-6.1.21-v8+-aarch64-with-glibc2.31
> Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__:
> Locale is 'en_GB.UTF-8'
> Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__:
> Using configuration file /etc/weewx/weewx.conf
> Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__:
> Debug is 0
> Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: PID
> file is /var/run/weewx.pid
> Oct 23 02:21:25 SunSDR-pi4 python3[12427]: weewx[12427] INFO weewx.engine:
> Loading station type Ultimeter (weewx.drivers.ultimeter)
> Oct 23 02:21:25 SunSDR-pi4 python3[12427]: weewx[12427] INFO
> weewx.drivers.ultimeter: Driver version is 0.6
> Oct 23 02:21:25 SunSDR-pi4 python3[12427]: weewx[12427] INFO
> weewx.drivers.ultimeter: Using serial port /dev/ttyUSB0
>
> Daniel Fourlas schrieb am Donnerstag, 8. Februar 2024 um 17:37:23 UTC+2:
>
>> Journal begins at Thu 2022-09-22 06:17:24 EEST, ends at Thu 2024-02-08
>> 17:35:55 EET. --
>> Oct 23 02:19:57 SunSDR-pi4 systemd[1]: Starting LSB: weewx weather
>> system...
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> Initializing weewx version 4.10.2
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> Using Python 3.9.2 (default, Feb 28 2021, 17:03:44)
>>[GCC 10.2.1 20210110]
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> Located at /bin/python3
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> Platform Linux-6.1.21-v8+-aarch64-with-glibc2.31
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> Locale is 'en_GB.UTF-8'
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> Using configuration file /etc/weewx/weewx.conf
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> Debug is 0
>> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__:
>> PID file is /var/run/weewx.pid
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO
>> weewx.engine: Loading station type Ultimeter (weewx.drivers.ultimeter)
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO
>> weewx.drivers.ultimeter: Driver version is 0.6
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO
>> weewx.drivers.ultimeter: Using serial port /dev/ttyUSB0
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__: Caught unrecoverable exception:
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__:   could not convert string to float:
>> '___>
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__:   Traceback (most recent call last):
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__: File "/usr/share/weewx/weewxd", line 148, in main
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__:   engine = weewx.engine.StdEngine(config_dict)
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__: File "/usr/share/weewx/weewx/engine.py", line 84, in
>> __init__
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__:   self.stn_info =
>> weewx.station.StationInfo(self.console, **config_dict['Station'])
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__: File "/usr/share/weewx/weewx/station.py", line 51, in
>> __init__
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__:   self.latitude_f  = float(stn_dict['latitude'])
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__:   ValueError: could not convert string to float:
>> '___>
>> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL
>> __main__:   Exiting.
>> Oct 23 02:19:57 SunSDR-pi4 weewx[11877]: Starting weewx weather system:
>> weewx.
>> Oct 23 02:19:57 SunSDR-pi4 systemd[1]: Started LSB: weewx weather system.
>> Oct 23 02:21:25 SunSDR-pi4 systemd[1]: Stopping LSB: 

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Vetti52]

After updating to from v5.0.0 to v5-0.1I got this log entry:
Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Deactivated successfully.
Feb 05 14:59:07 raspbee systemd[1]: Stopped weewx.service - WeeWX.
Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Consumed 27min 28.104s 
CPU time.
Feb 05 14:59:39 raspbee systemd[1]: Started weewx.service - WeeWX.
Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: version is 0.6
Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: Data will be uploaded to 
https://stations.windy.com/pws/update
Feb 05 15:00:25 raspbee weewxd[7015]: 2024-02-05 15:00:25 xCreatePipe: 
Can't set permissions (436) for //.lgd-nfy0, Die Operation ist nicht erlaubt
Feb 05 15:00:25 raspbee weewxd[7015]: 
/usr/lib/python3/dist-packages/gpiozero/devices.py:295: PinFactoryFallback: 
Falling back from lgpio: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'.>
Feb 05 15:00:25 raspbee weewxd[7015]:   warnings.warn(
Feb 05 15:00:26 raspbee weewxd.py[7015]: historygenerator.py: Generated 5 
tables in 0.15 seconds

Although since then Weewx runs fine,  I doubt, that everything works ok. 
After reading this thread, I decided to chown root.weewx for .lgd.nfy0. 
Hope, that is, what it should be.
I did my upgrade from v4.10.2 according to the user guide for version 4, 
thus install weewx, stop it, copy all files and directories back, as listed 
in the user guide, just edited weewx.conf to match my old configuration and 
started weewx. However, after detecting the "new" user guide for version 5, 
I was no longer sure, that this was the proper way. With the latest update 
to v5.0.1 there is some hope, that at least the permissions are clean now. 
Except of this one.
Pierre-Yves schrieb am Donnerstag, 8. Februar 2024 um 11:00:36 UTC+1:

> Thanks a lot, very interesting !
>
> Yesterday, as I failed to have weewx 5.1 working properly, I reverted to 
> 4.10.2.
>
> My configuration is very similar :
> - BME280 sensor
> - AS3953 lightning sensor
> - SDR driver
> - Seasons skin
> - Belchertown skin
>
> I am tempted to give a new try...
>
> Pierre-Yves
>
> Le jeudi 8 février 2024 à 10:40:18 UTC+1, Mks Mk a écrit :
>
>> today tried to update my other raspberry pi to weewx v5.01 and this pi is 
>> different than the main weather pi that we use:
>> 1-bme280 sensor.
>> 2-sdr
>> 3-weewx-wxobs skin.
>>
>>
>> after the weewx update we did the following:
>> sudo usermod -aG dialout weewx
>> sudo usermod -aG plugdev weewx
>> sudo systemctl restart udev weewx
>>
>> but weewx v5.01 failed with following errors:
>> -PermissionError: [Errno 13] Permission denied: '/dev/i2c-1', this error 
>> related to bme280 sensor
>> running this command "sudo usermod -aG i2c weewx" fixed the issue.
>>
>> -PermissionError: [Errno 13] Permission denied: 
>> '/usr/share/php/wxobs_weewx.inc', this error related to weewx-wxobs skin
>> we are using apache2, doing these changes fixed the issue (thanks to 
>> *glennmckechnie*)
>> mkdir /etc/weewx/wxobs-tmp
>> chown weewx.weewx /etc/weewx/wxobs-tmp
>> edited skin.conf located in /etc/weewx/skins/wxobs/ and uncommenting line 
>> #30 and changing include_path = '/tmp' to become include_path = 
>> '/etc/weewx/wxobs-tmp'
>>
>> weewx v5.01 is running ok now on this raspberry pi, hoping the above step 
>> may help someone during the upgrade to weewx v5.01
>>
>> On Wednesday, February 7, 2024 at 7:59:59 PM UTC+3 Tom Keffer wrote:
>>
>>> https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user
>>>
>>>
>>> On Wed, Feb 7, 2024 at 8:58 AM Tom Keffer  wrote:
>>>
 I'll add "plughw" to the troubleshooting section.

 -tk

 On Wed, Feb 7, 2024 at 8:16 AM Steve Gee  wrote:

> I ended up adding the weewx user to the plughw group which fixed the 
> problem with rtl_433 not starting:
>
> sudo adduser weewx plughw
> sudo systemctl restart weewx.service
>
> On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František Slimařík 
> wrote:
>
>> @Matthew:
>>
>> That makes sense yep. Thanks a lot for detailed explanation. I cannot 
>> change port 80 on my hardware so I will review other options :)
>>
>> st 7. 2. 2024 v 8:08 odesílatel matthew wall  
>> napsal:
>>
>>> another option is to put a proxy in front of interceptor.  configure 
>>> interceptor to listen on a high port, say 8080, then run nginx binding 
>>> to 
>>> port 80 as a reverse proxy to interceptor, proxying all traffic or just 
>>> specific requests.
>>>
>>> m
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in 
>>> the Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/5BuR3BSQfeY/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> 

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

[Tom Keffer]

In most installations, HTML root is /var/www/html/weewx, not /var/www. Make
sure you did not inadvertently change it in weewx.conf.

/var/www/html/weewx should be owned by user "weewx". /var/www, or
/var/www/html will be owned by root.

-tk

On Thu, Feb 8, 2024 at 11:58 AM Dominic Reich  wrote:

> 'neu...@bnjpro.dk' via weewx-user  wrote:
>
> >output of "ls -al /vat/www/rumoclock.dk/web/weewx/" is:
> >total 920
> >drwxrwsr-x 7 web1  client1  4096 feb  8 14:19 .
>
> So as you aint answered which user weewx is running I assume it is
> running as weewx as that would also explain that you cannot create the
> temp files when creating the HTLM output:
>
> > Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:
>    [Errno 13] Permission denied: '/var/www/
> rumoclock.dk/web/weewx/index.html.tmp'
>
> You wrote you did `chown -R weewx: /var/www/rumoclock.dk/web/weewx/`
>  -
> but that directory is still owned by user web1. So either you did not
> run the command or it gets reverted by something else (maybe your
> ispconfig tool).
>
> If that's not the case, maybe another directory on the path is missing
> permissions, you can check that too with this:
>
> ls -ld /vat/www/{,rumoclock.dk/{,web} }
>
> I doubt /var/www will have wrong permissions, but you can check those
> directories as well if everything else looks ok.
>
> Also maybe run `sudo ps ux | grep weewxd` to confirm the daemon runs as
> user weewx - it is, probably.
>
> >drw-r-xr-x 4 root  root 4096 jul 17  2023 ..
> >[snip files...]
> >
> >My weewx output is actually generated and put in the standard output
> folder: /
> >var/www/html/weewx/ All files in here are chmod 644 and chown weewx:weewx.
> >
> >But in order to be shown right in my setup using a open-source
> control-panel
> >called ispconfig, In the working root of my primary homepage I have made a
> >folder called /weewx (hence the /var/www/rumoclock.dk/web/weewx/ with
> the chown
> >of that particular virtual homepage chown client1:web1- That folder is
> >symlinked to the standard output folder. This has worked from version
> 4.10.2 up
> >til 5.0.0, but gives me a hard time in 5.0.1 after the upgrade. I can't
> figure
> >out why.
> >
> >torsdag den 8. februar 2024 kl. 20.10.18 UTC+1 skrev vince:
> >
> >We would need to see "ls -al /var/www/rumoclock.dk/web/weewx/" and
> also
> >tell us what user+group weewx is running as.
> >
> >On Thursday, February 8, 2024 at 5:55:20 AM UTC-8 neu...@bnjpro.dk
> wrote:
> >
> >I was to fast. It did come up with the resent generated html, but
> it
> >will not continue generating new html pages. It made one for the
> time I
> >was at when I did the  chown -R weewx: /var/www/
> rumoclock.dk/web/weewx/
> >
> >
> >Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:
>
> >  PermissionError: [Errno 13] Permission denied: '/var/www/
> >rumoclock.dk/web/weewx/index.html.tmp'
> >Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:
>
> >  Generator terminated
> >
> >--
> >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 the web visit
> https://groups.google.com/d/msgid/
> >weewx-user/ac78ec0e-1723-4858-9c8c-d87cc0a5cfa0n%40googlegroups.com.
>
>
> --
> Be the change that you wish to see in the world.
> - Mahatma Gandhi
>
> --
> 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 the web visit
> https://groups.google.com/d/msgid/weewx-user/%24fczqnfvnz-%24rZXlPtl-%24RmbQX-2024%40odin.oe7drt.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 on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECfEMr32G%2ByNUomT5EP4hRX1WBq1K6BXYS2K%3D-HJz97Fg%40mail.gmail.com.

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

[Dominic Reich]

'neu...@bnjpro.dk' via weewx-user  wrote:


output of "ls -al /vat/www/rumoclock.dk/web/weewx/" is:
total 920
drwxrwsr-x 7 web1  client1  4096 feb  8 14:19 .


So as you aint answered which user weewx is running I assume it is
running as weewx as that would also explain that you cannot create the
temp files when creating the HTLM output:


Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:   
[Errno 13] Permission denied: '/var/www/rumoclock.dk/web/weewx/index.html.tmp'


You wrote you did `chown -R weewx: /var/www/rumoclock.dk/web/weewx/` -
but that directory is still owned by user web1. So either you did not
run the command or it gets reverted by something else (maybe your
ispconfig tool).

If that's not the case, maybe another directory on the path is missing
permissions, you can check that too with this:

ls -ld /vat/www/{,rumoclock.dk/{,web}}

I doubt /var/www will have wrong permissions, but you can check those
directories as well if everything else looks ok.

Also maybe run `sudo ps ux | grep weewxd` to confirm the daemon runs as
user weewx - it is, probably.


drw-r-xr-x 4 root  root     4096 jul 17  2023 ..
[snip files...]

My weewx output is actually generated and put in the standard output folder: /
var/www/html/weewx/ All files in here are chmod 644 and chown weewx:weewx.

But in order to be shown right in my setup using a open-source control-panel
called ispconfig, In the working root of my primary homepage I have made a
folder called /weewx (hence the /var/www/rumoclock.dk/web/weewx/ with the chown
of that particular virtual homepage chown client1:web1- That folder is
symlinked to the standard output folder. This has worked from version 4.10.2 up
til 5.0.0, but gives me a hard time in 5.0.1 after the upgrade. I can't figure
out why.

torsdag den 8. februar 2024 kl. 20.10.18 UTC+1 skrev vince:

   We would need to see "ls -al /var/www/rumoclock.dk/web/weewx/" and also
   tell us what user+group weewx is running as.

   On Thursday, February 8, 2024 at 5:55:20 AM UTC-8 neu...@bnjpro.dk wrote:

   I was to fast. It did come up with the resent generated html, but it
   will not continue generating new html pages. It made one for the time I
   was at when I did the  chown -R weewx: /var/www/rumoclock.dk/web/weewx/


   Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:        
     PermissionError: [Errno 13] Permission denied: '/var/www/
   rumoclock.dk/web/weewx/index.html.tmp'
   Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:        
     Generator terminated

--
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 the web visit https://groups.google.com/d/msgid/
weewx-user/ac78ec0e-1723-4858-9c8c-d87cc0a5cfa0n%40googlegroups.com.



--
Be the change that you wish to see in the world.
- Mahatma Gandhi

--
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/%24fczqnfvnz-%24rZXlPtl-%24RmbQX-2024%40odin.oe7drt.com.

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

['neu...@bnjpro.dk' via weewx-user]

output of "ls -al /vat/www/rumoclock.dk/web/weewx/" is:
total 920
drwxrwsr-x 7 web1  client1  4096 feb  8 14:19 .
drw-r-xr-x 4 root  root 4096 jul 17  2023 ..
drwxrwsr-x 2 weewx weewx4096 mar 12  2023 backgrounds
-rw-r--r-- 1 weewx weewx8760 feb  8 14:19 celestial.html
-rw-rw-r-- 1 weewx weewx7719 feb  8 20:10 daybarometer.png
-rw-rw-r-- 1 weewx weewx8069 mar 12  2023 dayET.png
-rw-rw-r-- 1 weewx weewx7920 feb  8 20:10 dayhumin.png
-rw-rw-r-- 1 weewx weewx7089 feb  8 20:10 dayhum.png
-rw-rw-r-- 1 weewx weewx5807 jul 18  2023 dayinside.png
-rw-rw-r-- 1 weewx weewx5166 jul 18  2023 daypond.png
-rw-rw-r-- 1 weewx weewx5267 jul 18  2023 dayradiation.png
-rw-rw-r-- 1 weewx weewx6892 feb  8 20:10 dayrain.png
-rw-rw-r-- 1 weewx weewx5231 jul 18  2023 dayrx.png
-rw-rw-r-- 1 weewx weewx6406 jul 18  2023 daytempchill.png
-rw-rw-r-- 1 weewx weewx9509 feb  8 20:10 daytempdew.png
-rw-rw-r-- 1 weewx weewx9544 feb  8 20:10 daytempfeel.png
-rw-rw-r-- 1 weewx weewx7454 feb  8 20:10 daytempin.png
-rw-rw-r-- 1 weewx weewx5926 mar 12  2023 dayUV.png
-rw-rw-r-- 1 weewx weewx   18602 mar 12  2023 dayvolt.png
-rw-rw-r-- 1 weewx weewx7930 feb  8 20:10 daywinddir.png
-rw-rw-r-- 1 weewx weewx   10234 feb  8 20:10 daywind.png
-rw-rw-r-- 1 weewx weewx9148 feb  8 20:10 daywindvec.png
-rw-rw-r-- 1 weewx weewx1150 feb  8 15:04 favicon.ico
drwxrwsr-x 2 weewx weewx4096 mar  6  2023 font
-rw-rw-r-- 1 weewx weewx5374 jul 18  2023 grid.css
-rw-r--r-- 1 weewx weewx   26344 feb  8 14:19 index.html
-rw-rw-r-- 1 weewx weewx 647 jul 18  2023 mobile.css
-rw-rw-r-- 1 weewx weewx2450 jul 18  2023 mobile.html
-rw-rw-r-- 1 weewx weewx7159 feb  8 18:04 monthbarometer.png
-rw-rw-r-- 1 weewx weewx7163 mar 12  2023 monthET.png
-rw-rw-r-- 1 weewx weewx   19575 jul 18  2023 month.html
-rw-rw-r-- 1 weewx weewx7421 feb  8 18:04 monthhumin.png
-rw-rw-r-- 1 weewx weewx7562 feb  8 18:04 monthhum.png
-rw-rw-r-- 1 weewx weewx6929 jul 18  2023 monthinside.png
-rw-rw-r-- 1 weewx weewx5157 jul 18  2023 monthpond.png
-rw-rw-r-- 1 weewx weewx5209 jul 18  2023 monthradiation.png
-rw-rw-r-- 1 weewx weewx6728 feb  8 18:04 monthrain.png
-rw-rw-r-- 1 weewx weewx5413 jul 18  2023 monthrx.png
-rw-rw-r-- 1 weewx weewx8876 jul 18  2023 monthtempchill.png
-rw-rw-r-- 1 weewx weewx   10132 feb  8 18:04 monthtempdew.png
-rw-rw-r-- 1 weewx weewx   10409 feb  8 18:04 monthtempfeel.png
-rw-rw-r-- 1 weewx weewx7824 feb  8 18:04 monthtempin.png
-rw-rw-r-- 1 weewx weewx5111 mar 12  2023 monthUV.png
-rw-rw-r-- 1 weewx weewx   13432 mar 12  2023 monthvolt.png
-rw-rw-r-- 1 weewx weewx7849 feb  8 18:04 monthwinddir.png
-rw-rw-r-- 1 weewx weewx   11125 feb  8 18:04 monthwind.png
-rw-rw-r-- 1 weewx weewx9788 feb  8 18:04 monthwindvec.png
drwxrwsr-x 2 weewx weewx4096 feb  8 20:10 NOAA
drwxrwsr-x 2 weewx weewx4096 jul 18  2023 RSS
-rw-r--r-- 1 weewx weewx9001 feb  8 14:19 rss.xml
-rw-rw-r-- 1 weewx weewx5406 feb  8 15:04 seasons.css
-rw-rw-r-- 1 weewx weewx6404 feb  8 15:04 seasons.js
drwxrwsr-x 3 weewx weewx4096 feb  8 20:10 smartphone
-rw-r--r-- 1 weewx weewx   19902 feb  8 14:19 statistics.html
-rw-r--r-- 1 weewx weewx4678 feb  8 14:19 tabular.html
-rw-r--r-- 1 weewx weewx6994 feb  8 14:19 telemetry.html
-rw-rw-r-- 1 weewx weewx6870 feb  8 20:00 weekbarometer.png
-rw-rw-r-- 1 weewx weewx6905 mar 12  2023 weekET.png
-rw-rw-r-- 1 weewx weewx   19450 jul 18  2023 week.html
-rw-rw-r-- 1 weewx weewx6614 feb  8 20:00 weekhumin.png
-rw-rw-r-- 1 weewx weewx8775 feb  8 20:00 weekhum.png
-rw-rw-r-- 1 weewx weewx6981 jul 18  2023 weekinside.png
-rw-rw-r-- 1 weewx weewx4801 jul 18  2023 weekpond.png
-rw-rw-r-- 1 weewx weewx4853 jul 18  2023 weekradiation.png
-rw-rw-r-- 1 weewx weewx6294 feb  8 20:00 weekrain.png
-rw-rw-r-- 1 weewx weewx5056 jul 18  2023 weekrx.png
-rw-rw-r-- 1 weewx weewx6743 jul 18  2023 weektempchill.png
-rw-rw-r-- 1 weewx weewx   10102 feb  8 20:00 weektempdew.png
-rw-rw-r-- 1 weewx weewx   10197 feb  8 20:00 weektempfeel.png
-rw-rw-r-- 1 weewx weewx8526 feb  8 20:00 weektempin.png
-rw-rw-r-- 1 weewx weewx5832 mar 12  2023 weekUV.png
-rw-rw-r-- 1 weewx weewx   16009 mar 12  2023 weekvolt.png
-rw-rw-r-- 1 weewx weewx7304 feb  8 20:00 weekwinddir.png
-rw-rw-r-- 1 weewx weewx   11310 feb  8 20:00 weekwind.png
-rw-rw-r-- 1 weewx weewx9749 feb  8 20:00 weekwindvec.png
-rw-rw-r-- 1 weewx weewx6231 jul 18  2023 weewx.css
-rw-rw-r-- 1 weewx weewx7407 feb  8 00:01 yearbarometer.png
-rw-rw-r-- 1 weewx weewx7187 mar 12  2023 yearET.png
-rw-rw-r-- 1 weewx weewx7697 jul 18  2023 yearhilow.png
-rw-rw-r-- 1 weewx weewx   16516 jul 18  2023 year.html
-rw-rw-r-- 1 weewx weewx7065 feb  8 00:01 yearhumin.png
-rw-rw-r-- 1 weewx weewx8409 feb  8 00:01 yearhum.png
-rw-rw-r-- 1 weewx weewx7102 jul 18  2023 yearinside.png
-rw-rw-r-- 1 weewx 

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

[vince]

We would need to see "ls -al /var/www/rumoclock.dk/web/weewx/" and also 
tell us what user+group weewx is running as.

On Thursday, February 8, 2024 at 5:55:20 AM UTC-8 neu...@bnjpro.dk wrote:

I was to fast. It did come up with the resent generated html, but it will 
not continue generating new html pages. It made one for the time I was at 
when I did the  chown -R weewx: /var/www/rumoclock.dk/web/weewx/

Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:  
 PermissionError: [Errno 13] Permission denied: '/var/www/
rumoclock.dk/web/weewx/index.html.tmp'
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:  
 Generator terminated

-- 
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/b11da884-5629-4f11-9ec0-7bd52323b751n%40googlegroups.com.

[weewx-user] successful update to weewx 5.0.1 for driver WH23xx

['Michael Waldor' via weewx-user]

Today I could successfully update my weewx 4.x installation to the new 
weewx version  5.0.1 on a raspberry pi 4 running OSMC 2024-02 (kodi 20.3).

Don't know why but I had to manually update the weewx gpg key. Otherwise 
apt update failed.

There was one major flaw in using the driver WH23xx - the access onto USB 
connection was refused (to be expected due to the permission changes). 
Sadly WH23xx is no longer officially supported, but the driver from 
weewx-4.x works fine. One has to add one udev rule to grant weewx access. I 
added the file /etc/udev/rules.d/900-weewx-wh23xx.rules containing the 
single line:

SUBSYSTEM=="usb",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="8468",MODE="0664",GROUP="weewx"

BTW, I've seen "private" udev rules wihin /etc/weewx/udev. I assume that 
those rules are only for reference, but not used directly. Of course I've 
used them as a pattern for my solution.

Regarding installation: Before running the update on my target raspberry 
pi4 I tried a "vanilla" installation on another platform -  Suse 
tumbleweed. That, too, failed first. This time the URL of the weewx 
repository was not accessible. I manipulated it to point onto .../suse15. 
As a consequence the validation failed, but I simply ignored that and could 
finally install weewx under tumbleweed. I only wanted to get some files in 
advance before doing the real raspberry installation. I do NOT use weewx 
under tumbleweed.

Regards, Michael

-- 
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/706d5b92-ed91-477e-8c68-091fea0da6f4n%40googlegroups.com.

[weewx-user] Re: dpkg: error processing package weewx (--configure):

[Daniel Fourlas]

Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: 
Using Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
   [GCC 10.2.1 20210110]
Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: 
Located at /bin/python3
Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: 
Platform Linux-6.1.21-v8+-aarch64-with-glibc2.31
Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: 
Locale is 'en_GB.UTF-8'
Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: 
Using configuration file /etc/weewx/weewx.conf
Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: 
Debug is 0
Oct 23 02:21:25 SunSDR-pi4 python3[12424]: weewx[12424] INFO __main__: PID 
file is /var/run/weewx.pid
Oct 23 02:21:25 SunSDR-pi4 python3[12427]: weewx[12427] INFO weewx.engine: 
Loading station type Ultimeter (weewx.drivers.ultimeter)
Oct 23 02:21:25 SunSDR-pi4 python3[12427]: weewx[12427] INFO 
weewx.drivers.ultimeter: Driver version is 0.6
Oct 23 02:21:25 SunSDR-pi4 python3[12427]: weewx[12427] INFO 
weewx.drivers.ultimeter: Using serial port /dev/ttyUSB0

Daniel Fourlas schrieb am Donnerstag, 8. Februar 2024 um 17:37:23 UTC+2:

> Journal begins at Thu 2022-09-22 06:17:24 EEST, ends at Thu 2024-02-08 
> 17:35:55 EET. --
> Oct 23 02:19:57 SunSDR-pi4 systemd[1]: Starting LSB: weewx weather 
> system...
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
> Initializing weewx version 4.10.2
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
> Using Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
>[GCC 10.2.1 20210110]
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
> Located at /bin/python3
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
> Platform Linux-6.1.21-v8+-aarch64-with-glibc2.31
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
> Locale is 'en_GB.UTF-8'
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
> Using configuration file /etc/weewx/weewx.conf
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
> Debug is 0
> Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: PID 
> file is /var/run/weewx.pid
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO weewx.engine: 
> Loading station type Ultimeter (weewx.drivers.ultimeter)
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO 
> weewx.drivers.ultimeter: Driver version is 0.6
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO 
> weewx.drivers.ultimeter: Using serial port /dev/ttyUSB0
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
> Caught unrecoverable exception:
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
>   could not convert string to float: 
> '___>
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
>   Traceback (most recent call last):
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
> File "/usr/share/weewx/weewxd", line 148, in main
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
>   engine = weewx.engine.StdEngine(config_dict)
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 84, in __init__
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
>   self.stn_info = weewx.station.StationInfo(self.console, 
> **config_dict['Station'])
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/station.py", line 51, in __init__
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
>   self.latitude_f  = float(stn_dict['latitude'])
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
>   ValueError: could not convert string to float: 
> '___>
> Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
>   Exiting.
> Oct 23 02:19:57 SunSDR-pi4 weewx[11877]: Starting weewx weather system: 
> weewx.
> Oct 23 02:19:57 SunSDR-pi4 systemd[1]: Started LSB: weewx weather system.
> Oct 23 02:21:25 SunSDR-pi4 systemd[1]: Stopping LSB: weewx weather 
> system...
> Oct 23 02:21:25 SunSDR-pi4 weewx[12401]: Stopping weewx weather system: 
> weewx not running
> Oct 23 02:21:25 SunSDR-pi4 systemd[1]: weewx.service: Succeeded.
> Oct 23 02:21:25 SunSDR-pi4 systemd[1]: Stopped LSB: weewx weather system.
>
>
> Daniel Fourlas schrieb am Donnerstag, 8. Februar 2024 um 17:29:16 UTC+2:
>
>> Many Tnx for the info, now i fid this!
>>
>> Now give a unique URL for the 

[weewx-user] Re: dpkg: error processing package weewx (--configure):

[Daniel Fourlas]

Journal begins at Thu 2022-09-22 06:17:24 EEST, ends at Thu 2024-02-08 
17:35:55 EET. --
Oct 23 02:19:57 SunSDR-pi4 systemd[1]: Starting LSB: weewx weather system...
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
Initializing weewx version 4.10.2
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
Using Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
   [GCC 10.2.1 20210110]
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
Located at /bin/python3
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
Platform Linux-6.1.21-v8+-aarch64-with-glibc2.31
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
Locale is 'en_GB.UTF-8'
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
Using configuration file /etc/weewx/weewx.conf
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: 
Debug is 0
Oct 23 02:19:57 SunSDR-pi4 python3[11888]: weewx[11888] INFO __main__: PID 
file is /var/run/weewx.pid
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO weewx.engine: 
Loading station type Ultimeter (weewx.drivers.ultimeter)
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO 
weewx.drivers.ultimeter: Driver version is 0.6
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] INFO 
weewx.drivers.ultimeter: Using serial port /dev/ttyUSB0
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
Caught unrecoverable exception:
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
  could not convert string to float: 
'___>
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
  Traceback (most recent call last):
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
File "/usr/share/weewx/weewxd", line 148, in main
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
  engine = weewx.engine.StdEngine(config_dict)
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine.py", line 84, in __init__
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
  self.stn_info = weewx.station.StationInfo(self.console, 
**config_dict['Station'])
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
File "/usr/share/weewx/weewx/station.py", line 51, in __init__
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
  self.latitude_f  = float(stn_dict['latitude'])
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
  ValueError: could not convert string to float: 
'___>
Oct 23 02:19:57 SunSDR-pi4 python3[11891]: weewx[11891] CRITICAL __main__: 
  Exiting.
Oct 23 02:19:57 SunSDR-pi4 weewx[11877]: Starting weewx weather system: 
weewx.
Oct 23 02:19:57 SunSDR-pi4 systemd[1]: Started LSB: weewx weather system.
Oct 23 02:21:25 SunSDR-pi4 systemd[1]: Stopping LSB: weewx weather system...
Oct 23 02:21:25 SunSDR-pi4 weewx[12401]: Stopping weewx weather system: 
weewx not running
Oct 23 02:21:25 SunSDR-pi4 systemd[1]: weewx.service: Succeeded.
Oct 23 02:21:25 SunSDR-pi4 systemd[1]: Stopped LSB: weewx weather system.


Daniel Fourlas schrieb am Donnerstag, 8. Februar 2024 um 17:29:16 UTC+2:

> Many Tnx for the info, now i fid this!
>
> Now give a unique URL for the station. A Weather Underground 
> URL such as https://www.wunderground.com/dashboard/pws/KORPORT12 will do.
> Unique URL: https://stationsweb.awekas.at/index.php?id=34255
> Saving configuration file /etc/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/shutil.py", line 806, in move
> os.rename(src, real_dst)
> PermissionError: [Errno 13] Permission denied: '/etc/weewx/weewx.conf' -> 
> '/etc/weewx/weewx.conf.20240208172027'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/station_cmd.py", line 311, in 
> reconfigure_station
> weectllib.station_actions.station_reconfigure(config_dict=config_dict,
>   File "/usr/share/weewx/weectllib/station_actions.py", line 183, in 
> station_reconfigure
> backup_path = weecfg.save(config_dict, config_dict['config_path'], not 
> no_backup)
>   File "/usr/share/weewx/weecfg/__init__.py", line 224, in save
> backup_path = weeutil.weeutil.move_with_timestamp(config_path)
>   File 

[weewx-user] Re: dpkg: error processing package weewx (--configure):

[Daniel Fourlas]

Many Tnx for the info, now i fid this!

Now give a unique URL for the station. A Weather Underground 
URL such as https://www.wunderground.com/dashboard/pws/KORPORT12 will do.
Unique URL: https://stationsweb.awekas.at/index.php?id=34255
Saving configuration file /etc/weewx/weewx.conf
Traceback (most recent call last):
  File "/usr/lib/python3.9/shutil.py", line 806, in move
os.rename(src, real_dst)
PermissionError: [Errno 13] Permission denied: '/etc/weewx/weewx.conf' -> 
'/etc/weewx/weewx.conf.20240208172027'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/weewx/weectl.py", line 74, in 
main()
  File "/usr/share/weewx/weectl.py", line 66, in main
namespace.func(namespace)
  File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File "/usr/share/weewx/weectllib/station_cmd.py", line 311, in 
reconfigure_station
weectllib.station_actions.station_reconfigure(config_dict=config_dict,
  File "/usr/share/weewx/weectllib/station_actions.py", line 183, in 
station_reconfigure
backup_path = weecfg.save(config_dict, config_dict['config_path'], not 
no_backup)
  File "/usr/share/weewx/weecfg/__init__.py", line 224, in save
backup_path = weeutil.weeutil.move_with_timestamp(config_path)
  File "/usr/share/weewx/weeutil/weeutil.py", line 1697, in 
move_with_timestamp
shutil.move(path, newpath)
  File "/usr/lib/python3.9/shutil.py", line 820, in move
copy_function(src, real_dst)
  File "/usr/lib/python3.9/shutil.py", line 435, in copy2
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.9/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
PermissionError: [Errno 13] Permission denied: 
'/etc/weewx/weewx.conf.20240208172027'

vince schrieb am Mittwoch, 7. Februar 2024 um 22:29:26 UTC+2:

> Another terribly bad problem report.  Please read 
> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user for how 
> to provide enough information for people to try to help
>
> But given your minimal information
>
> Why did you answer yes for installing weewx if it was already there and 
> installed ?
>
> Suggest you try 'sudo apt-get update' and then 'sudo apt-get upgrade' if 
> you are trying to upgrade from initial 5.0.0 to the latest revision...
>
> On Wednesday, February 7, 2024 at 12:20:46 PM UTC-8 Daniel Fourlas wrote:
>
>>
>> pi@SunSDR-pi4:~ $ sudo apt-get install weewx
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> weewx is already the newest version (5.0.0-1).
>> 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
>> 1 not fully installed or removed.
>> After this operation, 0 B of additional disk space will be used.
>> Do you want to continue? [Y/n] y
>> Setting up weewx (5.0.0-1) ...
>> Using root:root as user:group
>> Using debconf configuration values from previous install
>> usage: weectl.py -v|--version
>>weectl.py -h|--help
>>weectl.py database --help
>>weectl.py debug --help
>>weectl.py device --help
>>weectl.py extension --help
>>weectl.py import --help
>>weectl.py report --help
>>weectl.py station --help
>> weectl.py: error: unrecognized arguments: ¦ ¦
>> dpkg: error processing package weewx (--configure):
>>  installed weewx package post-installation script subprocess returned 
>> error exit status 2
>> Errors were encountered while processing:
>>  weewx
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>

-- 
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/90760d5f-3fdb-4c43-816e-bc5cbae4ca15n%40googlegroups.com.

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

['neu...@bnjpro.dk' via weewx-user]

I was to fast. It did come up with the resent generated html, but it will 
not continue generating new html pages. It made one for the time I was at 
when I did the  chown -R weewx: /var/www/rumoclock.dk/web/weewx/

Syslog:

Feb  8 14:54:15 frej weewxd[754]: INFO weewx.restx: Wunderground-PWS: 
Published record 2024-02-08 14:50:00 CET (1707400200)
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:  
 [Errno 13] Permission denied: 
'/var/www/rumoclock.dk/web/weewx/index.html.tmp'
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:  
 Traceback (most recent call last):
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/reportengine.py", line 220, in run
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
   obj.start()
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/reportengine.py", line 409, in start
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
   self.run()
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
Feb  8 14:54:16 frej weewxd[754]: Traceback (most recent call last):
Feb  8 14:54:16 frej weewxd[754]:   File 
"/usr/share/weewx/weewx/reportengine.py", line 220, in run
Feb  8 14:54:16 frej weewxd[754]: obj.start()
Feb  8 14:54:16 frej weewxd[754]:   File 
"/usr/share/weewx/weewx/reportengine.py", line 409, in start
Feb  8 14:54:16 frej weewxd[754]: self.run()
Feb  8 14:54:16 frej weewxd[754]:   File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
Feb  8 14:54:16 frej weewxd[754]: ngen = 
self.generate(gen_dict[section_name], section_name, self.gen_ts)
Feb  8 14:54:16 frej weewxd[754]:   File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
Feb  8 14:54:16 frej weewxd[754]: ngen += 
self.generate(section[subsection], subsection, gen_ts)
Feb  8 14:54:16 frej weewxd[754]:   File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
Feb  8 14:54:16 frej weewxd[754]: ngen += 
self.generate(section[subsection], subsection, gen_ts)
Feb  8 14:54:16 frej weewxd[754]:   File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 371, in generate
Feb  8 14:54:16 frej weewxd[754]: with open(tmpname, mode='wb') as fd:
Feb  8 14:54:16 frej weewxd[754]: PermissionError: [Errno 13] Permission 
denied: '/var/www/rumoclock.dk/web/weewx/index.html.tmp'
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
   ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts)
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
   ngen += self.generate(section[subsection], subsection, gen_ts)
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
   ngen += self.generate(section[subsection], subsection, gen_ts)
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 371, in generate
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:    
   with open(tmpname, mode='wb') as fd:
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:  
 PermissionError: [Errno 13] Permission denied: 
'/var/www/rumoclock.dk/web/weewx/index.html.tmp'
Feb  8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:  
 Generator terminated
Feb  8 14:54:16 frej weewxd[754]: DEBUG weewx.manager: Daily summary 
version is 4.0
Feb  8 14:54:17 frej weewxd[754]: INFO weewx.imagegenerator: Generated 10 
images for report SeasonsReport in 0.65 seconds
Feb  8 14:54:17 frej weewxd[754]: INFO weewx.reportengine: Copied 0 files 
to /var/www/rumoclock.dk/web/weewx
Feb  8 14:54:17 frej weewxd[754]: DEBUG weewx.reportengine: Running report 
'SmartphoneReport'
Feb  8 14:54:17 frej weewxd[754]: DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
'SmartphoneReport'
Feb  8 14:54:17 frej weewxd[754]: DEBUG weewx.reportengine: Running 
generators for report 'SmartphoneReport' in directory 
'/etc/weewx/skins/Smartphone'
Feb  8 14:54:17 frej weewxd[754]: DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

['neu...@bnjpro.dk' via weewx-user]

Thanks John

It didn't work at first, because I symlink to the actual place it is 
located. But when I changed the chown for the symlink, it worked right 
away. :-)

Cheers
Bent

torsdag den 8. februar 2024 kl. 11.12.27 UTC+1 skrev John Smith:

> chown -R weewx: '/var/www/rumoclock.dk/web/weewx/
>
> On Thu, 8 Feb 2024 at 18:56, 'neu...@bnjpro.dk' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I did a normal apt update, apt upgrade. But after having been running 
>> perfectly with 5.0.0 I now don't get html renewal.
>> I have here a snippet of the logfile indicating a few errors, of which I 
>> think the permission error is the worst, and the one causing the problem. 
>> But I don't see any file of that name in the claimed directory.
>>
>> I do not update the conf files, because they work just fine and I don't 
>> want to use time to reconfigure all over again everytime there is an 
>> upgrade. And they worked fine with version 5.0.0, so no need to.
>>
>> Any ideas on what is happening?
>>
>>
>> Log snippet:
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'weewx.cheetahgenerator.CheetahGenerator'
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  [Errno 13] Permission denied: '/var/www/
>> rumoclock.dk/web/weewx/index.html.tmp'
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  Traceback (most recent call last):
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>File "/usr/share/weewx/weewx/reportengine.py", line 220, in run
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  obj.start()
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>File "/usr/share/weewx/weewx/reportengine.py", line 409, in start
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  self.run()
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts)
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  ngen += self.generate(section[subsection], subsection, gen_ts)
>> Feb  8 08:33:00 frej weewxd[754]: Traceback (most recent call last):
>> Feb  8 08:33:00 frej weewxd[754]:   File 
>> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
>> Feb  8 08:33:00 frej weewxd[754]: obj.start()
>> Feb  8 08:33:00 frej weewxd[754]:   File 
>> "/usr/share/weewx/weewx/reportengine.py", line 409, in start
>> Feb  8 08:33:00 frej weewxd[754]: self.run()
>> Feb  8 08:33:00 frej weewxd[754]:   File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
>> Feb  8 08:33:00 frej weewxd[754]: ngen = 
>> self.generate(gen_dict[section_name], section_name, self.gen_ts)
>> Feb  8 08:33:00 frej weewxd[754]:   File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
>> Feb  8 08:33:00 frej weewxd[754]: ngen += 
>> self.generate(section[subsection], subsection, gen_ts)
>> Feb  8 08:33:00 frej weewxd[754]:   File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
>> Feb  8 08:33:00 frej weewxd[754]: ngen += 
>> self.generate(section[subsection], subsection, gen_ts)
>> Feb  8 08:33:00 frej weewxd[754]:   File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 371, in generate
>> Feb  8 08:33:00 frej weewxd[754]: with open(tmpname, mode='wb') as fd:
>> Feb  8 08:33:00 frej weewxd[754]: PermissionError: [Errno 13] Permission 
>> denied: '/var/www/rumoclock.dk/web/weewx/index.html.tmp'
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  ngen += self.generate(section[subsection], subsection, gen_ts)
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 371, in generate
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  with open(tmpname, mode='wb') as fd:
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  PermissionError: [Errno 13] Permission denied: '/var/www/
>> rumoclock.dk/web/weewx/index.html.tmp'
>> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine:  
>>  Generator terminated
>> Feb  8 08:33:00 frej weewxd[754]: DEBUG weewx.manager: Daily summary 
>> version is 4.0
>> Feb  8 08:33:00 frej weewxd[754]: INFO weewx.imagegenerator: 

Re: [weewx-user] Re: rsync: host key verification failed - problem

[Mario Wesolek]

some problem.. weewx homedir is /var/lib/weewx ... copy the hostkey and 
config file to /var/lib/weewx/.ssh and chown it to weewx:weewx

Kalju schrieb am Donnerstag, 8. Februar 2024 um 11:22:46 UTC+1:

> Hi Dominic!
>
> Thanks for the tip. Indeed, the user was changed from *root* to *weewx*
> That solved the issue
> Thanks!
>
> On Thursday, February 8, 2024 at 11:49:48 AM UTC+2 Dominic Reich wrote:
>
>> Kalju  wrote: 
>>
>> >Hi all, 
>> > 
>> >Facing same issue with ERROR weeutil.rsyncupload:  Host key 
>> verification 
>> >failed error.  
>> >However, it's really strange... 
>> >I can ssh to remote site as both root as well as pi user 
>> >I can do manual rsync with no problems but weewx builtin rsync returns 
>> above 
>> >error 
>> >At the moment my weewx installation is syncing using cron with no 
>> problems but 
>> >I want to understand why builtin rsync fails 
>> >Problem started after upgrade from weewx 5.0.0 to 5.0.1 
>> > 
>> >Any ideas? 
>>
>> Adding the debug info should output the actual rsync command initiated by 
>> weewx to the logs. That's what I assume when looking at line 104 in 
>> `src/weeutil/rsyncupload.py` from the sources of 5.0.1. 
>>
>> Maybe that gives a clue in which the actual rsync commands differ and 
>> why it might fail within Weewx. 
>>
>> Somewhere around 5.0.1 or 5.1.x the user got switched to weewx (not root 
>> anymore) so maybe there is a problem? (I can't remember when the switch 
>> was (it was mentioned on the list somwhere) and haven't found it in the 
>> docs yet) 
>>
>> I'd always suggest looking as what weewx is running so you may not have 
>> to play the guessing game on which user to look at. 
>>
>> sudo ps ux | grep weewxd 
>>
>> should return the user that actually runs the (python) daemon like on my 
>> old Raspberry this runs still as root with 4.10.2. 
>>
>> root 690 2.8 1.5 647360 60428 ? Sl Feb06 75:38 python3 
>> /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid 
>> /etc/weewx/weewx.conf 
>>
>> As it was a package-installation I never messed with it, though I 
>> welcome the change to a non-root package installation per default :) 
>>
>> In case host keys have changed on the server a deletion of the 
>> known_hosts 
>> file within ~/.ssh could also help, probably. 
>>
>> -dominic 
>>
>> >Thank you forward :-) 
>> >On Friday, July 21, 2023 at 1:14:24 PM UTC+3 Tomasz Lewicki wrote: 
>> > 
>> > Thank you for replies. 
>> > 
>> > @Warren Gill: yes, I was thinking about crontab but wanted to use 
>> built-in 
>> > solution. Of course crontab is good as backup solution. 
>> > 
>> > @vince: you're right, I didn't think about it from this side. Just for 
>> > record for future seekers: 
>> > 
>> > 1. I logged as root ('sudo -i' from 'pi' account) 
>> > 2. generated SSH keys ('ssh-keygen') 
>> > 3. copied them to external server ('ssh-copy-id 
>> ace...@external.domain.com 
>> > -p 222') 
>> > 4. copied /home/pi/.ssh/config to /root/.ssh/config 
>> > 5. changed owner of 'config' ('chown root:root /root/.ssh/config') 
>> > 6. waited for next synchronization 
>> > 7. smiled because everything worked as expected :) 
>> > 
>>
>> -- 
>> Educating the mind without educating the heart is no education at all. 
>> - Aristotle 
>>
>

-- 
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/619884db-8d65-4b83-a462-f46a923f7776n%40googlegroups.com.

Re: [weewx-user] Re: rsync: host key verification failed - problem

[Kalju]

Hi Dominic!

Thanks for the tip. Indeed, the user was changed from *root* to *weewx*
That solved the issue
Thanks!

On Thursday, February 8, 2024 at 11:49:48 AM UTC+2 Dominic Reich wrote:

> Kalju  wrote:
>
> >Hi all,
> >
> >Facing same issue with ERROR weeutil.rsyncupload:  Host key 
> verification
> >failed error. 
> >However, it's really strange...
> >I can ssh to remote site as both root as well as pi user
> >I can do manual rsync with no problems but weewx builtin rsync returns 
> above
> >error
> >At the moment my weewx installation is syncing using cron with no 
> problems but
> >I want to understand why builtin rsync fails
> >Problem started after upgrade from weewx 5.0.0 to 5.0.1
> >
> >Any ideas?
>
> Adding the debug info should output the actual rsync command initiated by
> weewx to the logs. That's what I assume when looking at line 104 in
> `src/weeutil/rsyncupload.py` from the sources of 5.0.1.
>
> Maybe that gives a clue in which the actual rsync commands differ and
> why it might fail within Weewx.
>
> Somewhere around 5.0.1 or 5.1.x the user got switched to weewx (not root
> anymore) so maybe there is a problem? (I can't remember when the switch
> was (it was mentioned on the list somwhere) and haven't found it in the
> docs yet)
>
> I'd always suggest looking as what weewx is running so you may not have
> to play the guessing game on which user to look at.
>
> sudo ps ux | grep weewxd
>
> should return the user that actually runs the (python) daemon like on my
> old Raspberry this runs still as root with 4.10.2.
>
> root 690 2.8 1.5 647360 60428 ? Sl Feb06 75:38 python3 
> /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid 
> /etc/weewx/weewx.conf
>
> As it was a package-installation I never messed with it, though I
> welcome the change to a non-root package installation per default :)
>
> In case host keys have changed on the server a deletion of the known_hosts
> file within ~/.ssh could also help, probably.
>
> -dominic
>
> >Thank you forward :-)
> >On Friday, July 21, 2023 at 1:14:24 PM UTC+3 Tomasz Lewicki wrote:
> >
> > Thank you for replies.
> >
> > @Warren Gill: yes, I was thinking about crontab but wanted to use 
> built-in
> > solution. Of course crontab is good as backup solution.
> >
> > @vince: you're right, I didn't think about it from this side. Just for
> > record for future seekers:
> >
> > 1. I logged as root ('sudo -i' from 'pi' account)
> > 2. generated SSH keys ('ssh-keygen')
> > 3. copied them to external server ('ssh-copy-id 
> ace...@external.domain.com
> > -p 222')
> > 4. copied /home/pi/.ssh/config to /root/.ssh/config
> > 5. changed owner of 'config' ('chown root:root /root/.ssh/config')
> > 6. waited for next synchronization
> > 7. smiled because everything worked as expected :)
> >
>
> -- 
> Educating the mind without educating the heart is no education at all.
> - Aristotle
>

-- 
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/2c276b90-5b2b-431d-b7ce-16d185f1d672n%40googlegroups.com.

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

[John Smith]

chown -R weewx: '/var/www/rumoclock.dk/web/weewx/

On Thu, 8 Feb 2024 at 18:56, 'neu...@bnjpro.dk' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I did a normal apt update, apt upgrade. But after having been running
> perfectly with 5.0.0 I now don't get html renewal.
> I have here a snippet of the logfile indicating a few errors, of which I
> think the permission error is the worst, and the one causing the problem.
> But I don't see any file of that name in the claimed directory.
>
> I do not update the conf files, because they work just fine and I don't
> want to use time to reconfigure all over again everytime there is an
> upgrade. And they worked fine with version 5.0.0, so no need to.
>
> Any ideas on what is happening?
>
>
> Log snippet:
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: Caught
> unrecoverable exception in generator
> 'weewx.cheetahgenerator.CheetahGenerator'
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  [Errno 13] Permission denied: '/var/www/
> rumoclock.dk/web/weewx/index.html.tmp'
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  Traceback (most recent call last):
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  File "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>obj.start()
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  File "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>self.run()
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts)
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>ngen += self.generate(section[subsection], subsection, gen_ts)
> Feb  8 08:33:00 frej weewxd[754]: Traceback (most recent call last):
> Feb  8 08:33:00 frej weewxd[754]:   File
> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Feb  8 08:33:00 frej weewxd[754]: obj.start()
> Feb  8 08:33:00 frej weewxd[754]:   File
> "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Feb  8 08:33:00 frej weewxd[754]: self.run()
> Feb  8 08:33:00 frej weewxd[754]:   File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
> Feb  8 08:33:00 frej weewxd[754]: ngen =
> self.generate(gen_dict[section_name], section_name, self.gen_ts)
> Feb  8 08:33:00 frej weewxd[754]:   File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
> Feb  8 08:33:00 frej weewxd[754]: ngen +=
> self.generate(section[subsection], subsection, gen_ts)
> Feb  8 08:33:00 frej weewxd[754]:   File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
> Feb  8 08:33:00 frej weewxd[754]: ngen +=
> self.generate(section[subsection], subsection, gen_ts)
> Feb  8 08:33:00 frej weewxd[754]:   File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 371, in generate
> Feb  8 08:33:00 frej weewxd[754]: with open(tmpname, mode='wb') as fd:
> Feb  8 08:33:00 frej weewxd[754]: PermissionError: [Errno 13] Permission
> denied: '/var/www/rumoclock.dk/web/weewx/index.html.tmp'
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>ngen += self.generate(section[subsection], subsection, gen_ts)
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 371, in generate
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>with open(tmpname, mode='wb') as fd:
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  PermissionError: [Errno 13] Permission denied: '/var/www/
> rumoclock.dk/web/weewx/index.html.tmp'
> Feb  8 08:33:00 frej weewxd[754]: ERROR weewx.reportengine: 
>  Generator terminated
> Feb  8 08:33:00 frej weewxd[754]: DEBUG weewx.manager: Daily summary
> version is 4.0
> Feb  8 08:33:00 frej weewxd[754]: INFO weewx.imagegenerator: Generated 10
> images for report SeasonsReport in 0.67 seconds
> Feb  8 08:33:00 frej weewxd[754]: INFO weewx.reportengine: Copied 0 files
> to /var/www/rumoclock.dk/web/weewx
> Feb  8 08:33:00 frej weewxd[754]: DEBUG weewx.reportengine: Running report
> 'SmartphoneReport'
> Feb  8 08:33:00 frej weewxd[754]: DEBUG weewx.reportengine: Found
> configuration file 

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

Thanks a lot, very interesting !

Yesterday, as I failed to have weewx 5.1 working properly, I reverted to 
4.10.2.

My configuration is very similar :
- BME280 sensor
- AS3953 lightning sensor
- SDR driver
- Seasons skin
- Belchertown skin

I am tempted to give a new try...

Pierre-Yves

Le jeudi 8 février 2024 à 10:40:18 UTC+1, Mks Mk a écrit :

> today tried to update my other raspberry pi to weewx v5.01 and this pi is 
> different than the main weather pi that we use:
> 1-bme280 sensor.
> 2-sdr
> 3-weewx-wxobs skin.
>
>
> after the weewx update we did the following:
> sudo usermod -aG dialout weewx
> sudo usermod -aG plugdev weewx
> sudo systemctl restart udev weewx
>
> but weewx v5.01 failed with following errors:
> -PermissionError: [Errno 13] Permission denied: '/dev/i2c-1', this error 
> related to bme280 sensor
> running this command "sudo usermod -aG i2c weewx" fixed the issue.
>
> -PermissionError: [Errno 13] Permission denied: 
> '/usr/share/php/wxobs_weewx.inc', this error related to weewx-wxobs skin
> we are using apache2, doing these changes fixed the issue (thanks to 
> *glennmckechnie*)
> mkdir /etc/weewx/wxobs-tmp
> chown weewx.weewx /etc/weewx/wxobs-tmp
> edited skin.conf located in /etc/weewx/skins/wxobs/ and uncommenting line 
> #30 and changing include_path = '/tmp' to become include_path = 
> '/etc/weewx/wxobs-tmp'
>
> weewx v5.01 is running ok now on this raspberry pi, hoping the above step 
> may help someone during the upgrade to weewx v5.01
>
> On Wednesday, February 7, 2024 at 7:59:59 PM UTC+3 Tom Keffer wrote:
>
>> https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user
>>
>>
>> On Wed, Feb 7, 2024 at 8:58 AM Tom Keffer  wrote:
>>
>>> I'll add "plughw" to the troubleshooting section.
>>>
>>> -tk
>>>
>>> On Wed, Feb 7, 2024 at 8:16 AM Steve Gee  wrote:
>>>
 I ended up adding the weewx user to the plughw group which fixed the 
 problem with rtl_433 not starting:

 sudo adduser weewx plughw
 sudo systemctl restart weewx.service

 On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František Slimařík 
 wrote:

> @Matthew:
>
> That makes sense yep. Thanks a lot for detailed explanation. I cannot 
> change port 80 on my hardware so I will review other options :)
>
> st 7. 2. 2024 v 8:08 odesílatel matthew wall  
> napsal:
>
>> another option is to put a proxy in front of interceptor.  configure 
>> interceptor to listen on a high port, say 8080, then run nginx binding 
>> to 
>> port 80 as a reverse proxy to interceptor, proxying all traffic or just 
>> specific requests.
>>
>> m
>>
>> -- 
>> You received this message because you are subscribed to a topic in 
>> the Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/5BuR3BSQfeY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e8a748e8-5008-4ecc-b5f2-59fad26e8b67n%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 on the web visit 
 https://groups.google.com/d/msgid/weewx-user/3239d8e8-5e87-420a-a660-74666b1847ben%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/841fd8c5-0d2c-4007-a34c-7077d2fbae7cn%40googlegroups.com.

Re: [weewx-user] Re: rsync: host key verification failed - problem

[Dominic Reich]

Kalju  wrote:


Hi all,

Facing same issue with ERROR weeutil.rsyncupload:  Host key verification
failed error. 
However, it's really strange...
I can ssh to remote site as both root as well as pi user
I can do manual rsync with no problems but weewx builtin rsync returns above
error
At the moment my weewx installation is syncing using cron with no problems but
I want to understand why builtin rsync fails
Problem started after upgrade from weewx 5.0.0 to 5.0.1

Any ideas?


Adding the debug info should output the actual rsync command initiated by
weewx to the logs. That's what I assume when looking at line 104 in
`src/weeutil/rsyncupload.py` from the sources of 5.0.1.

Maybe that gives a clue in which the actual rsync commands differ and
why it might fail within Weewx.

Somewhere around 5.0.1 or 5.1.x the user got switched to weewx (not root
anymore) so maybe there is a problem? (I can't remember when the switch
was (it was mentioned on the list somwhere) and haven't found it in the
docs yet)

I'd always suggest looking as what weewx is running so you may not have
to play the guessing game on which user to look at.

sudo ps ux | grep weewxd

should return the user that actually runs the (python) daemon like on my
old Raspberry this runs still as root with 4.10.2.

root 690  2.8  1.5 647360 60428 ?Sl   Feb06  75:38 python3 
/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid 
/etc/weewx/weewx.conf

As it was a package-installation I never messed with it, though I
welcome the change to a non-root package installation per default :)

In case host keys have changed on the server a deletion of the known_hosts
file within ~/.ssh could also help, probably.

-dominic


Thank you forward :-)
On Friday, July 21, 2023 at 1:14:24 PM UTC+3 Tomasz Lewicki wrote:

   Thank you for replies.

   @Warren Gill: yes, I was thinking about crontab but wanted to use built-in
   solution. Of course crontab is good as backup solution.

   @vince: you're right, I didn't think about it from this side. Just for
   record for future seekers:

   1. I logged as root ('sudo -i' from 'pi' account)
   2. generated SSH keys ('ssh-keygen')
   3. copied them to external server ('ssh-copy-id ace...@external.domain.com
   -p 222')
   4. copied /home/pi/.ssh/config to /root/.ssh/config
   5. changed owner of 'config' ('chown root:root /root/.ssh/config')
   6. waited for next synchronization
   7. smiled because everything worked as expected :)



--
Educating the mind without educating the heart is no education at all.
- Aristotle

--
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 the web visit 
https://groups.google.com/d/msgid/weewx-user/%24tcqbskwxq-%24bksDsvl-%24pdtHn-2024%40odin.oe7drt.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Mks Mk]

today tried to update my other raspberry pi to weewx v5.01 and this pi is 
different than the main weather pi that we use:
1-bme280 sensor.
2-sdr
3-weewx-wxobs skin.


after the weewx update we did the following:
sudo usermod -aG dialout weewx
sudo usermod -aG plugdev weewx
sudo systemctl restart udev weewx

but weewx v5.01 failed with following errors:
-PermissionError: [Errno 13] Permission denied: '/dev/i2c-1', this error 
related to bme280 sensor
running this command "sudo usermod -aG i2c weewx" fixed the issue.

-PermissionError: [Errno 13] Permission denied: 
'/usr/share/php/wxobs_weewx.inc', this error related to weewx-wxobs skin
we are using apache2, doing these changes fixed the issue (thanks to 
*glennmckechnie*)
mkdir /etc/weewx/wxobs-tmp
chown weewx.weewx /etc/weewx/wxobs-tmp
edited skin.conf located in /etc/weewx/skins/wxobs/ and uncommenting line 
#30 and changing include_path = '/tmp' to become include_path = 
'/etc/weewx/wxobs-tmp'

weewx v5.01 is running ok now on this raspberry pi, hoping the above step 
may help someone during the upgrade to weewx v5.01

On Wednesday, February 7, 2024 at 7:59:59 PM UTC+3 Tom Keffer wrote:

> https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user
>
>
> On Wed, Feb 7, 2024 at 8:58 AM Tom Keffer  wrote:
>
>> I'll add "plughw" to the troubleshooting section.
>>
>> -tk
>>
>> On Wed, Feb 7, 2024 at 8:16 AM Steve Gee  wrote:
>>
>>> I ended up adding the weewx user to the plughw group which fixed the 
>>> problem with rtl_433 not starting:
>>>
>>> sudo adduser weewx plughw
>>> sudo systemctl restart weewx.service
>>>
>>> On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František Slimařík 
>>> wrote:
>>>
 @Matthew:

 That makes sense yep. Thanks a lot for detailed explanation. I cannot 
 change port 80 on my hardware so I will review other options :)

 st 7. 2. 2024 v 8:08 odesílatel matthew wall  
 napsal:

> another option is to put a proxy in front of interceptor.  configure 
> interceptor to listen on a high port, say 8080, then run nginx binding to 
> port 80 as a reverse proxy to interceptor, proxying all traffic or just 
> specific requests.
>
> m
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/5BuR3BSQfeY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/e8a748e8-5008-4ecc-b5f2-59fad26e8b67n%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 on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/3239d8e8-5e87-420a-a660-74666b1847ben%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/40f7eabb-bca8-4b44-9038-45b34398b963n%40googlegroups.com.

[weewx-user] Re: rsync: host key verification failed - problem

['Tomasz Lewicki' via weewx-user]

In my weewx.conf I have a section:

[[RSYNC]]
enable = true
server = XYZ # It's only identifier needed for file described below. 
Can be anything, for example MY_SECRET_SERVER
path = /path/to/files/on/my/remote/server # for example: 
/domains/my-domain/public_html/pws

And in /root/.ssh I have file named simply 'config':

Host XYZ
HostName my.remote.server.com # HostName can be also direct IP address
Port 45678 # Port to SSH if not standard 22
User me # name of your user on remote server

And rsync from inside of Weewx works in my case.

czwartek, 8 lutego 2024 o 09:33:14 UTC+1 Kalju napisał(a):

> Hi all,
>
> Facing same issue with *ERROR weeutil.rsyncupload:  Host key 
> verification failed *error. 
> However, it's really strange...
> I can ssh to remote site as both *root* as well as *pi* user
> I can do manual rsync with no problems but weewx builtin rsync returns 
> above error
> At the moment my weewx installation is syncing using cron with no problems 
> but I want to understand why builtin rsync fails
> Problem started after upgrade from weewx 5.0.0 to 5.0.1
>
> Any ideas?
> Thank you forward :-)
> On Friday, July 21, 2023 at 1:14:24 PM UTC+3 Tomasz Lewicki wrote:
>
>> Thank you for replies.
>>
>> @Warren Gill: yes, I was thinking about crontab but wanted to use 
>> built-in solution. Of course crontab is good as backup solution.
>>
>> @vince: you're right, I didn't think about it from this side. Just for 
>> record for future seekers:
>>
>> 1. I logged as root ('sudo -i' from 'pi' account)
>> 2. generated SSH keys ('ssh-keygen')
>> 3. copied them to external server ('ssh-copy-id 
>> ace...@external.domain.com -p 222')
>> 4. copied /home/pi/.ssh/config to /root/.ssh/config
>> 5. changed owner of 'config' ('chown root:root /root/.ssh/config')
>> 6. waited for next synchronization
>> 7. smiled because everything worked as expected :)
>>
>> czwartek, 20 lipca 2023 o 23:24:20 UTC+2 vince napisał(a):
>>
>>> Unless you did something custom, weewx runs as root, not as user 'pi'.
>>>
>>> You need 'root' to be able to ssh into the remote system with the 
>>> user+key you specified.  Same procedure you did to get 'pi' to work, just 
>>> do it after sudo(ing) to root so you set the 'root' account up similiarly. 
>>>   Two minute thing to do.
>>>
>>> On Thursday, July 20, 2023 at 1:06:54 PM UTC-7 Tomasz Lewicki wrote:
>>>
 rsync: host key verification failed

 Dear Weewx users.

 I'm trying to send files generated by Weewx to external webserver (paid 
 hosting) with rsync. I'm familiar with rsync, ssh and Linux. Weewx is 
 running on Raspberry Pi as 'pi' user. Here are my configs:

 /home/pi/.ssh/config

 Host CF
 #HostName external.domain.com <- here of course is real web address
 HostName 10.20.30.40 <- here of course is real IP
 Port 222
 User acetone <- this is my username on remote webserver (hosting)
 
 /etc/weewx/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
 # public/private key authentication from the user account that 
 weewx
 # runs to the user account on the remote machine where the files
 # will be copied.
 #
 # If you wish to use rsync, set "enable" to "true", then
 # fill out server, user, and path.
 # The server should appear in your .ssh/config file.
 # The user is the username used in the identity file.
 # The path is the destination directory, such as 
 /var/www/html/weather.
 # Be sure that the user has write permissions on the 
 destination!
 enable = true
 server = external.domain.com
 port = 222
 user = acetone
 path = domains/external.domain.com/private_html/meteo/
 
 # To upload files from something other than what HTML_ROOT is 
 set
 # to above, specify a different HTML_ROOT here.
 #HTML_ROOT = /var/www/html/weewx
 
 # Rsync can be configured to remove files from the remote 
 server if
 # they don't exist under HTML_ROOT locally. USE WITH CAUTION: 
 if you
 # make a mistake in the remote path, you could could 
 unintentionally
 # cause unrelated files to be deleted. Set to 1 to enable 
 remote file
 # deletion, zero to allow files to accumulate remotely.
 delete = 0

 (...)

 I can log in to external server with ssh (passwordless) with command:

 $ ssh -p 222 ace...@external.domain.com

 or just

 $ ssh CF <- this is host from .ssh/config

 I got error message from weewx:

 Jul 

[weewx-user] Re: rsync: host key verification failed - problem

[Kalju]

Hi all,

Facing same issue with *ERROR weeutil.rsyncupload:  Host key 
verification failed *error. 
However, it's really strange...
I can ssh to remote site as both *root* as well as *pi* user
I can do manual rsync with no problems but weewx builtin rsync returns 
above error
At the moment my weewx installation is syncing using cron with no problems 
but I want to understand why builtin rsync fails
Problem started after upgrade from weewx 5.0.0 to 5.0.1

Any ideas?
Thank you forward :-)
On Friday, July 21, 2023 at 1:14:24 PM UTC+3 Tomasz Lewicki wrote:

> Thank you for replies.
>
> @Warren Gill: yes, I was thinking about crontab but wanted to use built-in 
> solution. Of course crontab is good as backup solution.
>
> @vince: you're right, I didn't think about it from this side. Just for 
> record for future seekers:
>
> 1. I logged as root ('sudo -i' from 'pi' account)
> 2. generated SSH keys ('ssh-keygen')
> 3. copied them to external server ('ssh-copy-id ace...@external.domain.com 
> -p 222')
> 4. copied /home/pi/.ssh/config to /root/.ssh/config
> 5. changed owner of 'config' ('chown root:root /root/.ssh/config')
> 6. waited for next synchronization
> 7. smiled because everything worked as expected :)
>
> czwartek, 20 lipca 2023 o 23:24:20 UTC+2 vince napisał(a):
>
>> Unless you did something custom, weewx runs as root, not as user 'pi'.
>>
>> You need 'root' to be able to ssh into the remote system with the 
>> user+key you specified.  Same procedure you did to get 'pi' to work, just 
>> do it after sudo(ing) to root so you set the 'root' account up similiarly. 
>>   Two minute thing to do.
>>
>> On Thursday, July 20, 2023 at 1:06:54 PM UTC-7 Tomasz Lewicki wrote:
>>
>>> rsync: host key verification failed
>>>
>>> Dear Weewx users.
>>>
>>> I'm trying to send files generated by Weewx to external webserver (paid 
>>> hosting) with rsync. I'm familiar with rsync, ssh and Linux. Weewx is 
>>> running on Raspberry Pi as 'pi' user. Here are my configs:
>>>
>>> /home/pi/.ssh/config
>>>
>>> Host CF
>>> #HostName external.domain.com <- here of course is real web address
>>> HostName 10.20.30.40 <- here of course is real IP
>>> Port 222
>>> User acetone <- this is my username on remote webserver (hosting)
>>> 
>>> /etc/weewx/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
>>> # public/private key authentication from the user account that 
>>> weewx
>>> # runs to the user account on the remote machine where the files
>>> # will be copied.
>>> #
>>> # If you wish to use rsync, set "enable" to "true", then
>>> # fill out server, user, and path.
>>> # The server should appear in your .ssh/config file.
>>> # The user is the username used in the identity file.
>>> # The path is the destination directory, such as 
>>> /var/www/html/weather.
>>> # Be sure that the user has write permissions on the destination!
>>> enable = true
>>> server = external.domain.com
>>> port = 222
>>> user = acetone
>>> path = domains/external.domain.com/private_html/meteo/
>>> 
>>> # To upload files from something other than what HTML_ROOT is set
>>> # to above, specify a different HTML_ROOT here.
>>> #HTML_ROOT = /var/www/html/weewx
>>> 
>>> # Rsync can be configured to remove files from the remote server 
>>> if
>>> # they don't exist under HTML_ROOT locally. USE WITH CAUTION: if 
>>> you
>>> # make a mistake in the remote path, you could could 
>>> unintentionally
>>> # cause unrelated files to be deleted. Set to 1 to enable remote 
>>> file
>>> # deletion, zero to allow files to accumulate remotely.
>>> delete = 0
>>>
>>> (...)
>>>
>>> I can log in to external server with ssh (passwordless) with command:
>>>
>>> $ ssh -p 222 ace...@external.domain.com
>>>
>>> or just
>>>
>>> $ ssh CF <- this is host from .ssh/config
>>>
>>> I got error message from weewx:
>>>
>>> Jul 20 21:36:04 WeewxFR24 weewx[28079] DEBUG weeutil.rsyncupload: 
>>> rsyncupload: cmd: [['rsync', '--archive', '--stats', '-e', 'ssh -p 222', 
>>> '/var/www/html/weewx/', 'ace...@external.domain.com:~/domains/
>>> external.domain.com/private_html/meteo']]
>>> Jul 20 21:36:04 WeewxFR24 weewx[28079] ERROR weeutil.rsyncupload: rsync 
>>> reported errors. Original command: ['rsync', '--archive', '--stats', '-e', 
>>> 'ssh -p 222', '/var/www/html/weewx/', 'ace...@external.domain.com:~/domains/
>>> external.domain.com/private_html/meteo']
>>> Jul 20 21:36:04 WeewxFR24 weewx[28079] ERROR weeutil.rsyncupload:  
>>> Host key verification failed.
>>> Jul 20 21:36:04 WeewxFR24 weewx[28079] ERROR weeutil.rsyncupload:  
>>> rsync: connection unexpectedly closed (0 bytes