Public bug reported:
1. Description: Ubuntu 16.04.5 LTS
Release: 16.04
2. apt-cache policy systemd
systemd:
Installed: 229-4ubuntu21.15
Candidate: 229-4ubuntu21.15
Version table:
*** 229-4ubuntu21.15 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
3. After VPS was rebooted I can't to connect via SSH
4. SSH Service fail because systemd-tmpfiles service fail to start after update
I can connect to VPS (openVZ) only via emergency console
journalctl -b 0 -u systemd-tmpfiles-setup.service
-- Logs begin at Sun 2019-01-13 18:34:20 EET, end at Sun 2019-01-13 18:50:00
EET. --
Jan 13 18:34:20 wok.f.time4vps.cloud systemd[1]: Starting Create Volatile Files
and Directories...
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]:
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/screen: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/sshd: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/sudo: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/sudo/ts: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/utmp failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/systemd/netif failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/systemd/netif/links failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/systemd/netif/leases failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]:
systemd-tmpfiles-setup.service: Main process exited, code=exited,
status=1/FAILURE
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: Failed to start Create
Volatile Files and Directories.
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]:
systemd-tmpfiles-setup.service: Unit entered failed state.
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]:
systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
workaround to start SSH is mkdir /run/sshd
The situation like this
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: ssh sshd systemd-tmpfiles
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1811592
Title:
systemd-tmpfiles-setup.service fails after update
Status in systemd package in Ubuntu:
New
Bug description:
1. Description: Ubuntu 16.04.5 LTS
Release: 16.04
2. apt-cache policy systemd
systemd:
Installed: 229-4ubuntu21.15
Candidate: 229-4ubuntu21.15
Version table:
*** 229-4ubuntu21.15 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
3. After VPS was rebooted I can't to connect via SSH
4. SSH Service fail because systemd-tmpfiles service fail to start after
update
I can connect to VPS (openVZ) only via emergency console
journalctl -b 0 -u systemd-tmpfiles-setup.service
-- Logs begin at Sun 2019-01-13 18:34:20 EET, end at Sun 2019-01-13 18:50:00
EET. --
Jan 13 18:34:20 wok.f.time4vps.cloud systemd[1]: Starting Create Volatile
Files and Directories...
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]:
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/screen: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/sshd: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/sudo: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate
path /var/run/sudo/ts: Too many levels of symbolic links
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/utmp failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/systemd/netif failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/systemd/netif/links failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of
/run/systemd/netif/leases failed: Invalid argument
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]:
systemd-tmpfiles-setup.service: Main process exited, code=exited,
status=1/FAILURE
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: Failed to start Create
Volatile Files and Directories.
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]:
systemd-tmpfiles-setup.service: Unit entered failed state.
Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]:
systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
workaround to start SSH is mkdir /run/sshd
The situation like this
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811592/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
