On Sunday, December 12, 2021 at 4:19:33 PM UTC-8 Tom Keffer wrote: > 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. > > Pot. Kettle .Black. Moi ? - Guilty as charged, sir :-)
I guess I was trying to get a feel for "occasionally seeing this or that" is not that unusual nor necessarily actionable if everything else works ok. But to answer - everything seems to be working ok. The db is getting updated just fine, as are the web pages and images. All the extensions posting to WU/PWS/CWOP and the MQTT stuff (publish and subscribe) are working fine too. I've attached a gzipped syslog from a restart of weewx and a couple cycles afterward. Typically the rsync stuff completes last, so I added a blank line between cycles to make this a little easier to parse. I did notice a api key error in my forecast setup (fixed) so the initial startup might be a little longer than normal since the forecast stuff had to catch up. Timings for subsequent runs look normal for here - a little over 3 minutes til the rsync stuff ends a 5-minute archive set of stuff... -- 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/61b8a4db-7ee4-4449-9fcc-7780f1775078n%40googlegroups.com.
syslog.txt.gz
Description: GNU Zip compressed data
