Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

['Peter Fletcher' via weewx-user]

That is the entire log from shortly before the update. I am guessing that 
the known bug in crt.py results in the crash not being properly reported.

The good news is that I was able to figure out what was going on. I am 
using crt to produce a file that allows the display of current weather 
conditions on my HOA's website. It is written to a subfolder of its own in 
/var/www/html and uploaded to the HOA site from there by weewx. Again, it 
was the change from weewx running as root to it running as weewx that was 
causing an access privilege error. Simply deleting the old version of the 
file did not solve the problem, but assigning ownership of the relevant 
*subfolder* to weewx:weewx restored normal functionality.
On Tuesday, February 20, 2024 at 8:50:50 PM UTC-5 Tom Keffer wrote:

> That's the end of the log? Where is the crt error?
>
> The record timestamped 2024-02-20 20:30:00 was downloaded from the logger 
> at 20:32:22. I would expect the next record to be processed at 20:35:16 or 
> so. Did you terminate the program? Is there something later in the log?
>
> On Tue, Feb 20, 2024 at 5:41 PM 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Here is the log from before I applied the apt update, through now. This 
>> includes one reboot. The last  start was after setting debug=1 in the 
>> config file. I hope that it helps you more than it does me!:
>>
>> Feb 20 18:20:19 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
>> Generated 7 files for report SeasonsReport in 2.52 seconds
>> Feb 20 18:20:21 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
>> Generated 16 images for report SeasonsReport in 1.47 seconds
>> Feb 20 18:20:21 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> Feb 20 18:20:23 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report PublicReport in 2.19 seconds
>> Feb 20 18:20:24 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
>> Generated 16 images for report PublicReport in 1.39 seconds
>> Feb 20 18:20:24 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx2
>> Feb 20 18:20:25 bullseyepi weewxd[447]: INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 1 files in 0.75 seconds
>> Feb 20 18:20:35 bullseyepi weewxd[447]: INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 22 files in 10.12 seconds
>> Feb 20 18:25:16 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
>> 2024-02-20 18:25:00 EST (1708471500) to database 'weewx.sdb'
>> Feb 20 18:25:16 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
>> 2024-02-20 18:25:00 EST (1708471500) to daily summary in 'weewx.sdb'
>> Feb 20 18:25:19 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
>> Generated 7 files for report SeasonsReport in 2.53 seconds
>> Feb 20 18:25:20 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
>> Generated 16 images for report SeasonsReport in 1.41 seconds
>> Feb 20 18:25:20 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> Feb 20 18:25:23 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report PublicReport in 2.19 seconds
>> Feb 20 18:25:24 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
>> Generated 16 images for report PublicReport in 1.40 seconds
>> Feb 20 18:25:24 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx2
>> Feb 20 18:25:25 bullseyepi weewxd[447]: INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 1 files in 0.76 seconds
>> Feb 20 18:25:36 bullseyepi weewxd[447]: INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 22 files in 11.08 seconds
>> Feb 20 18:30:21 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
>> 2024-02-20 18:30:00 EST (1708471800) to database 'weewx.sdb'
>> Feb 20 18:30:21 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
>> 2024-02-20 18:30:00 EST (1708471800) to daily summary in 'weewx.sdb'
>> Feb 20 18:30:24 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
>> Generated 7 files for report SeasonsReport in 3.31 seconds
>> Feb 20 18:30:26 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
>> Generated 16 images for report SeasonsReport in 1.62 seconds
>> Feb 20 18:30:26 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> Feb 20 18:30:28 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report PublicReport in 2.54 seconds
>> Feb 20 18:30:30 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
>> Generated 16 images for report PublicReport in 1.47 seconds
>> Feb 20 18:30:30 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx2
>> Feb 20 18:30:31 bullseyepi weewxd[447]: INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 1 files in 0.76 seconds
>> Feb 20 18:30:41 bullseyepi weewxd[447]: INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 22 files in 10.28 seconds
>> Feb 20 18:32:29 bullseyepi 

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

[Tom Keffer]

That's the end of the log? Where is the crt error?

The record timestamped 2024-02-20 20:30:00 was downloaded from the logger
at 20:32:22. I would expect the next record to be processed at 20:35:16 or
so. Did you terminate the program? Is there something later in the log?

On Tue, Feb 20, 2024 at 5:41 PM 'Peter Fletcher' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Here is the log from before I applied the apt update, through now. This
> includes one reboot. The last  start was after setting debug=1 in the
> config file. I hope that it helps you more than it does me!:
>
> Feb 20 18:20:19 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator:
> Generated 7 files for report SeasonsReport in 2.52 seconds
> Feb 20 18:20:21 bullseyepi weewxd[447]: INFO weewx.imagegenerator:
> Generated 16 images for report SeasonsReport in 1.47 seconds
> Feb 20 18:20:21 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> Feb 20 18:20:23 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator:
> Generated 8 files for report PublicReport in 2.19 seconds
> Feb 20 18:20:24 bullseyepi weewxd[447]: INFO weewx.imagegenerator:
> Generated 16 images for report PublicReport in 1.39 seconds
> Feb 20 18:20:24 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx2
> Feb 20 18:20:25 bullseyepi weewxd[447]: INFO weewx.reportengine:
> ftpgenerator: Ftp'd 1 files in 0.75 seconds
> Feb 20 18:20:35 bullseyepi weewxd[447]: INFO weewx.reportengine:
> ftpgenerator: Ftp'd 22 files in 10.12 seconds
> Feb 20 18:25:16 bullseyepi weewxd[447]: INFO weewx.manager: Added record
> 2024-02-20 18:25:00 EST (1708471500) to database 'weewx.sdb'
> Feb 20 18:25:16 bullseyepi weewxd[447]: INFO weewx.manager: Added record
> 2024-02-20 18:25:00 EST (1708471500) to daily summary in 'weewx.sdb'
> Feb 20 18:25:19 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator:
> Generated 7 files for report SeasonsReport in 2.53 seconds
> Feb 20 18:25:20 bullseyepi weewxd[447]: INFO weewx.imagegenerator:
> Generated 16 images for report SeasonsReport in 1.41 seconds
> Feb 20 18:25:20 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> Feb 20 18:25:23 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator:
> Generated 8 files for report PublicReport in 2.19 seconds
> Feb 20 18:25:24 bullseyepi weewxd[447]: INFO weewx.imagegenerator:
> Generated 16 images for report PublicReport in 1.40 seconds
> Feb 20 18:25:24 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx2
> Feb 20 18:25:25 bullseyepi weewxd[447]: INFO weewx.reportengine:
> ftpgenerator: Ftp'd 1 files in 0.76 seconds
> Feb 20 18:25:36 bullseyepi weewxd[447]: INFO weewx.reportengine:
> ftpgenerator: Ftp'd 22 files in 11.08 seconds
> Feb 20 18:30:21 bullseyepi weewxd[447]: INFO weewx.manager: Added record
> 2024-02-20 18:30:00 EST (1708471800) to database 'weewx.sdb'
> Feb 20 18:30:21 bullseyepi weewxd[447]: INFO weewx.manager: Added record
> 2024-02-20 18:30:00 EST (1708471800) to daily summary in 'weewx.sdb'
> Feb 20 18:30:24 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator:
> Generated 7 files for report SeasonsReport in 3.31 seconds
> Feb 20 18:30:26 bullseyepi weewxd[447]: INFO weewx.imagegenerator:
> Generated 16 images for report SeasonsReport in 1.62 seconds
> Feb 20 18:30:26 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> Feb 20 18:30:28 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator:
> Generated 8 files for report PublicReport in 2.54 seconds
> Feb 20 18:30:30 bullseyepi weewxd[447]: INFO weewx.imagegenerator:
> Generated 16 images for report PublicReport in 1.47 seconds
> Feb 20 18:30:30 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx2
> Feb 20 18:30:31 bullseyepi weewxd[447]: INFO weewx.reportengine:
> ftpgenerator: Ftp'd 1 files in 0.76 seconds
> Feb 20 18:30:41 bullseyepi weewxd[447]: INFO weewx.reportengine:
> ftpgenerator: Ftp'd 22 files in 10.28 seconds
> Feb 20 18:32:29 bullseyepi weewxd[447]: INFO __main__: Received signal
> TERM (15).
> Feb 20 18:32:29 bullseyepi weewxd[447]: INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Feb 20 18:32:29 bullseyepi weewxd[447]: INFO weewx.engine: Shutting down
> StdReport thread
> Feb 20 18:32:29 bullseyepi weewxd[447]: INFO __main__: Terminating weewx
> version 5.0.0
> Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Initializing
> weewxd version 5.0.2
> Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Command line:
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Using Python
> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
> Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Located at
> /usr/bin/python3
> Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Platform
> Linux-6.1.21-v7+-armv7l-with-glibc2.31
> 

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

['Peter Fletcher' via weewx-user]

Here is the log from before I applied the apt update, through now. This 
includes one reboot. The last  start was after setting debug=1 in the 
config file. I hope that it helps you more than it does me!:

Feb 20 18:20:19 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
Generated 7 files for report SeasonsReport in 2.52 seconds
Feb 20 18:20:21 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
Generated 16 images for report SeasonsReport in 1.47 seconds
Feb 20 18:20:21 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Feb 20 18:20:23 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
Generated 8 files for report PublicReport in 2.19 seconds
Feb 20 18:20:24 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
Generated 16 images for report PublicReport in 1.39 seconds
Feb 20 18:20:24 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx2
Feb 20 18:20:25 bullseyepi weewxd[447]: INFO weewx.reportengine: 
ftpgenerator: Ftp'd 1 files in 0.75 seconds
Feb 20 18:20:35 bullseyepi weewxd[447]: INFO weewx.reportengine: 
ftpgenerator: Ftp'd 22 files in 10.12 seconds
Feb 20 18:25:16 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
2024-02-20 18:25:00 EST (1708471500) to database 'weewx.sdb'
Feb 20 18:25:16 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
2024-02-20 18:25:00 EST (1708471500) to daily summary in 'weewx.sdb'
Feb 20 18:25:19 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
Generated 7 files for report SeasonsReport in 2.53 seconds
Feb 20 18:25:20 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
Generated 16 images for report SeasonsReport in 1.41 seconds
Feb 20 18:25:20 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Feb 20 18:25:23 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
Generated 8 files for report PublicReport in 2.19 seconds
Feb 20 18:25:24 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
Generated 16 images for report PublicReport in 1.40 seconds
Feb 20 18:25:24 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx2
Feb 20 18:25:25 bullseyepi weewxd[447]: INFO weewx.reportengine: 
ftpgenerator: Ftp'd 1 files in 0.76 seconds
Feb 20 18:25:36 bullseyepi weewxd[447]: INFO weewx.reportengine: 
ftpgenerator: Ftp'd 22 files in 11.08 seconds
Feb 20 18:30:21 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
2024-02-20 18:30:00 EST (1708471800) to database 'weewx.sdb'
Feb 20 18:30:21 bullseyepi weewxd[447]: INFO weewx.manager: Added record 
2024-02-20 18:30:00 EST (1708471800) to daily summary in 'weewx.sdb'
Feb 20 18:30:24 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
Generated 7 files for report SeasonsReport in 3.31 seconds
Feb 20 18:30:26 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
Generated 16 images for report SeasonsReport in 1.62 seconds
Feb 20 18:30:26 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Feb 20 18:30:28 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: 
Generated 8 files for report PublicReport in 2.54 seconds
Feb 20 18:30:30 bullseyepi weewxd[447]: INFO weewx.imagegenerator: 
Generated 16 images for report PublicReport in 1.47 seconds
Feb 20 18:30:30 bullseyepi weewxd[447]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx2
Feb 20 18:30:31 bullseyepi weewxd[447]: INFO weewx.reportengine: 
ftpgenerator: Ftp'd 1 files in 0.76 seconds
Feb 20 18:30:41 bullseyepi weewxd[447]: INFO weewx.reportengine: 
ftpgenerator: Ftp'd 22 files in 10.28 seconds
Feb 20 18:32:29 bullseyepi weewxd[447]: INFO __main__: Received signal TERM 
(15).
Feb 20 18:32:29 bullseyepi weewxd[447]: INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Feb 20 18:32:29 bullseyepi weewxd[447]: INFO weewx.engine: Shutting down 
StdReport thread
Feb 20 18:32:29 bullseyepi weewxd[447]: INFO __main__: Terminating weewx 
version 5.0.0
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Initializing 
weewxd version 5.0.2
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Command line: 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Using Python 3.9.2 
(default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Located at 
/usr/bin/python3
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Platform 
Linux-6.1.21-v7+-armv7l-with-glibc2.31
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Locale: 'en_US'
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Entry path: 
/usr/share/weewx/weewxd.py
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: WEEWX_ROOT: 
/etc/weewx
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: Configuration 
file: /etc/weewx/weewx.conf
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO __main__: User module: 
/etc/weewx/bin/user
Feb 20 18:33:15 bullseyepi weewxd[18134]: INFO 

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

[Tom Keffer]

The "AttributeError" problem is a known problem with crt. See this thread
.

But, it is not the actual problem --- it's just a reporting problem. For
the actual problem, we will need to see more of the log.

On Tue, Feb 20, 2024 at 4:14 PM 'Peter Fletcher' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I have had weewx 4.x (apt installed) running happily on my Pi 3b for
> years. A month ago, since 5.0 seemed to be stable, I allowed the upgrade to
> the then current release of 5.0. Since there had been a few concerns raised
> about it, I did a complete image backup of the Pi before allowing the
> upgrade. This turned out not to be necessary, since the upgrade essentially
> 'just worked', though I did have to deal with the missing private key issue
> that has been discussed elsewhere. This evening, as part of a routine apt
> full-upgrade, , I was updated to 5.02, and the weewx installation appears
> to have been comprehensively clobbered. Sadly, it didn't occur to me to do
> an image backup before a minor update, So I don't have an easy way of going
> back. The initial error appeared to be an access violation to /dev/serial0,
> such as was described in another recent thread with this version of weewx,
> but changing the ownership of the serial port to weewx:weewx only changed
> the problem. systemctl status now reports:
> * weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>  Active: failed (Result: exit-code) since Tue 2024-02-20 18:48:39 EST;
> 31s ago
>Docs: https://weewx.com/docs
> Process: 3348 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=1/FAILURE)
>Main PID: 3348 (code=exited, status=1/FAILURE)
> CPU: 1.256s
>
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  callback(event)
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  File "/etc/weewx/bin/user/crt.py", line 540, in handle_new_loop
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  self.handle_data(event.packet)
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  File "/etc/weewx/bin/user/crt.py", line 563, in handle_data
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  weeutil.weeutil.log_traceback('crt:  ')
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  AttributeError: module 'weeutil.weeutil' has no attribute 'log_traceback'
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  Exiting.
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Main process exited,
> code=exited, status=1/FAILURE
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Consumed 1.256s CPU
> time.
>
> What is going on?
>
> --
> 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/9e86020c-1a88-4b0a-b47f-6133c5432b88n%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/CAPq0zEADbiW1%3D988zn%2BV-pUdP3Oi-ihZNfHAT3v-FqmMrQN05Q%40mail.gmail.com.

[weewx-user] Re: Catastrophic apt upgrade to V5.02 on Raspberry Pi

[vince]

Well FWIW the error appears to be for the optional crt extension so I’d 
perhaps try disabling that and seeing if core weewx is ok. As always set 
debug=1 and provide logs from weewx startup through two archive periods.

You could also try reinstalling the crt extension.  Back your /etc/weewx 
tree up just in case,

On Tuesday, February 20, 2024 at 4:14:01 PM UTC-8 Peter Fletcher wrote:

> I have had weewx 4.x (apt installed) running happily on my Pi 3b for 
> years. A month ago, since 5.0 seemed to be stable, I allowed the upgrade to 
> the then current release of 5.0. Since there had been a few concerns raised 
> about it, I did a complete image backup of the Pi before allowing the 
> upgrade. This turned out not to be necessary, since the upgrade essentially 
> 'just worked', though I did have to deal with the missing private key issue 
> that has been discussed elsewhere. This evening, as part of a routine apt 
> full-upgrade, , I was updated to 5.02, and the weewx installation appears 
> to have been comprehensively clobbered. Sadly, it didn't occur to me to do 
> an image backup before a minor update, So I don't have an easy way of going 
> back. The initial error appeared to be an access violation to /dev/serial0, 
> such as was described in another recent thread with this version of weewx, 
> but changing the ownership of the serial port to weewx:weewx only changed 
> the problem. systemctl status now reports:
> * weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>  Active: failed (Result: exit-code) since Tue 2024-02-20 18:48:39 EST; 
> 31s ago
>Docs: https://weewx.com/docs
> Process: 3348 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=1/FAILURE)
>Main PID: 3348 (code=exited, status=1/FAILURE)
> CPU: 1.256s
>
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
>  callback(event)
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:    
>  File "/etc/weewx/bin/user/crt.py", line 540, in handle_new_loop
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
>  self.handle_data(event.packet)
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:    
>  File "/etc/weewx/bin/user/crt.py", line 563, in handle_data
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
>  weeutil.weeutil.log_traceback('crt:  ')
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
>  AttributeError: module 'weeutil.weeutil' has no attribute 'log_traceback'
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
>  Exiting.
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Main process exited, 
> code=exited, status=1/FAILURE
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Consumed 1.256s CPU 
> time.
>
> What is going on?
>

-- 
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/40c779ea-b896-441b-9151-6cace208397cn%40googlegroups.com.

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

[p q]

https://weewx.com/docs/5.0/usersguide/troubleshooting/what-to-do/


   1.

   Look at the log file
   . We are
   always happy to take questions, but the first thing someone will ask is,
   "What did you find in the log file?"


On Tue, Feb 20, 2024 at 4:14 PM 'Peter Fletcher' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I have had weewx 4.x (apt installed) running happily on my Pi 3b for
> years. A month ago, since 5.0 seemed to be stable, I allowed the upgrade to
> the then current release of 5.0. Since there had been a few concerns raised
> about it, I did a complete image backup of the Pi before allowing the
> upgrade. This turned out not to be necessary, since the upgrade essentially
> 'just worked', though I did have to deal with the missing private key issue
> that has been discussed elsewhere. This evening, as part of a routine apt
> full-upgrade, , I was updated to 5.02, and the weewx installation appears
> to have been comprehensively clobbered. Sadly, it didn't occur to me to do
> an image backup before a minor update, So I don't have an easy way of going
> back. The initial error appeared to be an access violation to /dev/serial0,
> such as was described in another recent thread with this version of weewx,
> but changing the ownership of the serial port to weewx:weewx only changed
> the problem. systemctl status now reports:
> * weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>  Active: failed (Result: exit-code) since Tue 2024-02-20 18:48:39 EST;
> 31s ago
>Docs: https://weewx.com/docs
> Process: 3348 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=1/FAILURE)
>Main PID: 3348 (code=exited, status=1/FAILURE)
> CPU: 1.256s
>
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  callback(event)
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  File "/etc/weewx/bin/user/crt.py", line 540, in handle_new_loop
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  self.handle_data(event.packet)
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  File "/etc/weewx/bin/user/crt.py", line 563, in handle_data
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  weeutil.weeutil.log_traceback('crt:  ')
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  AttributeError: module 'weeutil.weeutil' has no attribute 'log_traceback'
> Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__: 
>  Exiting.
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Main process exited,
> code=exited, status=1/FAILURE
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
> Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Consumed 1.256s CPU
> time.
>
> What is going on?
>
> --
> 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/9e86020c-1a88-4b0a-b47f-6133c5432b88n%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM21suGsBYrAcQnJBoq1-memkn2kkFpJjdXyF4LV5u-69Gg%40mail.gmail.com.

[weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

['Peter Fletcher' via weewx-user]

I have had weewx 4.x (apt installed) running happily on my Pi 3b for years. 
A month ago, since 5.0 seemed to be stable, I allowed the upgrade to the 
then current release of 5.0. Since there had been a few concerns raised 
about it, I did a complete image backup of the Pi before allowing the 
upgrade. This turned out not to be necessary, since the upgrade essentially 
'just worked', though I did have to deal with the missing private key issue 
that has been discussed elsewhere. This evening, as part of a routine apt 
full-upgrade, , I was updated to 5.02, and the weewx installation appears 
to have been comprehensively clobbered. Sadly, it didn't occur to me to do 
an image backup before a minor update, So I don't have an easy way of going 
back. The initial error appeared to be an access violation to /dev/serial0, 
such as was described in another recent thread with this version of weewx, 
but changing the ownership of the serial port to weewx:weewx only changed 
the problem. systemctl status now reports:
* weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2024-02-20 18:48:39 EST; 
31s ago
   Docs: https://weewx.com/docs
Process: 3348 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=1/FAILURE)
   Main PID: 3348 (code=exited, status=1/FAILURE)
CPU: 1.256s

Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
 callback(event)
Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:    
 File "/etc/weewx/bin/user/crt.py", line 540, in handle_new_loop
Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
 self.handle_data(event.packet)
Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:    
 File "/etc/weewx/bin/user/crt.py", line 563, in handle_data
Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
 weeutil.weeutil.log_traceback('crt:  ')
Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
 AttributeError: module 'weeutil.weeutil' has no attribute 'log_traceback'
Feb 20 18:48:39 bullseyepi weewxd[3348]: CRITICAL __main__:  
 Exiting.
Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Failed with result 
'exit-code'.
Feb 20 18:48:39 bullseyepi systemd[1]: weewx.service: Consumed 1.256s CPU 
time.

What is going on?

-- 
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/9e86020c-1a88-4b0a-b47f-6133c5432b88n%40googlegroups.com.

Re: [weewx-user] Weewx v5 fresh install Errno 13

[vince]

Good it’s working. Weewx used to run as root so a lot of permission 
problems didn’t happen previously.

With the switch to running as a unprivileged user, you need to ensure that 
user can attach to peripherals (your case) or listening ports (some 
interceptor and sdr users) as well as hook it into your webserver properly. 
So it’s a little heavier lift in some situations.

For your situation with /dev/ttyUSB0 adding the user weewx runs as to group 
dialout usually  fixes the issue on a raspi but it really depends on your 
os and which customizations have been done to it.,.

On Tuesday, February 20, 2024 at 3:38:46 PM UTC-8 Jason Patton wrote:

> Hi Vince, et al,
>   Yes, all working well.  I was looking at it, from a device permissions 
> point-of-view.  Software weewx, for some reason, no-longer had rights to, 
> in my case /dev/ttyUSB0 (which has been working for 11 years).  Ownership 
> of the device were set to root:dialout (as are the serial ports).  I saw 
> that weewx was running as user weewx (hmm, don't recall that...).  User 
> weewx was a member of group weewx, so amended the device ownership to: 
> root:weewx.
>
> Cheers, Jason.
>
> On Tuesday 20 February 2024 at 17:10:27 UTC+11 vince wrote:
>
>> Is it working now ? What thoughts are you looking for in particular ?
>>
>> On Monday, February 19, 2024 at 5:47:48 PM UTC-8 Jason Patton wrote:
>>
>>> Hello All,
>>>   After trying to pick-up the pieces of a borked upgrade, I just 
>>> encountered the same 'could not open port /dev/ttyUSB0'.  Entirely possible 
>>> that I've missed documentation somewhere, but is would seem that weewx, is 
>>> now running as usr:grp weewx:weewx (which is where the upgrade script 
>>> borked, setting user permissions)?  My fix was amending permissions on: 
>>> '/dev/ttyUSB0' to: root:weewx, and weewx started fine.  Until, it tried to 
>>> write the HTML, where weewx no-longer had permissions.  Upon granting weewx 
>>> permission to that folder / sub-folders, all seems well.  Thoughts, anyone?
>>>
>>> Best regards, Jason.
>>>
>>> On Sunday 11 February 2024 at 07:36:30 UTC+11 Joseph Verreau wrote:
>>>
 p.p.s I just noticed that I didn't have the subsystem prefix on my 
 rule.  So my entry in 50-localusb.rules is:
 SUBSYSTEM=="tty",ATTRS{serial}=="1344794749", 
 ATTRS{manufacturer}=="Silicon Labs", SYMLINK+="DavisVP"
 and I rebooted; altho I still don't have a symlink for /dev/DavisVP
 all the same my station is back online, submitting reports to all three 
 configured weather services

 On Saturday, February 10, 2024 at 3:22:52 PM UTC-5 Joseph Verreau wrote:

> p.s. just noticed I'm not getting a symlink for the DavisVP rule but I 
> haven't rebooted since I added that local rule.
>
> Joe Verreau
>
> On Saturday, February 10, 2024 at 3:05:41 PM UTC-5 Joseph Verreau 
> wrote:
>
>> hmm.  this seems to be my issue on installing 5.0.0 following erasing 
>> 4.10.  On my own I tried adding weewx user to the wheel group and to 
>> sudoers file.  I tried what Matt and Paul were discussing about rule 
>> changes and yet I still get the "ERROR weewx.engine: Import of driver 
>> failed: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] 
>> Permission 
>> denied:"  When I run as root from command line all seems to be good.
>> Should I do a full report with journal log?
>>
>> Joe Verreau KMIOKEMO13
>> Okemos, MI 
>>
>> On Wednesday, January 31, 2024 at 11:09:41 AM UTC-5 matthew wall 
>> wrote:
>>
>>> On Wednesday, January 31, 2024 at 3:29:36 AM UTC-5 
>>> pshep...@gmail.com wrote:
>>>
>>> Hi Matthew
>>>
>>> Thanks for the information about the various udev folders which 
>>> helps me understand their interaction.
>>>
>>> I created a file /etc/udev/50-localusb.rules and inserted the rule. 
>>> Also, inherited from Linux Mint 20.1 running Weewx 4.8, I also have the 
>>> following line in /etc/udev/descriptive-names.rules
>>>
>>> ATTRS{serial}=="1344794749", ATTRS{manufacturer}=="Silicon Labs", 
>>> SYMLINK+="DavisVP"
>>>
>>> and that SYMLINK is created.
>>>
>>> /usr/lib/udev/rules.d/60-weewx.rules contains 10+ lines for 
>>> different stations and includes the following for Vantage:
>>>
>>> # davis vantage via usb-serial
>>>
>>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>>
>>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTR{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>>
>>> The vantage SYMLINK is not being created.
>>>
>>> Not sure if I should leave 'as is' or edit 60-weewx.rules and remove 
>>> 50-localusb.rules
>>>
>>>
>>> you can keep your 50-localusb.rules.  you might want to consolidate 
>>> the vpro rule in localusb.rules with the vpro rule in 
>>> 

Re: [weewx-user] Weewx v5 fresh install Errno 13

['Jason Patton' via weewx-user]

Hi Vince, et al,
  Yes, all working well.  I was looking at it, from a device permissions 
point-of-view.  Software weewx, for some reason, no-longer had rights to, 
in my case /dev/ttyUSB0 (which has been working for 11 years).  Ownership 
of the device were set to root:dialout (as are the serial ports).  I saw 
that weewx was running as user weewx (hmm, don't recall that...).  User 
weewx was a member of group weewx, so amended the device ownership to: 
root:weewx.

Cheers, Jason.

On Tuesday 20 February 2024 at 17:10:27 UTC+11 vince wrote:

> Is it working now ? What thoughts are you looking for in particular ?
>
> On Monday, February 19, 2024 at 5:47:48 PM UTC-8 Jason Patton wrote:
>
>> Hello All,
>>   After trying to pick-up the pieces of a borked upgrade, I just 
>> encountered the same 'could not open port /dev/ttyUSB0'.  Entirely possible 
>> that I've missed documentation somewhere, but is would seem that weewx, is 
>> now running as usr:grp weewx:weewx (which is where the upgrade script 
>> borked, setting user permissions)?  My fix was amending permissions on: 
>> '/dev/ttyUSB0' to: root:weewx, and weewx started fine.  Until, it tried to 
>> write the HTML, where weewx no-longer had permissions.  Upon granting weewx 
>> permission to that folder / sub-folders, all seems well.  Thoughts, anyone?
>>
>> Best regards, Jason.
>>
>> On Sunday 11 February 2024 at 07:36:30 UTC+11 Joseph Verreau wrote:
>>
>>> p.p.s I just noticed that I didn't have the subsystem prefix on my 
>>> rule.  So my entry in 50-localusb.rules is:
>>> SUBSYSTEM=="tty",ATTRS{serial}=="1344794749", 
>>> ATTRS{manufacturer}=="Silicon Labs", SYMLINK+="DavisVP"
>>> and I rebooted; altho I still don't have a symlink for /dev/DavisVP
>>> all the same my station is back online, submitting reports to all three 
>>> configured weather services
>>>
>>> On Saturday, February 10, 2024 at 3:22:52 PM UTC-5 Joseph Verreau wrote:
>>>
 p.s. just noticed I'm not getting a symlink for the DavisVP rule but I 
 haven't rebooted since I added that local rule.

 Joe Verreau

 On Saturday, February 10, 2024 at 3:05:41 PM UTC-5 Joseph Verreau wrote:

> hmm.  this seems to be my issue on installing 5.0.0 following erasing 
> 4.10.  On my own I tried adding weewx user to the wheel group and to 
> sudoers file.  I tried what Matt and Paul were discussing about rule 
> changes and yet I still get the "ERROR weewx.engine: Import of driver 
> failed: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] 
> Permission 
> denied:"  When I run as root from command line all seems to be good.
> Should I do a full report with journal log?
>
> Joe Verreau KMIOKEMO13
> Okemos, MI 
>
> On Wednesday, January 31, 2024 at 11:09:41 AM UTC-5 matthew wall wrote:
>
>> On Wednesday, January 31, 2024 at 3:29:36 AM UTC-5 pshep...@gmail.com 
>> wrote:
>>
>> Hi Matthew
>>
>> Thanks for the information about the various udev folders which helps 
>> me understand their interaction.
>>
>> I created a file /etc/udev/50-localusb.rules and inserted the rule. 
>> Also, inherited from Linux Mint 20.1 running Weewx 4.8, I also have the 
>> following line in /etc/udev/descriptive-names.rules
>>
>> ATTRS{serial}=="1344794749", ATTRS{manufacturer}=="Silicon Labs", 
>> SYMLINK+="DavisVP"
>>
>> and that SYMLINK is created.
>>
>> /usr/lib/udev/rules.d/60-weewx.rules contains 10+ lines for different 
>> stations and includes the following for Vantage:
>>
>> # davis vantage via usb-serial
>>
>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>
>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTR{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>
>> The vantage SYMLINK is not being created.
>>
>> Not sure if I should leave 'as is' or edit 60-weewx.rules and remove 
>> 50-localusb.rules
>>
>>
>> you can keep your 50-localusb.rules.  you might want to consolidate 
>> the vpro rule in localusb.rules with the vpro rule in 
>> descriptive-names.rules.  or not.  depends on how you like to manage 
>> things.  and your weewx.conf must already refer to 'DavisVP'...
>>
>> if you modify /usr/lib/udev/rules.d/60-weewx.rules, it will be 
>> overwritten when you next upgrade weewx, so just leave it.
>>
>> on your system, is there a /dev/vantage that is a symlink to the 
>> usb-serial adapter?  if so, that indicates the weewx.rules in 
>> /usr/lib/udev 
>> is working.
>>
>> m
>>
>

-- 
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 

Re: [weewx-user] Can no longer run a command with weewx v5

[Tom Keffer]

See the Upgrade Guide, in particular, the section *New location for user
directory
*.

On Tue, Feb 20, 2024 at 12:29 PM Harley Welsh 
wrote:

> I am trying to use *sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/sdr.py cmd="rtl_433 -M utc -F json"* to get the the
> full names of a sensors. When I run the line I get this *error  python:
> can't open file '/usr/share/weewx/user/sdr.py': [Errno 2] No such file or
> directory*  using weewx v5 but before the update it worked fine. Is there
> a new command I could use to get the same output as before?
>
> Thanks,
> Harley
>
>
>
>
> --
> 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/758a80cb-a3d6-4431-8202-218145f4d831n%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/CAPq0zED2AfiRYRBhtvGva1Em_ReF85%2BtHRBEcCQdx0cNAexhwg%40mail.gmail.com.

[weewx-user] Can no longer run a command with weewx v5

[Harley Welsh]

I am trying to use *sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/sdr.py cmd="rtl_433 -M utc -F json"* to get the the 
full names of a sensors. When I run the line I get this *error  python: 
can't open file '/usr/share/weewx/user/sdr.py': [Errno 2] No such file or 
directory*  using weewx v5 but before the update it worked fine. Is there a 
new command I could use to get the same output as before?

Thanks,
Harley




-- 
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/758a80cb-a3d6-4431-8202-218145f4d831n%40googlegroups.com.

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

[vince]

Kostas - if you post your logs when 5.0 crashed it is likely somebody can 
help you.   Make sure to set debug=1 in weewx.conf 

On Tuesday, February 20, 2024 at 7:05:14 AM UTC-8 kostas costas wrote:

> Hi Michael,
>
> Is it possible to give more information about gpg key update and further 
> on? Up to now, i run wh2310 meteo station only with 3.9.2 version. I tried 
> 5.0, it worked for  few minutes and after crashed.
>
> Thank you in advance.
> Kostas
>
> Στις Πέμπτη 8 Φεβρουαρίου 2024 στις 6:37:54 μ.μ. UTC+2, ο χρήστης Michael 
> Waldor έγραψε:
>
>> 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/eabc6928-0a0f-42b5-88ce-17ff2a888cc0n%40googlegroups.com.

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

[kostas costas]

Hi Michael,

Is it possible to give more information about gpg key update and further 
on? Up to now, i run wh2310 meteo station only with 3.9.2 version. I tried 
5.0, it worked for  few minutes and after crashed.

Thank you in advance.
Kostas

Στις Πέμπτη 8 Φεβρουαρίου 2024 στις 6:37:54 μ.μ. UTC+2, ο χρήστης Michael 
Waldor έγραψε:

> 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/f930b0b7-3802-41a6-905d-3f3f4ecfed2cn%40googlegroups.com.