My recollection is that abnormal code 4 is when it can't connect to the USB. I can replicate the error by stopping weewx, unplugging the USB and starting it back up. With KeepAlive on , if i plug the device back in, it connects and behaves just like the startup. Not positive, but my best guess is that weewx is trying to load before the USB data logger (SLAB_UART) is available or for some reason it becomes temporarily unavailable after initial load. Since weewx dies immediately, I think it is likely that the USB is never seen. Thoughts on how to make the process wait for the USB logger to become available before loading up weewx? The fact that it also only does the KeepAlive cycle once at startup and then merrily works further supports this hypothesis.
-Geoff On Monday, March 16, 2020 at 12:17:54 PM UTC-7, mwall wrote: > > On Monday, March 16, 2020 at 3:00:17 PM UTC-4, Geoff Harris wrote: >> >> Problem solved for now. Perhaps the plist for launchd should be updated >> to include KeepAlive? >> > > geoff, > > KeepAlive is definitely NOT something we want in a default installation. > KeepAlive (and whatever the equivalent is for systemd) is a band-aid, not a > cure. > > the solution is to fix whatever is terminating the weewx process. > > 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 https://groups.google.com/d/msgid/weewx-user/e518b157-12eb-430f-a731-00afbda100d3%40googlegroups.com.
