bind9 with dlz-mysql doesn't start at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (CentOS) |
New
|
Undecided
|
Unassigned | ||
bind9 (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: bind9
Description: Ubuntu 10.04 LTS
Release: 10.04
bind9: 1:9.7.0.dfsg.P1-1
There is a problem with bind-dlz/init.d and mysql/upstart
When compiled with dlz-mysql turned on, bind9 requires a running mysqld instance
It turns out that at boot /etc/rc2.d/S15bind9 is started before the upstart/mysql service.
In this way, bind9 fails to start with this error log:
Jun 7 17:57:30 dns2 named[1137]: starting BIND 9.7.0-P1 -u bind
Jun 7 17:57:30 dns2 named[1137]: built with '--prefix=/usr' '--mandir=
Jun 7 17:57:30 dns2 named[1137]: using up to 4096 sockets
Jun 7 17:57:30 dns2 named[1137]: loading configuration from '/etc/bind/
Jun 7 17:57:30 dns2 named[1137]: reading built-in trusted keys from file '/etc/bind/
Jun 7 17:57:30 dns2 named[1137]: using default UDP/IPv4 port range: [1024, 65535]
Jun 7 17:57:30 dns2 named[1137]: using default UDP/IPv6 port range: [1024, 65535]
Jun 7 17:57:30 dns2 named[1137]: listening on IPv4 interface eth0, 192.168.0.2#53
Jun 7 17:57:30 dns2 named[1137]: generating session key for dynamic DNS
Jun 7 17:57:30 dns2 named[1137]: Loading 'Mysql zone' using driver mysql
Jun 7 17:57:30 dns2 named[1137]: mysql driver failed to create database connection after 4 attempts
Jun 7 17:57:30 dns2 named[1137]: SDLZ driver failed to load.
Jun 7 17:57:30 dns2 named[1137]: DLZ driver failed to load.
Jun 7 17:57:30 dns2 named[1137]: loading configuration: failure
Jun 7 17:57:30 dns2 named[1137]: exiting (due to fatal error)
An upstart version of the bind init.d script is needed (with start on started mysql ?)
Thank you,
Roberto Sebastiano
Marking whishlist as the mysql dlz plugin is not compiled by default. One fix is to write up an upstart job for bind9 that will properly depend on mysql for this specific use case.
Writing an upstart job for bind9 may happen in the Maverick time frame. The default upstart job will probably require to be modified to support mysql as this is a non-default setup.