bind9 fails to start on precise after clean install

[José A. Calvo]

It is caused by the following error trying to start the bind9 service in postinst:

Setting up bind9 (1:9.8.1.dfsg.P1-1) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
NOT updating named.conf.options to include DNSSEC enablement
 * Starting domain name service... bind9 [fail]
invoke-rc.d: initscript bind9, action "start" failed.

As can be seen in the attached syslog the /etc/bind/named.conf.options is missing.
The package ships a /usr/share/bind9/named.conf.options file but it is not copied to /etc/bind

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.dfsg.P1-1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
Uname: Linux 3.2.0-8-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Jan 15 13:06:22 2012
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Alpha i386 (20120115)
ProcEnviron:
 LC_CTYPE=es_ES.UTF-8
 LC_COLLATE=es_ES.UTF-8
 LANG=en_US.UTF-8
 LC_MESSAGES=es_ES.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 bind9utils 1:9.8.1.dfsg.P1-1
 apparmor 2.7.0-0ubuntu2
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[José A. Calvo (jacalvo)]

Just to clarify this a bit more. It seems it only happens in new installations of bind9, when upgrading from a previously installed version it seems to work. I've also reproduced it on Debian sid (from which this new package was sync'ed) and I've filed the bug #657042 there.

[C de-Avillez (hggdh2)]

Confirmed. Affecting ISO testing:

Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: starting BIND 9.8.1-P1 -u bind
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-D_FORTIFY_SOURCE=2'
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: adjusted limit on open files from 4096 to 1048576
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: found 1 CPU, using 1 worker thread
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: using up to 4096 sockets
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: loading configuration from '/etc/bind/named.conf'
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: /etc/bind/named.conf:9: open: /etc/bind/named.conf.options: file not found
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: loading configuration: file not found
Jan 24 09:25:39 clean-precise-server-amd64 named[1543]: exiting (due to fatal error)

[Jean-Baptiste Lallement (jibel)]

first failure found on ubuntu-server images build 20120121

[Jean-Baptiste Lallement (jibel)]

Please don't change the status without a comment

[Launchpad Janitor (janitor)]

This bug was fixed in the package bind9 - 1:9.8.1.dfsg.P1-2

---------------
bind9 (1:9.8.1.dfsg.P1-2) unstable; urgency=low

  * Deliver named.conf.options on fresh install. Closes: #657042 LP: #920202

 -- LaMont Jones <email address hidden> Wed, 25 Jan 2012 03:55:21 -0700