Still getting station registry error Oct 10 14:30:20 RPi3 weewx[687]: restx: StationRegistry: Failed to publish record 2017-10-10 14:30:00 EEST (1507635000): FAIL: execute failed: database disk image is malformed
On Wednesday, 4 October 2017 07:07:26 UTC+3, Andrew Milner wrote: > Had the station registry error yesterday: > > upload errors: > Oct 3 06:15:46 RPi3 weewx[687]: restx: Wunderground-PWS: Failed to > publish record 2017-10-03 06:15:00 EEST (1507000500): Failed upload after 3 > tries > Oct 3 14:30:46 RPi3 weewx[687]: restx: StationRegistry: Failed to > publish record 2017-10-03 14:30:00 EEST (1507030200): FAIL: execute failed: > database disk image is malformed > > > On Monday, 2 October 2017 22:02:55 UTC+3, Messy Potamia wrote: > >> Aw shoot, I just posted nearly the same exact problem, then I read this. >> --MP >> >> On Sunday, October 1, 2017 at 6:05:45 PM UTC-5, Paul Anderson wrote: >>> >>> I noticed this in my stations weewx.log >>> >>> >>> Oct 1 17:50:15 webserver weewx[10004]: restx: StationRegistry: Failed to >>> publish record 2017-10-01 17:50:00 EDT (1506894600): FAIL: execute failed: >>> database disk image is malformed >>> >>> >>> Because the error referred to a database disk image being malformed , I >>> thought it was referring to my local Sqlite weewx.sdb. After researching on >>> SqLite database corruption issues, I learned how this sometimes happens >>> especial on SD cards such as used with the PI and on SSD drives. Because I >>> am running on a SSD drive I went though the steps of doing a .dump to a >>> file, then recreated the database from the backup file. When I opened the >>> “new” database with sqlite3 tool I checked it’s integrity with PRAGMA >>> integrity_check. The integrity_check pragma looks for out-of-order records, >>> missing pages, malformed records, missing index entries, and UNIQUE, CHECK, >>> and NOT NULL constraint errors. >>> >>> It returned OK, so it thinks the database is fine. >>> >>> >>> Moved the “new database” back into place , ran the checks that wee-data >>> base provides , did a rebuild-daily and restated weewx, and got the same >>> StationRegistry: Failed to publish error. >>> >>> >>> The more I look at this issue I am starting to believe that it’s not a >>> issue with my local weewx.sdb at all, but rather an issue with the Station >>> Registry database on THE WEEWX SERVER. >>> >>> >>> I believe the error is actually a server reply from register.cgi on the >>> weewx.com server. >>> >>> Most likely from here: >>> >>> $rc = >>> $sth->execute($rec{station_url},$rec{description},$rec{latitude},$rec{longitude},$rec{station_type},$rec{station_model},$rec{weewx_info},$rec{python_info},$rec{platform_info},$rec{last_addr},$rec{last_seen}); >>> >>> if(!$rc) { >>> >>> my $msg = 'execute failed: ' . $DBI::errstr; >>> >>> $dbh->disconnect(); >>> >>> return ('FAIL', $msg, \%rec); >>> >>> } >>> >>> >>> Also it’s very interesting to note that no North America station have >>> been updated after Fri, 29 Sep 2017 10:56:51 GMT. >>> >>> So my WILD SPECULATION is that the weewx.com site maybe run on at least >>> a couple of servers, and EUROPE may be OK, but North America has a bad >>> Station Registry database? >>> >>> >>> Thanks, >>> >>> Paul >>> >> -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.