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): systemd-233-6.fc26.x86_64 How reproducible: 100% Steps to Reproduce: 1.see above 2. 3. Actual results: Have to manually delete /var/run/nologin to login as non-root Expected results: Normal login Additional info: 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.
Indeed.
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.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.