After upgrading several systems from Stretch to Buster during the last
few weeks, I have had problems with several of them and seek advice.
First, after the upgrade (and in one case of a fresh install), systems
mostly intended as servers - long uptime and reboots only as necessary
for maintenance - appeared to enter a suspend state without approval or
intentional configuration change. All are Intel-based, and except for
the fresh (Intel) install, had run without issue on Stretch for periods
ranging from weeks to months rather than suspending after about 15 idle
minutes. All have Gnome DE (which, for convenience and because I am used
to it, I prefer to keep), either gdm3 or lightdm, and Xorg. All use
systemd for init.
Initially, I told the Gnome power manager not to suspend for idleness,
and that seems to have worked for all but one of them. For that, I
consulted https: //wiki.debian.org/Suspend which, although written for
Jessie, made sense. Masking sleep.target suspend.target hibernate.target
hybrid-sleep.target seems to have cured that one.
My question here is first, is there an explanation for the apparent
behavior change, and second, is there a preferred way to forbid
suspension of servers?
The second oddity is that on one system /etc/resolv.conf is empty after
each reboot after upgrading from Stretch (except for the warning to not
edit the file). It previously was made correctly by resolvconf, and the
This server runs a handful of virtual machines and is rebooted only for
good cause, so I have no particular problem deploying my own, but it is
an annoyance and I will be grateful for suggestions to. Probably
relevant installed packages include
bridge-utils 1.6-2
network-manager 1.14.6-2
network-manager-gnome 1.8.20-1.1
resolvconf 1.79
and maybe others.
What I think is the relevant part of /etc/network/interfaces is
#####
# Network interface #1: enp2s0 - NAS2 (Gray cable)
auto eth2
iface eth2 inet static
mtu 9000
address 192.168.33.10/24
# Network interface #2: enp3s0 - LAN (Blue cable)
auto br0
iface br0 inet static
address 192.168.1.10
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off
dns-nameservers 192.168.1.8 192.168.1.60
dns-search xxxx.xxx # EDITED #
auto br0.222
iface br0.222 inet static
address 10.10.10.10/24
vlan-raw-device br0
auto eth0
iface eth0 inet manual
mtu 9000
#####
For brevity I cut out specifications for the other interfaces, all of
which are similar to that for eth2 above. I'll post the entire file if
anyone thinks it would be useful to resolve the issue.
Thanks in advance for help with either of these.
Tom Dial
td...@acm.org
