After upgrading 4.8.0 to 4.9.1 my pi4 setup is seeing continual engine reboots due to "Caught WeeWxIOError: Max tries exceeded while getting archive data".
System is a VP2 connected to a pi4 via serial2usb connector that has worked for years. The hardware is good and was last touched over 60 days ago when I moved my setup to the pi4. Of note is when I flip back to 4.8.0 without touching hardware, there is no issue any more. It only appeared when I did an upgrade to 4.9.1 here. Some debug output from the logs.... Oct 26 12:50:16 pi4 weewx[6751] DEBUG weewx.drivers.vantage: Getting archive packets since 2022-10-26 12:45:00 PDT (1666813500) Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: DMPAFT try #1; error: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] DEBUG weewx.drivers.vantage: Getting archive packets since 2022-10-26 12:45:00 PDT (1666813500) Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: DMPAFT try #2; error: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] DEBUG weewx.drivers.vantage: Getting archive packets since 2022-10-26 12:45:00 PDT (1666813500) Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: DMPAFT try #3; error: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] DEBUG weewx.drivers.vantage: Getting archive packets since 2022-10-26 12:45:00 PDT (1666813500) Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: DMPAFT try #4; error: Unable to wake up Vantage console Oct 26 12:50:17 pi4 weewx[6751] ERROR weewx.drivers.vantage: DMPAFT max tries (4) exceeded. Oct 26 12:50:17 pi4 weewx[6751] INFO weewx.engine: Main loop exiting. Shutting engine down. Oct 26 12:50:17 pi4 weewx[6751] DEBUG weewx.restx: Shut down MQTT thread. Oct 26 12:50:18 pi4 weewx[6751] DEBUG weewx.restx: Shut down CWOP thread. Oct 26 12:50:18 pi4 weewx[6751] DEBUG weewx.restx: Shut down PWSWeather thread. Oct 26 12:50:18 pi4 weewx[6751] DEBUG weewx.restx: Shut down Wunderground-PWS thread. Oct 26 12:50:18 pi4 weewx[6751] DEBUG weewx.restx: Shut down StationRegistry thread. Oct 26 12:50:18 pi4 weewx[6751] INFO user.MQTTSubscribe: (Service) Disconnected with result code 0 Oct 26 12:50:18 pi4 weewx[6751] CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting archive data. Oct 26 12:50:18 pi4 weewx[6751] CRITICAL __main__: **** Waiting 60 seconds then retrying... I also noted the following: Oct 26 12:51:19 pi4 weewx[6751] INFO __main__: Starting up weewx version 4.9.1 Oct 26 12:51:19 pi4 weewx[6751] DEBUG weewx.drivers.vantage: Gentle wake up of console successful Oct 26 12:51:19 pi4 weewx[6751] DEBUG weewx.manager: Daily summary version is 4.0 Oct 26 12:51:19 pi4 weewx[6751] INFO weewx.engine: Clock error is 4.45 seconds (positive is fast) So what I'm wondering (wild guess mode) is if there's a timing thing going on. If the clock error is 4.45 seconds is this enough to cause these kinds of errors ? Again, flipping back to 4.8.0 results in a 100% working system. It's the 4.9.1 update that caused the issue to appear... Ideas ? -- 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/4790e51b-091f-4a26-9fc8-ad8aa6688af6n%40googlegroups.com.
