Re: [Pdns-users] TCP nameserver had error, cycling backend: innodb-read-committed=no

2021-01-12 Thread Peter van Dijk via Pdns-users
Hello, On Sat, 2021-01-09 at 18:26 +0100, Gert van Dijk via Pdns-users wrote: > It seems that this error message is triggered whenever PowerDNS cannot > connect to the database at the first attempt, but it succeeds a second > time. [1] The second time it tries to connect without transaction > isol

Re: [Pdns-users] TCP nameserver had error, cycling backend: innodb-read-committed=no

2021-01-09 Thread Gert van Dijk via Pdns-users
Hi Kevin, It seems that this error message is triggered whenever PowerDNS cannot connect to the database at the first attempt, but it succeeds a second time. [1] The second time it tries to connect without transaction isolation enabled which may suggest that is the cause but that does not seem a c

[Pdns-users] TCP nameserver had error, cycling backend: innodb-read-committed=no

2021-01-09 Thread Kevin via Pdns-users
Dear Community, I am running against an issue i like to fix. So now and then we are getting the following error in the logs: TCP nameserver had error, cycling backend: Unable to launch gmysql connection: Please add '(gmysql-)innodb-read-committed=no' to your PowerDNS configuration, and reconsid