package bind9 1:9.6.1.dfsg.P1-3ubuntu0.2 failed to install/upgrade: 子进程 已安装的 post-installation 脚本 返回了错误号 1

[Xiaoqi Zhao]

Binary package hint: bind9

package bind9 1:9.6.1.dfsg.P1-3ubuntu0.2 failed to install/upgrade: 子进程 已安装的 post-installation 脚本 返回了错误号 1

ProblemType: Package
Architecture: i386
Date: Tue Dec 8 09:05:06 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: 子进程 已安装的 post-installation 脚本 返回了错误号 1
Package: bind9 1:9.6.1.dfsg.P1-3ubuntu0.2
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: bind9
Title: package bind9 1:9.6.1.dfsg.P1-3ubuntu0.2 failed to install/upgrade: 子进程 已安装的 post-installation 脚本 返回了错误号 1
Uname: Linux 2.6.31-16-generic i686

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

Could you please attach the file /var/log/daemon.log to this report ?

[Jean-Baptiste Lallement (jibel)]

This is the relevant error
=====
Dec 8 11:10:56 mazda named[7347]: loading configuration from '/etc/bind/named.conf'
Dec 8 11:10:56 mazda named[7347]: /etc/bind/named.conf.local:21: expected quoted string near '“'
Dec 8 11:10:56 mazda named[7347]: loading configuration: unexpected token
Dec 8 11:10:56 mazda named[7347]: exiting (due to fatal error)
=====

If you take a look at message above, you'll see some strange " chars at line 21 of /etc/bind/named.conf.local . Delete the " chars and add them by yourself. It seems that they aren't ASCII chars as they should be.

Tell us if it fix you issue. Thanks.

[Francisco Brasileiro (fvbrasileiro)]

On other logs i was found this message:

09-Dec-2009 17:52:10.167 general: critical: couldn't mkdir '/var/run/named': Permission denied
09-Dec-2009 17:52:10.184 general: critical: exiting (due to early fatal error)

My bind was running on chroot enviroment. After install/upgrade the named.conf.options was change. So, I replace the named.conf.options with dkpg-old and correct permissions on new diretory (oldest is /var/run/bind) and bind is now OK.

[Jean-Baptiste Lallement (jibel)]

@Francisco, this is something completely different than the issue reported here. Please file another report. Thanks.

[Jean-Baptiste Lallement (jibel)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!