I fixed the binary log warning by setting the variable to mixed (SET SESSION binlog_format = 'ROW';). Now the syslog is just saying no valid nameservers. Which config part did I make a mistake?
Mar 7 12:47:54 ns3 pdns[2478]: Using 64-bits mode. Built on 20150302135812 by [email protected], gcc 4.7.2. Mar 7 12:47:54 ns3 pdns[2478]: PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2. Mar 7 12:47:54 ns3 pdns[2478]: Polled security status of version 3.4.3 at startup, no known issues reported: OK Mar 7 12:47:54 ns3 pdns[2478]: Listening for HTTP requests on 178.62.193.234:8081 Mar 7 12:47:54 ns3 pdns[2478]: Creating backend connection for TCP Mar 7 12:47:54 ns3 pdns[2478]: Master/slave communicator launching Mar 7 12:47:54 ns3 pdns[2478]: No new unfresh slave domains, 0 queued for AXFR already Mar 7 12:47:54 ns3 pdns[2478]: No master domains need notifications Mar 7 12:47:54 ns3 pdns[2478]: About to create 3 backend threads for UDP Mar 7 12:47:54 ns3 pdns[2478]: Done launching threads, ready to distribute questions Mar 7 12:48:54 ns3 pdns[2478]: 1 domain for which we are master needs notifications Mar 7 12:48:54 ns3 pdns[2478]: Request to queue notification for domain ' test2.com' was processed, but no valid nameservers or ALSO-NOTIFYs found. Not notifying! Mar 7 12:49:54 ns3 pdns[2478]: No master domains need notifications 2015-03-07 18:36 GMT+01:00 Melvin Mughal <[email protected]>: > Having an issue with master-slave configuration. I've used to setup both > following the official installation guide ( > https://doc.powerdns.com/md/authoritative/installation/). The both work > with the standard config and also the API is working. The problem: the > master can't seem to notify the slave. The syslog is displaying some issue > with a query. What piece of my database/config could be causing this? The > settings I changed on both: > > on the master (in pdns.conf): > > > > *allow-axfr-ips=178.62.95.98 (this is the slave server > ip)disable-axfr=nomaster=yes* > > on the slave: > > > *slave=yes* > > *set the supermaster to the master server ip.* > > Here is the syslog of the master server. The slave is ok and reporting no > errors in the syslog (= Done launching threads, ready to distribute > questions): > > *Mar 7 12:19:50 ns3 pdns[27026]: Reading random entropy from > '/dev/urandom'* > > *Mar 7 12:19:50 ns3 pdns[27026]: This is a guarded instance of pdns* > > *Mar 7 12:19:50 ns3 pdns[27026]: UDP server bound to 178.62.193.233:53 > <http://178.62.193.233:53>* > > *Mar 7 12:19:50 ns3 pdns[27026]: TCP server bound to 178.62.193.233:53 > <http://178.62.193.233:53>* > > *Mar 7 12:19:50 ns3 pdns[27026]: PowerDNS Authoritative Server 3.4.3 > ([email protected] <[email protected]>) (C) > 2001-2015 PowerDNS.COM BV* > > *Mar 7 12:19:50 ns3 pdns[27026]: Using 64-bits mode. Built on > 20150302135812 by [email protected] <[email protected]>, > gcc 4.7.2.* > > *Mar 7 12:19:50 ns3 pdns[27026]: PowerDNS comes with ABSOLUTELY NO > WARRANTY. This is free software, and you are welcome to redistribute it > according to the terms of the GPL version 2.* > > *Mar 7 12:19:50 ns3 pdns[27026]: Polled security status of version 3.4.3 > at startup, no known issues reported: OK* > > *Mar 7 12:19:50 ns3 pdns[27026]: Listening for HTTP requests on > 178.62.193.233:8081 <http://178.62.193.233:8081>* > > *Mar 7 12:19:50 ns3 pdns[27026]: Creating backend connection for TCP* > > *Mar 7 12:19:50 ns3 pdns[27026]: Master/slave communicator launching* > > *Mar 7 12:19:50 ns3 pdns[27026]: No new unfresh slave domains, 0 queued > for AXFR already* > > *Mar 7 12:19:50 ns3 pdns[27026]: 1 domain for which we are master needs > notifications* > > *Mar 7 12:19:50 ns3 pdns[27026]: Request to queue notification for domain > 'test.com <http://test.com>' was processed, but no valid nameservers or > ALSO-NOTIFYs found. Not notifying!* > > *Mar 7 12:19:50 ns3 pdns[27026]: Exiting because communicator thread died > with error: GSQLBackend unable to refresh domain_id 6: Failed to execute > mysql_query, perhaps connection died? Err=1: Cannot execute statement: > impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at > least one table uses a storage engine limited to row-based logging. InnoDB > is limited to row-logging when transaction isolation level is READ > COMMITTED or READ UNCOMMITTED.* > > *Mar 7 12:19:50 ns3 pdns[27026]: About to create 3 backend threads for > UDP* > > *Mar 7 12:19:50 ns3 pdns[27026]: Done launching threads, ready to > distribute questions* > > *Mar 7 12:19:51 ns3 mysqld: 150307 12:19:51 [Warning] Aborted connection > 2396 to db: 'powerdns' user: 'powerdns_user' host: 'localhost' (Unknown > error)* > > *Mar 7 12:19:51 ns3 mysqld: 150307 12:19:51 [Warning] Aborted connection > 2398 to db: 'powerdns' user: 'powerdns_user' host: 'localhost' (Unknown > error)* > > *Mar 7 12:19:51 ns3 mysqld: 150307 12:19:51 [Warning] Aborted connection > 2399 to db: 'powerdns' user: 'powerdns_user' host: 'localhost' (Unknown > error)* > > *Mar 7 12:19:51 ns3 mysqld: 150307 12:19:51 [Warning] Aborted connection > 2400 to db: 'powerdns' user: 'powerdns_user' host: 'localhost' (Unknown > error)* > > *Mar 7 12:19:52 ns3 pdns[25864]: Our pdns instance exited with code 0* > > Mar 7 12:19:52 ns3 pdns[25864]: Respawning >
_______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
