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

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

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

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

[Pdns-users] TCP nameserver had error

I have PowerDNS hidden masters (MASTER) managed by PowerAdmin/PowerDNS API using MySQL replication with PowerDNS public slaves that use NOTIFY/AXFR (SLAVE).  Every day or two I get this in my hidden master logs when they have just sent a NOTIFY and the public slave tries to do the AXFR: May 17

Re: [Pdns-users] TCP nameserver had error

On Thu, Jul 24, 2008 at 10:08:40PM +0200, Ronny Wagner wrote: > Logmessage: > Jul 24 17:05:02 sv02 pdns[1]: TCP nameserver had error, cycling > backend: Reading data: Connection reset by peer > What is that for a fail message? It is not very important - a remote nameserver that queried you di

[Pdns-users] TCP nameserver had error

Logmessage: Jul 24 17:05:02 sv02 pdns[1]: TCP nameserver had error, cycling backend: Reading data: Connection reset by peer Jul 24 17:10:02 sv02 pdns[1]: TCP nameserver had error, cycling backend: Reading data: Connection reset by peer Jul 24 17:15:03 sv02 pdns[1]: TCP nameserver had er

RE: [Pdns-users] TCP nameserver had error, cycling backend

ge- From: Daniel Greene - (mt) Media Temple [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2008 10:52 PM To: Eugene Pefti Cc: pdns-users@mailman.powerdns.com Subject: Re: [Pdns-users] TCP nameserver had error, cycling backend Eugene, I can't speak for the first, but: Exception: unkno

Re: [Pdns-users] TCP nameserver had error, cycling backend

, Inc 877 578.4000 x515 - Original Message - From: "Eugene Pefti" <[EMAIL PROTECTED]> To: pdns-users@mailman.powerdns.com Sent: Thursday, June 5, 2008 10:08:39 PM GMT -08:00 US/Canada Pacific Subject: [Pdns-users] TCP nameserver had error, cycling backend Hi folks, What c

[Pdns-users] TCP nameserver had error, cycling backend

Hi folks, What could this error message mean? Jun 5 21:28:53 ns2 pdns[5778]: TCP nameserver had error, cycling backend: Reading data: Connection reset by peer They are numerous indeed. I believe they affect the overall performance. And why would this stats show up in the log: Jun 5 21:44:33 n