There will be no cycles, because after I issue *[sudo systemctl start weewx*] it **immediately exits**. Therefore no *debug=1 *output. The only thing in syslog is
*Apr 15 21:05:48 PI4B1 systemd[1]: weewx.service: Main process exited, code=exited, status=1/FAILUREApr 15 21:05:48 PI4B1 systemd[1]: weewx.service: Failed with result 'exit-code'.* On Thursday, April 17, 2025 at 2:15:15 PM UTC-5 Karen K wrote: > I am quite sure there is more than just "Main process exited" in > /var/log/syslog. The general procedure to find the reasons of errors is > to set debug=1, then restart WeeWX, then wait for 2 archive cycles if > possible, then inspect /var/log/syslog. > > If one of those files referred within the open() statements do not exist > or the name is misspelled, then WeeWX will crash. May be you can start with > one of those open() statements, commenting out all the others. If you find > no more errors within that statement, you can uncomment the next etc. pp. > > -- 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 visit https://groups.google.com/d/msgid/weewx-user/c249e385-da56-4180-9859-c2876d92e86fn%40googlegroups.com.
