[Bug 1782709] Re: Updating systemd kills network on bionic
Launchpad Bug Tracker
1782709 at bugs.launchpad.net
Sun Mar 17 19:55:39 UTC 2019
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1782709
Title:
Updating systemd kills network on bionic
Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Confirmed
Bug description:
I do have an ubuntu bionic server installation without a graphical interface. The server
has two active network adapters, both connected to the internet. One is used for outgoing
internet traffic, the other for incoming. The incoming adapter lives on a public network segment
(something like 88.236.133.104/29). I do have multiple servers within this segment.
Typically, I update the server regularly, meaning:
* ssh to the incoming adapter: ssh 88.236.133.108
* apt-get update
* apt-get upgrade
* apt-get dist-upgrade
* apt-get clean
* reboot
It used to work ok.
BUT: Today, "apt-get upgrade" seem to take really long when updating systemd.
After a could of minutes, I realized that the ssh session became inactive. I couldn't type
into it, I had to abort it via ~. .
* ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108
* ssh via another server within the public network segment worked
* ssh 88.236.133.106 -> ssh 88.236.133.108
* After running "netplan apply" everything was fine again
Here my netplan configuration (I changed the ip addresses):
network:
version: 2
renderer: networkd
ethernets:
eno1:
dhcp4: yes
eno2:
dhcp4: no
addresses: [88.236.133.108/29]
#gateway4: 88.236.133.105
routes:
- to: 0.0.0.0/0
via: 88.236.133.105
table: 120
routing-policy:
- from: 88.236.133.108/32
table: 120
- to: 88.236.133.108/32
table: 120
Unfortunately, I don't have the console output avalable anymore.
Shall I provide additional info?
Best regards, Uli
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jul 20 08:10 seq
crw-rw---- 1 root audio 116, 33 Jul 20 08:10 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-07-14 (5 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: IBM IBM System x -[794582G]-
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/07/2014
dmi.bios.vendor: IBM Corp.
dmi.bios.version: -[D6E162AUS-1.20]-
dmi.board.asset.tag: (none)
dmi.board.name: 00D4062
dmi.board.vendor: IBM
dmi.board.version: (none)
dmi.chassis.asset.tag: none
dmi.chassis.type: 23
dmi.chassis.vendor: IBM
dmi.chassis.version: none
dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
dmi.product.family: System x
dmi.product.name: IBM System x -[794582G]-
dmi.product.version: 00
dmi.sys.vendor: IBM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions
More information about the foundations-bugs
mailing list