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, Nevi
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 an
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, Ma
I had neither binlog_format statement in my.conf, using instead the
default, which I think is "STATEMENT".
It works for me with either ROW or MIXED.
My database replication is still broken, but it's late, and I'll worry
about that in a couple of weeks after I get back from vacation. I'll
prob
One more thing – the service (if you’re using Linux) won’t restart after the
error until you STOP it first.
Clay
From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On
Behalf Of Craig Thom
Sent: Sunday, March 12, 2017 8:09 PM
To: weewx-user
Subject: [weewx-user] Re:
Hi, Craig – I had exactly the same issue! I’m actually using MariaDB (the
“real” OpenSource database derived from MySQL).
I fixed it by stopping maria, editing the my.cnf file (/etc/mysql/my.cnf) and
changing the line that read
binlog_format = row
to
binlog_format = mixed
a
