You could try using wee_device --dump <http://weewx.com/docs/hardware.htm#vantage_dumping_the_logger_memory>. It will dump all the records in the logger. Most will be duplicates, but it will recover the missing records. Then rebuild the daily summaries.
On Tue, Feb 26, 2019 at 7:32 AM Greg Troxel <[email protected]> wrote: > I have a weewx installation with Davis serial. It's been running > reliably for over a year, and I just updated to 3.9 after following git > master for a while. (I don't think 3.9 has anything to do with my > issues.) > > My computer is an RPI3 running netbsd-8, with a USB/serial adaptor, > going to an official Davis weatherlink in a VP2. I don't think this is > all that relevant either. The console has batteries, and the computer, > for no good reason, does not have backup power. > > We had a power failure around 2pm (you may have seen the wind reports in > New England yesterday). The power came back, and I had some mess with > access point and DHCP server state, resolved in not too long. > > First I made a database backup. > > weewx correctly grabbed the archive records from the outage and all > seemed ok. Later, around 8pm, the computer seemed to be locked up > (unusual), and I power cycled it. It came up and started generating > reports, but I noticed that an hour roughly 7-8 pm was missing on > graphs. I looked at the timestamps in the archive table, and sure > enough those were missing too. > > I assumed that somehow once an archive record was missing the code to > get new archives from station would not fill them in. > > I then dropped the archive records that were past the gap. weewx would > then not start due to the lastInterval (from memory; perhaps wrong) > record in summary metadata being after the last archive entry. > > I started to write this note, and then started to think about dropping > all of the post-gap daily archive table entries and resetting the > lastInterval, when I rememembered that trouble with daily summaries is > not so unusual and that they can just be regenerated, so I found > wee_database. > > "wee_database --check" reported no errors. This seems like a bug > because weewx itself errors out. > > I then ran "wee_database --drop-daily". > > Then, starting weewx gave me a few minutes of summary rebuilding, and > appears to run ok. > > But, I still have a gap, and the log shows the first REC as 20:10, which > I am pretty sure was the first post-gap record. But all the overnight > data looks right. > > So perhaps my console flaked, and the missing records really are > missing? > > I am curious if anybody else has experienced this. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
