Hi all,
Hate to pester, but I'd love to know whether this behavior is a bug or a
feature. :)
Thanks,
Charles
On Thu, 30 Jun 2011, 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
I got a few of those (accompanied with a servfail response), and then this
log line repeats:
Jun 30 19:46:07 ns3 pdns[1569]: Database module reported condition which
prevented lookup (PostgreSQL failed to execute command: unknown reason)
sending out servfail
If I repeat the dns query, I get an answer about 2 out of 5 tries, perhaps
because one backend connection is properly connected and the others are not.
After a restart of powerdns, the issue goes away.
This is 3.0.20110509 of powerdns with PostgreSQL 9.0.4.
I also am still seeing the issue of the "loglevel=" config not seeming to
have an effect on the logging verbosity (currently set to 8, but the logs
seem pretty minimal).
Thanks,
Charles
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
