systemd-tmpfiles-setup.services fails to create /var/run directories
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Xenial |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
systemd:
Installed: 229-4ubuntu21.16
Candidate: 229-4ubuntu21.16
Version table:
*** 229-4ubuntu21.16 500
500 http://
500 http://
100 /var/lib/
229-4ubuntu4 500
500 http://
3) What you expected to happen
4) What happened instead
Ubuntu server (running in OpenVZ VPS farm, thus the old kernel version) has been up and running happily, until I performed apt-get upgrade and rebooted the server. After reboot, I could not establish SSH connection to server, port 22 connection was refused.
I opened a HTML console to my server instance and checked logs. From the logs, it was shown, that SSH server could not start, as it did not have the /var/run/sshd directory. After scrolling back the /var/log/syslog, I noticed that there were lots of other /var/run subdirectories, which were not created. Here is cut&paste from /var/log/syslog, related to systemd-tmpfiles:
---8<---8<---
Mar 6 12:32:54 vspk systemd-
ar/log", ignoring.
Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces...
Mar 6 12:32:54 vspk systemd-
Mar 6 12:32:54 vspk systemd-
olic links
Mar 6 12:32:54 vspk systemd-
ic links
Mar 6 12:32:54 vspk systemd-
links
Mar 6 12:32:54 vspk systemd-
links
Mar 6 12:32:54 vspk systemd-
lic links
Mar 6 12:32:54 vspk systemd-
Mar 6 12:32:54 vspk systemd-
Mar 6 12:32:54 vspk systemd-
Mar 6 12:32:54 vspk systemd-
Mar 6 12:32:54 vspk systemd-
ic links
Mar 6 12:32:54 vspk systemd-
Mar 6 12:32:54 vspk systemd-
iled: Invalid argument
Mar 6 12:32:54 vspk systemd-
stem.journal failed: Invalid argument
Mar 6 12:32:54 vspk systemd[1]: systemd-
AILURE
Mar 6 12:32:54 vspk systemd[1]: Failed to start Create Volatile Files and Directories.
Mar 6 12:32:54 vspk systemd[1]: systemd-
Mar 6 12:32:54 vspk systemd[1]: systemd-
---8<---8<---
My first idea was, that for some reason, systemd-tmpfiles was not able to create the /var directory properly, so I renamed /usr/lib/
As I created this error using the "ubuntu-bug" command, I assume necessary background information is automatically attached. I'll check those and add more, if necessary.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu21.16
Uname: Linux 2.6.32-042stab128.2 x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDmesg:
Date: Wed Mar 6 12:43:51 2019
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
TERM=vt220
PATH=(custom, no user)
ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts'
ProcKernelCmdLine: quiet
ProcModules:
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
CVE References
Changed in systemd (Ubuntu): | |
status: | New → Incomplete |
Additional information: the problem appeared after updating libsystemd0:amd64 from 229-4ubuntu21.10 to 229-4ubuntu21.16