It will definitely help if you'd attach the log files as a whole, it see> ms > the> lo> g ab> ove is not showing all the relevant data. Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:41:33 UTC+1:
> pi@raspberrypi:~ $ apt policy weewx > weewx: > Installed: 5.0.2-1 > Candidate: 5.0.2-1 > > > Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:39:13 UTC+1: > >> here are some more information, something seems to be wrong with the >> gw1000 driver, but I changed nothing: >> >> pi@raspberrypi:~ $ systemctl status weewx* >> ● weewx.service - WeeWX >> Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor >> preset:> >> Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 >> CET; 17mi> >> Docs: https://weewx.com/docs >> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, >> status=4) >> Main PID: 606 (code=exited, status=4) >> CPU: 621ms >> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** >> s> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** >> Fil> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** >> r> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** >> Fil> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** >> r> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** >> user.> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to >> load driv> >> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: **** >> Exiting... >> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process >> exited, cod> >> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result >> 'exit> >> lines 1-18/18 (END)...skipping... >> ● weewx.service - WeeWX >> Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor >> preset: enabled) >> Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 >> CET; 17min ago >> Docs: https://weewx.com/docs >> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, >> status=4) >> Main PID: 606 (code=exited, status=4) >> CPU: 621ms >> >> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:35:25 UTC+1: >> >>> Hello, >>> I use weewx on a raspberry Pi 4. My system crashed and I had to go back >>> to an SD card image from January. It was a state were weewx was runing >>> normally. >>> But now I don't know why weewx is not working anymore. >>> I get no reaction for commands like >>> >>> sudo /etc/init.d/weewx stop >>> sudo /etc/init.d/weewx start >>> >>> debug = 1 and I don't see something in syslog: >>> >>> sudo tail -f /var/log/syslog | grep weewx >>> >>> in January I had a weewx 4 and with apt upgrade I guess I changed to >>> version 5 now but this was not a problem during my last update. >>> >>> Any ideas? Thank you! >>> >>> Regards >>> Thomas >>> >> -- 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/a56838d6-6761-4706-bfc6-3af01b7a303an%40googlegroups.com.
