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,
"Mostly the problem is situated between the chair and the screen." I should
read the documentation more carefully.
$day and $yesterday need some aggregation. So it is *not possible* to write
$day.GTS or $yesterday.GTS because the aggregation type is missing. Instead
it is necessary to write
Hi Jan-Jaap,
seems to work! I made two local changes: 1.) I removed the
@property
def archive_interval(self):
return 60
And changed the logging of "Import from UDP" to debug level. The driver
works now for me, the last thing on the wishlist would bei to let
genStartupRecords
To show a value for yesterday, the value would have to be in the database.
On Sun, Feb 14, 2021 at 10:29 AM Karen K wrote:
> Oh, so I mixed it up some way. I registered the XType as a service.
>
> Now there are two different classes, and that looks a lot better. The
> extension calculates the
Oh, so I mixed it up some way. I registered the XType as a service.
Now there are two different classes, and that looks a lot better. The
extension calculates the values and draws a graph. Thank you for your
advice. It saved a lot of time.
$current.GTS displays a value now. $day.GTS and
I meant the 670. I've got a pi3 I'm going to use.
On Saturday, February 13, 2021 at 12:14:39 PM UTC-7 ral...@gmail.com wrote:
> I considered an external timer as a solution for the ESP8266, but decided
> to use one of the "old" RPi 3 that were sitting on the workbench.
>
> Is the Eno
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.
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
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
