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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/9e86020c-1a88-4b0a-b47f-6133c5432b88n%40googlegroups.com.
