This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1782709
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782709
Title:
Updating systemd kills network on bionic
Status in linux package in Ubuntu:
Incomplete
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
