I believe the ‘DMPAFT complete’ message is often misinterpreted as indicating a problem. For most users that see it it is a sign of normal system operation. As Tom said key in interpreting the message is what else is going on around it - classic case showing why we ask users for a longer log extract not just one liners.
The logger operates in a round robin fashion where the oldest archive record is overwritten with the newest. Under normal operation the vantage driver reads archive records from the logger that are timestamped after a given time, typically the last archive record received by WeeWX. The vantage driver reads archive records from the logger accepting archive records that are newer than this given time, this continues until the driver encounters an archive record that is older than this given time(*) - this is key in implementing the ‘catch up’ function - this indicates the end of the round robin buffer has been reached and signals to the driver to stop reading archive records from the logger. In a properly functioning system each successive archive period will see the timestamp of the ‘old’ archive record encountered increment by the logger archive period - exactly what is shown in the log entries below/above. In a system with ‘corrupt station memory’ the same process occurs but no new archive records are found and (usually) the ‘old’ archive record timestamp does not increment each archive period. You will almost always see no archive records being saved to database - because no new archive records were read from the logger(compare this with a properly functioning system where one or more archive records will be saved to archive). In a normal log the lack of archive records being saved to database is the first hint of corrupt station memory; looking at a debug log and noting the timestamps in the ‘DMPAFT complete’ entries is the next clue. It’s worth pointing out this is a debug log event, so even though the ‘DMPAFT complete’ log entry is hit by all vantage users using hardware record generation, it is seldom seen as most users operate with debug = 0. If it was more serious you you’ll likely find it would not be included as a debug level log entry but something more prominent. So in the case above/below the fix (for the ‘DMPAFT complete’ issue) is to simply set debug = 0. No need to clear the station memory. Gary * - actually there is an adjustment for DST as well but for the the purposes of this explanation the simplified approach is adequate On Monday, 13 December 2021 at 16:35:49 UTC+10 vince wrote: > Tom - update. I noticed that the 'page timestamp' keeps walking upward > every interval. > > Think it's time to clear the logger ? > > (from "grep timestamp /var/log/syslog) > Dec 12 21:45:17 debian weewx[12817] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 00:30:00 PST (1638606600) less than > final timestamp 2021-12-12 21:45:00 PST (1639374300) > Dec 12 21:50:18 debian weewx[13726] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 00:35:00 PST (1638606900) less than > final timestamp 2021-12-12 21:50:00 PST (1639374600) > Dec 12 21:55:21 debian weewx[13726] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 00:40:00 PST (1638607200) less than > final timestamp 2021-12-12 21:55:00 PST (1639374900) > Dec 12 22:00:20 debian weewx[13726] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 00:45:00 PST (1638607500) less than > final timestamp 2021-12-12 22:00:00 PST (1639375200) > Dec 12 22:10:20 debian weewx[13726] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 00:55:00 PST (1638608100) less than > final timestamp 2021-12-12 22:10:00 PST (1639375800) > Dec 12 22:15:20 debian weewx[13726] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 01:00:00 PST (1638608400) less than > final timestamp 2021-12-12 22:15:00 PST (1639376100) > Dec 12 22:20:20 debian weewx[13726] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 01:05:00 PST (1638608700) less than > final timestamp 2021-12-12 22:20:00 PST (1639376400) > Dec 12 22:25:21 debian weewx[13726] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-12-04 01:10:00 PST (1638609000) less than > final timestamp 2021-12-12 22:25:00 PST (1639376700) > > > On Sunday, December 12, 2021 at 7:51:29 PM UTC-8 vince wrote: > >> oops => weewx VSS = box's RAM + the amount it's swapping. >> >> Only other thing on the box is nginx which is never getting hit for >> requests, so it's just paged out I guess. Zero load from nginx essentially. >> >> > -- 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/aad7770c-1f02-4961-857f-3e612ac07177n%40googlegroups.com.
