The MySQL server may be the trigger but not the actual problem.
Some time ago it used to be the case on my system that Weewx would exit
whenever the MySQL server was restarted, such as during an upgrade.
My recollection was that weewx was changed to try harder to restart under
these conditions, s
Well, I used to run as daemon since the beginning as it is suggested in the
docs.
But I found that errors and exception do not go in messages in my setup. I
ran weewx from the command line at one point in time, and saw that way more
info was coming on the output, as well as stack traces.
That'
I don’t know about anyone else but I’m confused. Why run WeeWX directly
with redirected stderr and WeeWX logging to syslog when you can run WeeWX
as a daemon and have the whole lot go to syslog. That way you have the
whole story chronologically timestamped in one place, the syslog. If it is
imp
Hi,
Thank you for the information. I looked into tonight's log and sure enough
the issue happened, but my weewx did not fully crash because the exception
was properly trapped this time.
So there were 2 crashes : 1 at 2:57 and 1 à 3:00. These are the start time
for the backup tasks that apply
If the database is myisam format that could cause it to fail to write during
backups.
I personally shut down weewx nightly to do my backups just so I get a clean
backup. So you may want to have weewx shutdown just before your backup job
kicks off then start back up again.
> On Feb 13, 2021,
Looks pretty clear that the issue is WeeWX losing its connection to the
MySQL server. WeeWX will be wanting database access each time it saves
records to database (every archive interval seconds) and every report cycle
but I don't see WeeWX doing anything to cause the error.
I guess only you kn
To be complete , the log from messages :
Feb 13 02:58:10 weatherpi /weewxd: PiSense: Pressure :1000.5552978515625
Feb 13 02:58:11 weatherpi /weewxd: PiSense: Lux:0.0
Feb 13 02:58:24 weatherpi /weewxd: PiSense: Pressure :1000.66787109375
Feb 13 02:58:25 weatherpi /weewxd: PiSense: Lux:0.0
Feb 13 02
Hi,
Ok I can try that.
I am running weewx 4.3.0 installed with setup.py.
I have a SDR with weewx SDR driver and a custom extension derived from a
BME280 extension that will inject some extra measures in the measure loop.
Regarding logs, even though I set debug=1, i find only minimal info in
me
Hi,
Probably easiest if you post a log extract showing the lead up to a failure
and the actual error trace. Also what version of WeeWX are you running and
is WeeWX running under python 2 or python 3?
Gary
On Sunday, 14 February 2021 at 03:39:13 UTC+10 sbar...@gmail.com wrote:
> Hi,
>
> My Wee
