Vince, you should know better! That's not much of a log excerpt. What was before that DMPAFT log entry? Did weewx put something in the database? If not, that looks like a classic case of memory corruption.
As for the LOOP errors, I see those every once in a while, particularly when the logger is busy after a large catch up. Again, more of the log would help. -tk On Sun, Dec 12, 2021 at 12:11 PM vince <[email protected]> wrote: > Looking for thoughts.... > > I see this every archive period.... > > Dec 12 08:15:21 debian weewx[30827] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-03 11:00:00 PST (1638558000) less than > final timestamp 2021-12-12 08:15:00 PST (1639325700) > > Given that 9 day offset is pretty close to the point in time where old > records should roll off the logger's memory, should I just leave it alone > for a few days and see if it goes away ? Logger is over 10 years old and > has never been cleared/reset. > > Dec 12 02:18:58 debian weewx[30827] ERROR weewx.drivers.vantage: LOOP try > #1; error: Expected to read 99 chars; got 0 instead > Dec 12 02:19:01 debian /USR/SBIN/CRON[4840]: (root) CMD (scp > /home/weewx/public_html/current.html pi:/mnt/ramdisk/current.html) > Dec 12 02:19:03 debian weewx[30827] ERROR weewx.drivers.vantage: LOOP try > #2; error: Expected to read 99 chars; got 0 instead > Dec 12 02:19:08 debian weewx[30827] ERROR weewx.drivers.vantage: LOOP try > #3; error: Expected to read 99 chars; got 0 instead > Dec 12 02:19:13 debian weewx[30827] ERROR weewx.drivers.vantage: LOOP try > #4; error: Expected to read 99 chars; got 0 instead > Dec 12 02:19:13 debian weewx[30827] ERROR weewx.drivers.vantage: LOOP max > tries (4) exceeded. > Dec 12 02:19:13 debian weewx[30827] INFO weewx.engine: Main loop exiting. > Shutting engine down. > Dec 12 02:19:13 debian weewx[30827] DEBUG weewx.restx: Shut down MQTT > thread. > Dec 12 02:19:13 debian weewx[30827] DEBUG weewx.restx: Shut down CWOP > thread. > Dec 12 02:19:13 debian weewx[30827] DEBUG weewx.restx: Shut down > PWSWeather thread. > Dec 12 02:19:13 debian weewx[30827] DEBUG weewx.restx: Shut down > Wunderground-PWS thread. > Dec 12 02:19:13 debian weewx[30827] DEBUG weewx.restx: Shut down > StationRegistry thread. > Dec 12 02:19:13 debian weewx[30827] INFO user.MQTTSubscribe: (Service) > Disconnected with result code 0 > Dec 12 02:19:13 debian weewx[30827] CRITICAL __main__: Caught > WeeWxIOError: Max tries exceeded while getting LOOP data. > Dec 12 02:19:13 debian weewx[30827] CRITICAL __main__: **** Waiting > 60 seconds then retrying... > Dec 12 02:20:01 debian /USR/SBIN/CRON[4844]: (root) CMD (scp > /home/weewx/public_html/current.html pi:/mnt/ramdisk/current.html) > Dec 12 02:20:13 debian weewx[30827] INFO __main__: retrying... > Dec 12 02:20:14 debian weewx[30827] INFO __main__: Using configuration > file /home/weewx/weewx.conf > Dec 12 02:20:14 debian weewx[30827] INFO __main__: Debug is 1 > Dec 12 02:20:14 debian weewx[30827] DEBUG __main__: Initializing engine > > Looking at the 'wake up' messages in syslog, I see about 40% rude vs. 60% > gentle wake ups, if that matters. A few LOOP CRC errors in the past week > but just a handful. > > Or should I start thinking about putting weewx on a far faster box ? It > does work pretty hard running Belchertown and a variety of other things but > everything fits easily in the 5-minute archive window. Worst case I've > seen is everything taking 3:22 to complete. > > > -- > 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/788d7dfb-b8f3-4639-be16-66528f03ffafn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/788d7dfb-b8f3-4639-be16-66528f03ffafn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPq0zEBFqPcW33VC-6mctY2hcd9DaEM_S%3D2TQOaXyGsA4i2H5A%40mail.gmail.com.
