Bind/named does not initialize on boot due to missing IPv6 address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Binary package hint: bind9
Hello,
After a reboot I noticed that named did not start. Starting it manually worked fine.
In the log I found:
Jan 21 11:27:40 sid named[1315]: starting BIND 9.6.1-P2 -u bind
Jan 21 11:27:40 sid named[1315]: built with '--prefix=/usr' '--mandir=
Jan 21 11:27:40 sid named[1315]: adjusted limit on open files from 1024 to 1048576
Jan 21 11:27:40 sid named[1315]: found 4 CPUs, using 4 worker threads
Jan 21 11:27:40 sid named[1315]: using up to 4096 sockets
Jan 21 11:27:40 sid named[1315]: loading configuration from '/etc/bind/
Jan 21 11:27:41 sid named[1315]: using default UDP/IPv4 port range: [1024, 65535]
Jan 21 11:27:41 sid named[1315]: using default UDP/IPv6 port range: [1024, 65535]
Jan 21 11:27:41 sid named[1315]: listening on IPv4 interface eth0:auth2, 62.212.1.11#53
Jan 21 11:27:41 sid named[1315]: listening on IPv6 interface eth0, 2a02:20:
Jan 21 11:27:41 sid named[1315]: could not listen on UDP socket: address not available
Jan 21 11:27:41 sid named[1315]: creating IPv6 interface eth0 failed; interface ignored
Jan 21 11:27:41 sid named[1315]: could not get query source dispatcher (2a02:20:
Jan 21 11:27:41 sid named[1315]: additionally listening on IPv6 interface eth0, 2a02:20:
Jan 21 11:27:41 sid named[1315]: could not listen on UDP socket: address not available
Jan 21 11:27:41 sid named[1315]: creating IPv6 interface eth0 failed; interface ignored
Jan 21 11:27:41 sid named[1315]: loading configuration: address not available
Jan 21 11:27:41 sid named[1315]: exiting (due to fatal error)
It looks like the IPv6 address was not yet assigned to the interface, thus named wasn't able to listen on it.
Changed in bind9 (Ubuntu): | |
status: | Expired → New |
Changed in bind9 (Ubuntu): | |
status: | New → Triaged |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!
When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.