Working config in eoan, bind9 fails after upgrade to fossa
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind-dyndb-ldap (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
In Progress
|
Undecided
|
Timo Aaltonen | ||
bind9 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Focal |
In Progress
|
Undecided
|
Timo Aaltonen |
Bug Description
Configuration was working in Eoan. Just upgraded to Fossa. Bind9(named) will not start. Syslog show the following:
Apr 23 16:55:58 ltserver2 named[1611]: starting BIND 9.16.1-Ubuntu (Stable Release) <id:d497c32>
Apr 23 16:55:58 ltserver2 named[1611]: running on Linux x86_64 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
Apr 23 16:55:58 ltserver2 named[1611]: built with '--build=
Apr 23 16:55:58 ltserver2 named[1611]: running as: named -f -u bind
Apr 23 16:55:58 ltserver2 named[1611]: compiled by GCC 9.3.0
Apr 23 16:55:58 ltserver2 named[1611]: compiled with OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
Apr 23 16:55:58 ltserver2 named[1611]: linked to OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
Apr 23 16:55:58 ltserver2 named[1611]: compiled with libxml2 version: 2.9.10
Apr 23 16:55:58 ltserver2 named[1611]: linked to libxml2 version: 20910
Apr 23 16:55:58 ltserver2 named[1611]: compiled with json-c version: 0.13.1
Apr 23 16:55:58 ltserver2 named[1611]: linked to json-c version: 0.13.1
Apr 23 16:55:58 ltserver2 named[1611]: compiled with zlib version: 1.2.11
Apr 23 16:55:58 ltserver2 named[1611]: linked to zlib version: 1.2.11
Apr 23 16:55:58 ltserver2 named[1611]: -------
Apr 23 16:55:58 ltserver2 named[1611]: BIND 9 is maintained by Internet Systems Consortium,
Apr 23 16:55:58 ltserver2 named[1611]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Apr 23 16:55:58 ltserver2 named[1611]: corporation. Support and training for BIND 9 are
Apr 23 16:55:58 ltserver2 named[1611]: available at https:/
Apr 23 16:55:58 ltserver2 named[1611]: -------
Apr 23 16:55:58 ltserver2 named[1611]: adjusted limit on open files from 524288 to 1048576
Apr 23 16:55:58 ltserver2 named[1611]: found 2 CPUs, using 2 worker threads
Apr 23 16:55:58 ltserver2 named[1611]: using 2 UDP listeners per interface
Apr 23 16:55:58 ltserver2 named[1611]: using up to 21000 sockets
Apr 23 16:55:58 ltserver2 named[1611]: loading configuration from '/etc/bind/
Apr 23 16:55:58 ltserver2 named[1611]: reading built-in trust anchors from file '/etc/bind/
Apr 23 16:55:58 ltserver2 named[1611]: looking for GeoIP2 databases in '/usr/share/GeoIP'
Apr 23 16:55:58 ltserver2 named[1611]: using default UDP/IPv4 port range: [32768, 60999]
Apr 23 16:55:58 ltserver2 named[1611]: using default UDP/IPv6 port range: [32768, 60999]
Apr 23 16:55:58 ltserver2 named[1611]: listening on IPv4 interface enp3s0, <LocalIPAddress>#53
Apr 23 16:55:58 ltserver2 named[1611]: IPv6 socket API is incomplete; explicitly binding to each IPv6 address separately
Apr 23 16:55:58 ltserver2 named[1611]: listening on IPv6 interface lo, ::1#53
Apr 23 16:55:58 ltserver2 named[1611]: listening on IPv6 interface enp3s0, <IP6Address>%2#53
Apr 23 16:55:58 ltserver2 named[1611]: unable to set effective uid to 0: Operation not permitted
Apr 23 16:55:58 ltserver2 named[1611]: generating session key for dynamic DNS
Apr 23 16:55:58 ltserver2 named[1611]: unable to set effective uid to 0: Operation not permitted
Apr 23 16:55:58 ltserver2 named[1611]: sizing zone task pool based on 0 zones
Apr 23 16:55:58 ltserver2 named[1611]: none:100: 'max-cache-size 90%' - setting to 3513MB (out of 3903MB)
Apr 23 16:55:58 ltserver2 named[1611]: set up managed keys zone for view _default, file 'managed-keys.bind'
Apr 23 16:55:58 ltserver2 named[1611]: loading DynDB instance 'MY_FULLY_
Apr 23 16:55:58 ltserver2 named[1611]: failed to dynamically load instance 'MY_FULLY_
Apr 23 16:55:58 ltserver2 named[1611]: dynamic database 'dns.schapker.
Apr 23 16:55:58 ltserver2 named[1611]: loading configuration: failure
Apr 23 16:55:58 ltserver2 named[1611]: exiting (due to fatal error)
Apr 23 16:55:58 ltserver2 systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE
Apr 23 16:55:58 ltserver2 systemd[1]: named.service: Failed with result 'exit-code'.
(I have attempted to remove personal identifiable information above. That's shouldn't hamper diagnosis of this issue)
Based on the error, I presume some code is missing somewhere.
I believe "/usr/lib/
This is kind of an issue for me as now I do not have a working DNS server since the upgrade. Any assistance would be greatly appreciated!
These are the "bind9" packages I have installed:
bind9-dnsutils/
bind9-dyndb-
bind9-host/
bind9-libs/
bind9-utils/
bind9/focal,now 1:9.16.1-0ubuntu2 amd64 [installed,
(fresh upgrade from Eoan to Focal, with no known deviations from Focal packages)
Larry Schapker
affects: | bind (Ubuntu) → bind9 (Ubuntu) |
Yes, it won't work until it has been ported to 9.16, and that didn't make it in focal, but probably as an SRU later.
Are you running freeipa-server? Did you not notice it's not even available in focal?