package bind9 1:9.6.1.dfsg.P1-3 failed to install/upgrade:

[j(/)rn]

Binary package hint: bind9

I did a do-release-upgrade -d on a pretty fresh install of jaunty.

Setting up bind9 (1:9.6.1.dfsg.P1-3) ...
 * Stopping domain name service... bind9 rndc: connection to remote host closed
This may indicate that
* the remote server is using an older version of the command protocol,
* this host is not authorized to connect,
* the clocks are not synchronized, or
* the key is invalid.

ProblemType: Package
Architecture: amd64
Date: Fri Oct 23 02:41:36 2009
DistroRelease: Ubuntu 9.10
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script killed by signal (Interrupt)
Package: bind9 1:9.6.1.dfsg.P1-3
ProcVersionSignature: Ubuntu 2.6.28-15.52-server
SourcePackage: bind9
Title: package bind9 1:9.6.1.dfsg.P1-3 failed to install/upgrade:
Uname: Linux 2.6.28-15-server x86_64
XsessionErrors:
 (gnome-settings-daemon:6090): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:6090): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-panel:6099): libglade-WARNING **: Unexpected element <requires-version> inside <glade-interface>.

[Chuck Short (zulcss)]

Hi,

Please include your /var/log/daemon.log.

Thanks
chuck

[j(/)rn (jorn-nydahl-gmail)]

Updating bind9 with update-manager worked fine after a reboot, but here is the file anyway :)

[j(/)rn (jorn-nydahl-gmail)]

Please disregard my previous message and attachment. That was the daemon.log from my desktop computer.

The daemon.log.1 file on the server, which I was upgrading, is over 30 m. So if you still want it I can pull out the stuff you want from it and post only that. Please let me know what to do.

[Chuck Short (zulcss)]

Can you try to grep the relevant lines for bind?

Thanks
chuck

[Chuck Short (zulcss)]

Sorry I meant "named"

Thanks
chuck

[j(/)rn (jorn-nydahl-gmail)]

This is the only relevant stuff I can find :

Oct 23 02:33:56 localhost named[19030]: invalid command from 127.0.0.1#35652: bad auth

But as I wrote earlier a restart solved the issue.

[boule75 (jbbmob)]

Roughly the same issue here, during today's upgrade from one stable version to the other.

Sorry for the 4 IPs on the same interface, but I cannot imagine this is the issue. Bind was working before. I cannot find the command "invalid command from ..." line in daemon.log. Here is a grep of that file. I'll see if a reboot "solves" the issue.

# grep named daemon.log
Oct 30 08:01:36 thelmus named[3123]: starting BIND 9.5.1-P2 -u bind
Oct 30 08:01:36 thelmus named[3123]: found 2 CPUs, using 2 worker threads
Oct 30 08:01:36 thelmus named[3123]: using up to 4096 sockets
Oct 30 08:01:36 thelmus named[3123]: loading configuration from '/etc/bind/named.conf'
Oct 30 08:01:36 thelmus named[3123]: max open files (1024) is smaller than max sockets (4096)
Oct 30 08:01:36 thelmus named[3123]: using default UDP/IPv4 port range: [1024, 65535]
Oct 30 08:01:36 thelmus named[3123]: using default UDP/IPv6 port range: [1024, 65535]
Oct 30 08:01:36 thelmus named[3123]: listening on IPv6 interfaces, port 53
Oct 30 08:01:36 thelmus named[3123]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 30 08:01:36 thelmus named[3123]: listening on IPv4 interface eth0, 192.168.1.11#53
Oct 30 08:01:36 thelmus named[3123]: listening on IPv4 interface eth0:0, 192.168.1.12#53
Oct 30 08:01:36 thelmus named[3123]: listening on IPv4 interface eth0:1, 192.168.1.13#53
Oct 30 08:01:36 thelmus named[3123]: listening on IPv4 interface eth0:2, 192.168.1.14#53
Oct 30 08:01:36 thelmus named[3123]: listening on IPv4 interface eth0:3, 192.168.1.15#53
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: 254.169.IN-ADDR.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: D.F.IP6.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: 8.E.F.IP6.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: 9.E.F.IP6.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: A.E.F.IP6.ARPA
Oct 30 08:01:36 thelmus named[3123]: automatic empty zone: B.E.F.IP6.ARPA
Oct 30 08:01:36 thelmus named[3123]: command channel listening on 127.0.0.1#953

[Chuck Short (zulcss)]

Anything in the syslog?

Thanks
chuck

[Chuck Short (zulcss)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Chuck Short (zulcss)]

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!