Your Ecowitt gateway driver issue is that the driver is unable to contact your gateway device, this is causing WeeWX to exit. This could be due to any number of reasons, it's impossible to say much more without seeing the full log from startup to failure. Refer to the How to get a good, useful log section <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#how-to-get-a-good-useful-log> of the Help! Posting to weewx-user Wiki page <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> for how to get a good log extract. Note that you will likely need to use the instructions for journalctl rather than syslog.
Gary On Saturday 17 February 2024 at 19:58:48 UTC+10 Thomas Hackler wrote: > I am sorry: > > pi@raspberrypi:~ $ systemctl status weewx > ● 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; > 38min 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 > > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** > self.mac = self.get_mac_address() > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** > File "/etc/weewx/bin/user/gw1000.py", line 3625, in get_mac_address > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** > return self.send_cmd_with_retries('CMD_READ_STATION_MAC') > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** > File "/etc/weewx/bin/user/gw1000.py", line 3808, in send_cmd_with_retries > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** > raise GW1000IOError(_msg) > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: **** > user.gw1000.GW1000IOError: Failed to obtain response to command > 'CMD_READ_STATION_MAC' after 3 attempts > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to load > driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 > attempts > > Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: **** > Exiting... > Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process > exited, code=exited, status=4/NOPERMISSION > Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with result > 'exit-code'. > > michael.k...@gmx.at schrieb am Samstag, 17. Februar 2024 um 10:53:49 > UTC+1: > >> 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/819e3ae3-76b7-40f0-8e5b-adc75691d976n%40googlegroups.com.
