.
On Tue, Jan 19, 2021 at 9:39 PM p q wrote:
> I don't know anything, but I can google...
>
> https://stackoverflow.com/questions/311691/importing-a-sqlite3-dump-back-into-the-database
>
>
> On Tue, Jan 19, 2021 at 7:35 PM Kevin Chapman wrote:
>
>> Ok the file com
Ok the file command is showing the backups to be large ASCII files. The
backup command script is using the sqlite3 .dump command. The ascii files
are the SQL commands to rebuild the file. Here is the code.
echo 'stop the weewx daemon and wait 30 seconds'
sudo /usr/sbin/service weewx stop
Hello,
I recently experienced a crash of weewx version 4.2.0. I am still on the
default Sqlite database. I have been backing it up nightly since around
November of last year. Noob mistake is that I assumed the database file
backups were good.
My backup routine consisted of stopping weewx,
/d/msgid/weewx-user/8a08f5b0-73be-43ff-aaca-0ec102e5aa2dn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/8a08f5b0-73be-43ff-aaca-0ec102e5aa2dn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
config_dict)
>>>>
>>>>
>>>>
>>>> # Bind to any new archive record events:
>>>>
>>>> self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)
>>>>
>>>>
>>>>
>>>> *def* new_archive_record(self, event):
>>>>
>>>>
Ok, I am not familiar with Python at all. I managed to work through the
instructions above and make the changes to my weewx.conf file and then
create cputemp.py in my /usr/share/weewx/user directory. This eliminated
the errors in the my syslog. I am not seeing the cpu temp on the charts.
