I updated to 3.7.0 and had MySQL bin log_format error and replication
stopped.
I edited the pi my.cnf and added binlog_format=row but I left the NAS
format as mixed.
weewx happy with its config and replication started without a problem.
Nev
On Monday, March 20, 2017 at 6:10:56 AM UTC+10,
I also use replication and am wondering if the issues mentioned here have been
resolved?
My logging is mixed.
I am on weewx 3.6.2 Pi3 and replicate to a QNAP NAS
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group
Something did change. Previously, weewx used transaction isolation level
"READ UNCOMMITTED." Now it uses "READ COMMITTED."
But, according to the error message in your first post, both are limited to
row-based logging, so I don't know why this change would suddenly cause the
error.
-tk
On Sun,
ly have NO idea what that does – that’s tomorrow’s research
> project.
>
>
>
> Clay Jackson
>
>
>
>
>
> *From:* weewx...@googlegroups.com [mailto:
> weewx...@googlegroups.com ] *On Behalf Of *Craig Thom
> *Sent:* Sunday, March 12, 2017 7:48 PM
> *To:* weewx-user <we
ser@googlegroups.com>
Subject: [weewx-user] Re: 3.7.0 with MySQL quitting with database error
3.6.2
I started with the new weewx.conf and made changes one at a time, testing each
one.
Everything is fine until I change
[DataBindings]
[[wx_binding]]
from database = archive_sqlite to archive
ser@googlegroups.com>
Subject: [weewx-user] Re: 3.7.0 with MySQL quitting with database error
I forgot to say I installed initially and upgraded using the .deb package using
apt-get
I saved my old weewx.conf and am now using the new one. I then edited it for
all the personal data and site u
