well i've now been able to restart 3 of the 4 systems about 5-10x each
through the day. all have had their gateway and dns- settings from
/e/n/i reliably set. that is, until now. i've got one system that did
not get gateway or dns- settings.
is there a way to check for a failure status code tied to ifup or
resolvconf runs during startup?
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address x.y.105.96
netmask 255.255.252.0
# network x.y.104.0
broadcast x.y.107.255
gateway x.y.107.250
# dns-* options are implemented by the resolvconf package, if installed
dns-nameserver x.y.105.44
dns-nameserver x.y.147.98
dns-search r.mydomain s.mydomain t.mydomain
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
note: i have since removed the comments from base & tail.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1628552
Title:
on startup gateway & dns- options in /etc/network/interfaces are not
always set
Status in ifupdown package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Bug description:
recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial
Xerus). on startup, settings within /etc/network/interfaces do not
appear to be taking effect reliably. specifically, the gateway and
dns- settings have been problematic for me. on subsequent restarts,
all or some of the settings take effect other times the gateway is set
and the dns- options are not set. very problematic when the default
gateway is not added to the routing table.
the dns- settings were a bit easier to illustrate the issue. i added a
comment to /etc/resolvconf/resolv.conf.d/base (# base) &
etc/resolvconf/resolv.conf.d/tail (# tail).
$ cat /etc/resolvconf/resolv.conf.d/*
# base
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# tail
on startup on 1 of the systems showed this:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# tail
you can see the "# base" comment wasn't added.
let me know if i can add anymore details or if this should be posted somewhere else.
$ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
$ apt-cache policy ifupdown
ifupdown:
Installed: 0.8.10ubuntu1.1
Candidate: 0.8.10ubuntu1.1
Version table:
*** 0.8.10ubuntu1.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.8.10ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
$ apt-cache policy resolvconf
resolvconf:
Installed: 1.78ubuntu2
Candidate: 1.78ubuntu2
Version table:
*** 1.78ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+subscriptions