users@mailman.powerdns.com
Subject: Re: [Pdns-users] powerdns authoritative 4.0.0 alpha stops working from
time to time
On Fri, Nov 11, 2016 at 09:33:30AM +, Alejandro Adroher Mellado wrote:
> Hi Oliver,
>
> You are right, I did not because as is happening also on version 4.0.0, It
> had nothi
ocket=/var/lib/mysql/mysql.sock
(caution, might cause problems with your chroot option)
> Anyone has something to add?
>
> Thanks a lot,
> Alejandro.
>
>
>
> -Original Message-
> From: Oliver Peter [mailto:li...@peter.de.com]
> Sent: jueves, 10 de noviembre
From: Oliver Peter [mailto:li...@peter.de.com]
Sent: jueves, 10 de noviembre de 2016 15:37
To: Alejandro Adroher Mellado
Cc: pdns-users@mailman.powerdns.com
Subject: Re: [Pdns-users] powerdns authoritative 4.0.0 alpha stops working from
time to time
Hi Alejandro,
On Thu, Nov 10, 2016 a
rs-boun...@mailman.powerdns.com] On Behalf
> Of Radoslaw Piliszek
> Sent: lunes, 7 de marzo de 2016 13:49
> To: pdns-users@mailman.powerdns.com
> Subject: Re: [Pdns-users] powerdns authoritative 4.0.0 alpha stops working
> from time to time
>
> Hello,
>
> I am having the sa
Pdns-users [mailto:pdns-users-boun...@mailman.powerdns.com] On Behalf Of
Radoslaw Piliszek
Sent: lunes, 7 de marzo de 2016 13:49
To: pdns-users@mailman.powerdns.com
Subject: Re: [Pdns-users] powerdns authoritative 4.0.0 alpha stops working from
time to time
Hello,
I am having the same problem usin
Hi,
I too have ran into this issue today. I can reproduce it easily.
Running 4.0.0~alpha2-1pdns.jessie with the MySQL backend. I restart the
MySQL server. After it is done restarting any queries to PowerDNS return
a SERVFAIL with this line logged first:
Backend reported condition which preve
Hello,
I am having the same problem using PowerDNS Authoritative Server
4.0.0-alpha2 from CentOS 7 repository and the MySQL backend.
I enabled the highest level of logging (9).
And here are the results...
First failed queries (e.g. three times for three connections to the backend):
Remote 127.
Hello,
I finally have some logs when this issue is happening:
Here is what I can find in the logs:
Mar 5 16:57:21 dns1 pdns[7111]: Backend reported condition which prevented
lookup (GSQLBackend lookup query: Attempt to bind more parameters than query
has: SELECT content,ttl,prio,type,domain_
Hello,
I finally have some logs when this issue is happening:
Here is what I can find in the logs:
Mar 5 16:57:21 dns1 pdns[7111]: Backend reported condition which prevented
lookup (GSQLBackend lookup query: Attempt to bind more parameters than query
has: SELECT content,ttl,prio,type,domain_
Just a "fyi" i've expirienced the same behaviour a while ago.
That was on a Ubuntu 14.04LTS system. PDNS works fine after restarting, but i
haven't been able to reproduce the issue.
My config is like this:
allow-dnsupdate-from=127.0.0.0/8,192.168.0.100/32
any-to-tcp=yes
config-dir=/etc/powerdns
d
Hello,
On 26 Feb 2016, at 14:18, Pieter Lexis wrote:
This is the `basic-query`, interesting that it gives this error, as we
never bind more than 2 elements in the code.
Unless there is a code path in which we never reach
try {
d_query_stmt->reset();
} catch (SSqlException &e) {
..
I have enabled the query logging and increased the log level however now I
need to wait for it to happen which should happen in the next two days. That is
the frequency this issue is happening.
By stop working I mean that the powerdns does not send response to the request.
The configuration
Hi Peter,
On Fri, 26 Feb 2016 14:49:16 +0200
Keresztes Péter-Zoltán wrote:
> I have installed the new 4.0 version of the pdns. It works great however from
> time to time it suddenly stops working. In the logs I see lots of these:
By "stops working", do you mean that the process dies or it just
Hello,
I have installed the new 4.0 version of the pdns. It works great however from
time to time it suddenly stops working. In the logs I see lots of these:
Feb 26 07:42:34 dns1 pdns[6514]: Backend reported condition which prevented
lookup (GSQLBackend lookup query: Attempt to bind more param
14 matches
Mail list logo
