Red Hat Bugzilla – Bug 1471519
Error in /etc/tmpfiles.d/ entry leads to /var/run/nologin still there after boot
Last modified: 2018-03-23 04:45:49 EDT
Description of problem:
I was copying stuff from my old root to my new fedora 26 root. One of the files I copied was /etc/tmpfiles.d/stunnel.conf which looks like:
d /var/run/stunnel 0755 stunnel stunnel
That refers to the stunnel user and group, but I foolishly failed to create the stunnel system user in the fedora 26 root.
That leads to the entirely unexpected and totally wacky side-effect of the /var/run/nologin file hanging around long after the system has actually finished booting.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Have to manually delete /var/run/nologin to login as non-root
This seems like busted error handling. I'd expect it to ignore the tmpfiles.d entry that makes no sense and spew a log message about it, not wind up with things so broken I can't login.
I ran into similar issues. Could you please point out how you figured out which tmpfiles.d conf file caused the issue on your side?
Not much help probably: I only had one that I manually created, so I figured it must be that one.
Just for curiosity, I made the same error again when installing fedora 27 and the same nologin problem is caused by a bad tmpfile configuration (at least it wasn't as confusing this time :-).
This is fixed in F28, but backporting to F27 is complicated. I'll leave this in POST state for now.