On Thu, 14 Jul 2011, bert hubert wrote:
This issue has been addressed in build 2234 which has just been published on
http://powerdnssec.org/downloads
Can you test?
A quick test here (stopping postgres, ask pdns for an uncached record, get
servfail, restart postgres, ask again) seems to indicate this works.
I patched directly against the version I'm already using (r2191). Since
the bug seems like something of a showstopper, I'm going to push the
patched version into production now as well. I'll report back if anything
odd happens.
Also "luxurious"? That was a very strange commit message. :)
Charles
Thanks to Peter van Dijk for additional debugging.
Bert
On Mon, Jul 11, 2011 at 07:54:59PM +0200, bert hubert wrote:
Hi everybody,
This issues has been turned into a blocker for the 3.0-final release. Could
you open a ticket to that effect on http://wiki.powerdns.com/ ?
Please follow the signup instructions carefully!
Thanks.
Bert
On Sat, Jul 09, 2011 at 05:24:11PM -0400, Charles Sprickman wrote:
On Sat, 9 Jul 2011, Stefan Kaltenbrunner wrote:
On 07/01/2011 02:08 AM, Charles Sprickman wrote:
Hello,
I'm in the middle of testing a new powerdns/postgres setup in native
mode with postgres replication. I've not run into any major issues so
far, but I'm seeing some odd behavior on the last server I setup.
I started powerdns, and after that had stopped and started postgres a
few times to make some config changes. It seems like powerdns is not
dealing with the disappearing postgres process, almost as if the backend
connection has not attempted a reconnect:
Jun 30 19:46:07 ns3 pdns[1569]: Database module reported condition which
prevented lookup (PostgreSQL failed to execute command: FATAL:
terminating connection due to administrator command server closed the
connection unexpectedly This probably means the server terminated
abnormally before or while processing the request. ) sending out
servfail
this indicates that somebody sent the PostgreSQL backend handing the
connection a -TERM signal to drop the connection, this has been caused
in the past by broken linux kernel OOM killers or weird admin scripts
sending random signals to random processes based on memory or cpu usage.
It does not at all seem to relate powerdns directly at all...
Oh, it was certainly me. I had to restart Postgres to pick up some
config changes. The problem I'm having is that until I restart
PowerDNS, it doesn't reconnect when Postgres is again available.
Thanks,
Charles
Stefan
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
