*** This bug is a duplicate of bug 1804847 *** https://bugs.launchpad.net/bugs/1804847
OpenVZ has been proactive w.r.t. this issue and have issued an update that includes the required backports a long time ago. Please see this comment: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/comments/20 """ Updated OpenVz6 kernel was released: https://wiki.openvz.org/Download/kernel/rhel6/042stab134.7 We are very grateful for Ubuntu team for reverting of patches specially for OpenVz. For affected hosters: OpenVz6 is great but it is really old, and similar incidents can happen again and again. Please think about switch to RHEL7-based OpenVz7. Thank you, Vasily Averin """ Which was released in November 2018. All your provider needs to do, is to apply OpenVZ updates. >From Ubuntu point of view this is a wontfix, as providing systemd without using fchownat opens a security vulnerability CVE-2018-6954. Please upgrde to OpenVZ kernel 042stab134.7 or anything better. I believe currently the latest kernel is 042stab136.1. @ddstreet please delete your packages from the PPA, as you are intentially distributing security vulnerable systemd. Regards, Dimitri. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6954 ** Changed in: systemd (Ubuntu Xenial) Status: Invalid => Won't Fix ** Changed in: systemd (Ubuntu) Status: New => Won't Fix ** This bug has been marked a duplicate of bug 1804847 systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818814 Title: systemd-tmpfiles-setup.services fails to create /var/run directories Status in systemd package in Ubuntu: Won't Fix Status in systemd source package in Xenial: Won't Fix 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 _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp