[Pdns-users] pdns with one mysql backend down and one up fails to process queries

[s-tobe]

Hi,

I created a setup with 1 x pdns auth server (3.0.1) and 2 x mysql backends
(IP B1, IP B2)

PDNS agrees to start with one mysql backend dead yet (non responsive) and
one mysql backend operational (responding)  
It shows the following log snippet:
Oct 22 07:47:53 pmnlapp11 pdns[8906]: gmysql Connection successful (must be
IP B1)
Oct 22 07:47:53 pmnlapp11 pdns[8906]: gmysql Connection failed: Unable to
connect to database: Can't connect to MySQL server on '<IP B2> (111)
Oct 22 07:47:53 pmnlapp11 pdns[8906]: Caught an exception instantiating a
backend, cleaning up
Oct 22 07:47:59 pmnlapp11 pdns[8906]: Distributor misses a thread (0<5),
spawning new one

However when launching DNS queries (using host -t A command) to the pdns
server it connects to IP B1 and disconnects again
it does not perform mysql lookup of the applicable records
The host -t A command times out with:
host -t A pmnlapp01 10.130.2.12
;; connection timed out; no servers could be reached

pdns.local contains:
# Here come the local changes the user made, like configuration of
# the several backends that exist.

# gmysql-socket=

# MULTI BACKEND OPERATION, TWO INSTANCES
launch=gmysql,gmysql:connection2


gmysql-connection2-password=...
gmysql-connection2-host=IP B1
gmysql-connection2-user=power_admin
gmysql-connection2-dbname=pdns
gmysql-connection2-dnssec=no

gmysql-password=...
gmysql-host=IP B2
gmysql-user=power_admin
gmysql-dbname=pdns
gmysql-dnssec=no

Questions 1 : why are no queries to the available backend launched, does
pdns need to start with all backends running initially ?
Questions 2 : Will pdns attempt to reconnect to mysql backend that was temp
out of service?
-- 
View this message in context: http://old.nabble.com/pdns-with-one-mysql-backend-down-and-one-up-fails-to-process-queries-tp34587480p34587480.html
Sent from the PowerDNS mailing list archive at Nabble.com.