[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories
Kalle Tuulos
1818814 at bugs.launchpad.net
Fri Apr 12 05:29:05 UTC 2019
For Dimitri:
> In addition to debug output from systemd-tmpfiles-setup.service
> as above, it is also interesting to know the permiissions
> on / itself, ie. what's the output of:
> $ ls -la /
kalle at vspk:~$ ls -la /
total 1272
drwxr-xr-x 24 root root 4096 Apr 11 15:18 .
drwxr-xr-x 24 root root 4096 Apr 11 15:18 ..
drwx------ 2 root root 4096 Nov 27 2016 .cpt_hardlink_dir_a920e4ddc233afddc9fb53d26c392319
-rw-r--r-- 1 root root 0 Apr 11 15:20 .vzfifo
drwxr-xr-x 2 root root 4096 Apr 11 15:17 bin
drwxr-xr-x 2 root root 4096 May 14 2018 boot
-rw------- 1 root root 1671168 Apr 11 15:19 core
drwxr-xr-x 5 root root 640 Apr 11 15:19 dev
drwxr-xr-x 154 root root 12288 Apr 11 15:18 etc
drwxr-xr-x 5 root root 4096 Apr 10 15:46 home
drwxr-xr-x 16 root root 4096 Jun 9 2018 lib
drwxr-xr-x 2 root root 4096 Mar 4 08:56 lib64
drwx------ 2 root root 4096 Nov 27 2016 lost+found
drwxr-xr-x 2 root root 4096 Nov 27 2016 media
drwxr-xr-x 2 root root 4096 Nov 27 2016 mnt
drwxr-xr-x 2 root root 4096 Nov 27 2016 opt
dr-xr-xr-x 139 root root 0 Apr 11 15:18 proc
drwx------ 9 root root 4096 Apr 11 08:29 root
drwxr-xr-x 32 root root 980 Apr 12 08:25 run
drwxr-xr-x 2 root root 12288 Apr 11 15:17 sbin
drwxr-xr-x 2 root root 4096 May 14 2018 snap
drwxr-xr-x 2 root root 4096 Nov 27 2016 srv
drwxr-xr-x 7 root root 0 Apr 11 15:18 sys
drwxrwxrwt 9 root root 4096 Apr 12 08:25 tmp
drwxr-xr-x 10 root root 4096 Nov 27 2016 usr
drwxr-xr-x 13 root root 4096 Dec 17 13:37 var
--
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/1818814
Title:
systemd-tmpfiles-setup.services fails to create /var/run directories
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
In Progress
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://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) 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-tmpfiles[81]: [/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v
ar/log", ignoring.
Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces...
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: Invalid argument
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/fail2ban: Too many levels of symb
olic links
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/screen: Too many levels of symbol
ic links
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sshd: Too many levels of symbolic
links
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo: Too many levels of symbolic
links
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo/ts: Too many levels of symbo
lic links
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: Invalid argument
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif failed: Invalid argument
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/links failed: Invalid argument
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/leases failed: Invalid argument
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/zabbix: Too many levels of symbol
ic links
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/log/journal failed: Invalid argument
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/log/journal/6d9c7cc322ee4c48af7c0ec3b492b5cc fa
iled: Invalid argument
Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/log/journal/6d9c7cc322ee4c48af7c0ec3b492b5cc/sy
stem.journal failed: Invalid argument
Mar 6 12:32:54 vspk systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/F
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-tmpfiles-setup.service: Unit entered failed state.
Mar 6 12:32:54 vspk systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
---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/tmpfiles.d/var.conf to 0000var.conf, but it was no help. The
only difference was the first line on the above log, complaining about
duplicate line for path /var/log.
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions
More information about the foundations-bugs
mailing list