[weewx-user] Re: table archive_day_barometer already exists

Phil (and anyone else interested), The script is now written and I have spent most of the day testing it. It has currently been running for about three hours now and seems to be running correctly. I'm attaching the script and a set of instructions on how to configure and run it. The script

[weewx-user] Re: table archive_day_barometer already exists

Phil, No problem. Just starting it now and as soon as it's done and tested, I'l post a copy. Dave On Wednesday, December 12, 2018 at 3:43:46 PM UTC-6, kutz...@gmail.com wrote: > > I'd appreciate you sharing a copy of the script with me after you write > it. > -- You received this message

[weewx-user] Re: table archive_day_barometer already exists

Phil, One of the things I will be implementing in my new backup strategy is a check to make sure the database isn't corrupted. This can be done using command line parameters to sqlite3. When run manually, it looks something like: pi@Weather:~ $ sqlite3 weewx.sdb 'pragma integrity_check' ok

[weewx-user] Re: table archive_day_barometer already exists

Gary, The backup strategy I use is a Python script I wrote that is started by cron every night. I had read that there could be a problem if the database is copied while it's being updated. The database is updated once a minute by weeWX so the script monitors the mtime of the weewx.sdb file,

[weewx-user] Re: table archive_day_barometer already exists

Gary - I am in your debt. The --reconfigure option seems to have done the trick. It took a while to generate the new file but, once it was done, weeWX was able to accept the database. It then spend another large chunk of time rebuilding the daily summaries and, once that was done, it started

[weewx-user] Re: table archive_day_barometer already exists

Thanks to you both for your suggestions. Gary, I followed your instructions with the following results: 1) Stopped weeWX and verified in /var/log/syslog that it was stopped 2) Used the wee_database utility to drop the daily summaries. The system responded with: Dropping daily summary tables

[weewx-user] table archive_day_barometer already exists

Over the past year I've had numerous cases of a corrupted database. I learned early on to have a good backup scheme in place and it has served me well - up until today. After I noticed that the web page was no longer updating I checked the /var/sys/logfile and found the message

Re: [weewx-user] weewx not starting after reboot (manual intervention necessary)

On Friday, September 22, 2017 at 11:42:32 PM UTC-5, Andrew Milner wrote: > > I think it has started when wifi network was up rather than Ethernet > network. Did you set wait for network in raspi-config - which is the RPi > method of ensuring network is available while booting. > >> >> Thanks

Re: [weewx-user] weewx not starting after reboot (manual intervention necessary)

On Friday, September 22, 2017 at 9:25:58 PM UTC-5, Tom Keffer wrote: > > Sorry. The WLIP logger is a common nickname for the Davis "WeatherLink IP > logger". Like this > . > > I'm officially embarrassed - apparently I was

Re: [weewx-user] weewx not starting after reboot (manual intervention necessary)

On Friday, September 22, 2017 at 9:11:19 PM UTC-5, Tom Keffer wrote: > > > One question: I assume you have the WLIP version of the Vantage logger? > > I'm just starting to transition from Windows to Linux and still have a lot to learn. For example, I don't know what the Vantage logger is or

[weewx-user] weewx not starting after reboot (manual intervention necessary)

A couple of days ago I switched from a Windows 7 system running Weatherlink to a Raspberry Pi 3B running weewx under the jessie distribution. Once running, the program works great but there is one problem I must solve and I'm not sure how to do it. If the Pi reboots weewx does not start