WEEWX stopped posting to Wunderground and CWOP and can't reestablish

[Bruce Balthaser]

After posting to Wunderground and CWOP for more than a year, WEEWX stopped posting on December 14 without any apparent reason or incident. i tried various solutions to fix the problem and eventually reimaged my zero 2 PI and reloaded the latest version of WEEWX via APT. Still not posting to Wunderground or CWOP.  According to the log (attached), it appears WEEWX is attempting to send data from December 14 to Wunderground and CWOP.  Not sure how that's possible since I reimaged the PI and reloaded WEEWX.

It appears that the Vantage Vue is sending data to WEEWx since files and images are created for the SEASONSREPORT.  i suspect the stale CWOP report and the old Wunderground data are holding up normal reporting. 

Hopefully someone can help resolve this issue.

Bruce Balthaser

[John Smith]

You have multiple problems and it looks like the log output is truncated.

Based on the following error it may mean you may have a corrupt DB file and I don't know how you fix a SQLite DB, but the following link may help
https://sqlite.org/recovery.html

ERROR weewx.manager: Unable to add record 2025-12-14 06:16:00 EST (1765710960) to database 'weewx.sdb': >

Did you change settings from metric to imperial or vice versa or something in the console? Again the logs are truncated so I'm guessing a little

WARNING weewx.qc: 2025-12-14 06:16:00 EST (1765710960) Archive value 'barometer' 62.8 outside limits (26>
WARNING weewx.qc: 2025-12-14 06:16:00 EST (1765710960) Archive value 'inHumidity' 165.0 outside limits (>

--
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 weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/65c002ec-b432-4d00-95d1-9cf8cb4405f7n%40googlegroups.com.

[Tom Keffer]

The problem is with the logger in your station, not WeeWX. Memory corruption of the logger is quite common, but your symptoms don't quite match. You're getting an "unknown archive type" error.

You are also getting unusual values for barometer and inHumidity, but let's worry about those later.

This is not a database problem.

Try clearing the logger. For how to do this, see the wiki guide on Corrupt station memory. 

Let us know how it works out.

-tk