Petter Reinholdtsen writes: > No idea how to best fix it. pdns can't run both before and after > mysql. Either pdns need to drop the mysql relationship, or mysql need > to drop the $named relationship. The latter might be the best option, > but I leave it to the pdns and mysql maintainers to discuss how to > best order these init.d scripts.
i would like to add that pdns does NOT require that mysql is running when pdns is started. pdns able to connect to mysql when mysql later becomes available (see below for a demo). so could you Matthijs please remove mysql from pdns init script Should lines. it may namely take forever before mysql maintainers fix their init script and remove $named from it. -- juha # /etc/init.d/pdns start Starting PowerDNS authoritative nameserver: Aug 31 22:39:56 localhost pdns[3197]: Listening on controlsocket in '/var/run/pdns.controlsocket' Aug 31 22:39:56 localhost pdns[3197]: Listening on controlsocket in '/var/run/pdns.controlsocket' Aug 31 22:39:56 localhost pdns[3200]: Guardian is launching an instance Aug 31 22:39:56 localhost pdns[3200]: Guardian is launching an instance Aug 31 22:39:56 localhost pdns[3200]: Reading random entropy from '/dev/urandom' Aug 31 22:39:56 localhost pdns[3200]: Reading random entropy from '/dev/urandom' Aug 31 22:39:56 localhost pdns[3200]: This is module gmysqlbackend.so reporting Aug 31 22:39:56 localhost pdns[3200]: This is module gmysqlbackend.so reporting Aug 31 22:39:56 localhost pdns[3200]: This is a guarded instance of pdns Aug 31 22:39:56 localhost pdns[3200]: This is a guarded instance of pdns Aug 31 22:39:56 localhost pdns[3200]: It is advised to bind to explicit addresses with the --local-address option Aug 31 22:39:56 localhost pdns[3200]: It is advised to bind to explicit addresses with the --local-address option Aug 31 22:39:56 localhost pdns[3200]: UDP server bound to 0.0.0.0:53 Aug 31 22:39:56 localhost pdns[3200]: UDP server bound to 0.0.0.0:53 Aug 31 22:39:56 localhost pdns[3200]: TCP server bound to 0.0.0.0:53 Aug 31 22:39:56 localhost pdns[3200]: TCP server bound to 0.0.0.0:53 Aug 31 22:39:56 localhost pdns[3200]: PowerDNS 2.9.22 (C) 2001-2009 PowerDNS.COM BV (Aug 6 2010, 11:14:21, gcc 4.4.5 20100728 (prerelease)) starting up Aug 31 22:39:56 localhost pdns[3200]: PowerDNS 2.9.22 (C) 2001-2009 PowerDNS.COM BV (Aug 6 2010, 11:14:21, gcc 4.4.5 20100728 (prerelease)) starting up Aug 31 22:39:56 localhost pdns[3200]: 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. Aug 31 22:39:56 localhost pdns[3200]: 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. Aug 31 22:39:56 localhost pdns[3200]: DNS Proxy launched, local port 33702, remote 127.0.0.1:54 Aug 31 22:39:56 localhost pdns[3200]: DNS Proxy launched, local port 33702, remote 127.0.0.1:54 Aug 31 22:39:56 localhost pdns[3200]: Creating backend connection for TCP Aug 31 22:39:56 localhost pdns[3200]: Creating backend connection for TCP Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: Launched webserver on 127.0.0.1:8081 Aug 31 22:39:56 localhost pdns[3200]: Launched webserver on 127.0.0.1:8081 Aug 31 22:39:56 localhost pdns[3200]: TCP server is unable to launch backends - will try again when questions come in: Unable to launch gmysql connection: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: TCP server is unable to launch backends - will try again when questions come in: Unable to launch gmysql connection: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: About to create 3 backend threads for UDP Aug 31 22:39:56 localhost pdns[3200]: About to create 3 backend threads for UDP Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: gmysql Connection failed: Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (111) Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: Caught an exception instantiating a backend, cleaning up Aug 31 22:39:56 localhost pdns[3200]: Done launching threads, ready to distribute questions Aug 31 22:39:56 localhost pdns[3200]: Done launching threads, ready to distribute questions started # /etc/init.d/mysql start Starting MySQL database server: mysqldAug 31 22:40:07 localhost mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Aug 31 22:40:07 localhost mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 [Note] Plugin 'FEDERATED' is disabled. Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 [Note] Plugin 'FEDERATED' is disabled. Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 InnoDB: Started; log sequence number 0 9127733 Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 InnoDB: Started; log sequence number 0 9127733 Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 [Note] Event Scheduler: Loaded 0 events Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 [Note] Event Scheduler: Loaded 0 events Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 [Note] /usr/sbin/mysqld: ready for connections. Aug 31 22:40:07 localhost mysqld: Version: '5.1.49-1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian) Aug 31 22:40:07 localhost mysqld: 100831 22:40:07 [Note] /usr/sbin/mysqld: ready for connections. Aug 31 22:40:07 localhost mysqld: Version: '5.1.49-1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian) . Checking for corrupt, not cleanly closed and upgrade needing tables.. Aug 31 22:40:08 localhost /etc/mysql/debian-start[3391]: Upgrading MySQL tables if necessary. Aug 31 22:40:08 localhost /etc/mysql/debian-start[3391]: Upgrading MySQL tables if necessary. Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: Looking for 'mysql' as: /usr/bin/mysql Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: Looking for 'mysql' as: /usr/bin/mysql Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: This installation of MySQL is already upgraded to 5.1.49, use --force if you still need to run mysql_upgrade Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Aug 31 22:40:08 localhost /etc/mysql/debian-start[3394]: This installation of MySQL is already upgraded to 5.1.49, use --force if you still need to run mysql_upgrade Aug 31 22:40:08 localhost /etc/mysql/debian-start[3401]: Checking for insecure root accounts. Aug 31 22:40:08 localhost /etc/mysql/debian-start[3401]: Checking for insecure root accounts. Aug 31 22:40:08 localhost /etc/mysql/debian-start[3405]: Triggering myisam-recover for all MyISAM tables Aug 31 22:40:08 localhost /etc/mysql/debian-start[3405]: Triggering myisam-recover for all MyISAM tables # host www.debian.org 127.0.0.1 Aug 31 22:40:54 localhost pdns[3200]: gmysql Connection succesful Aug 31 22:40:54 localhost pdns[3200]: gmysql Connection succesful Using domain server: Name: 127.0.0.1 Address: 127.0.0.1#53 Aliases: www.debian.org has address 141.76.2.5 www.debian.org has address 194.109.137.218 www.debian.org has address 213.129.232.18 www.debian.org has IPv6 address 2001:888:2000:12::2 www.debian.org has IPv6 address 2001:858:2:1::10 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
