On Tue, Feb 26, 2019 at 02:39:55PM -0000, Matt P wrote: > Anyway, root cause seems to be this systemd-tmpfiles error. Tmpfile gets > purged at reboot and doesn't get recreated.
> Seems pretty major that applying security updates would lock you out of > your server. If I didn't happen to have a serial console with this > particular VPS provider (some others I use don't provide one)...I would > have no idea what was going on. > I get this might be due to weird openvz image or older kernel...but > these ubuntu openvz images are very common. As per https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/comments/14 you must have at least 042stab134.7 installed. Your comment shows that you have 042sta120.18 installed. You will need to contact your hosting provider about updating. Given that an updated kernel exists, we do not intend to reduce security for all other Ubuntu users on account of hosting providers who are both running Ubuntu container guests on top of an unsupported non-Ubuntu kernel, *and* are not keeping their kernel up to date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811580 Title: systemd fails to start sshd at reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
