On 01/08/2014 04:29 AM, Sam Varshavchik issued this missive:
Steven P. Ulrick writes:
On Sat, 4 Jan 2014 19:42:16 -0600
Steven Ulrick <meow8282@xxxxxxxxx> wrote:
> On Saturday, January 4, 2014, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx>
> wrote:
> > About ten hours after a reboot, a chance attempt to log in back to
> > the
> server was rather rudely rejected with a:
> >
> > System is booting up. See pam_nologin(8)
> > Connection closed by 192.168.0.2
> >
> > A quick run back to the console revealed the existence of a ten
> > hour old
> /var/run/nologin file as the culprit. Removing it put everything back
> in working order.
>
> Two things:
> 1. You are not alone!
> 2. Thanks for the workaround...
OK... I guess #2 was a bit premature. I just had reason to log out of
my KDE session. When I logged back in (or tried to), I was greeted
with the dreaded "System is booting up. See pam_nologin(8)" When my
system is in this state, I can get to a console, but it will not let me
log in. I even tried to ssh from another system. The other system
informs me of the following:
> > System is booting up. See pam_nologin(8)
For clarification, the remote system that I am attempting to ssh FROM
is telling me that the system that I am trying to ssh INTO is in the
following state:
> > System is booting up. See pam_nologin(8)
So, it appears that I have no workaround to this issue other than
rebooting...
No. According to the documentation, root is allowed to log in. You
should be able to ssh as root.
My original working theory was that /run/nologin was not getting cleared
by whatever godforsaken systemd service is responsible for removing it,
when the boot mostly completes. This was based on my /run/nologin's
timestamp, which dated back to my system's boot.
But if that's getting spuriously created, during a normal system state,
then something indeed must be creating it, in the wild.
Not going to be easy tracking it down. Perusing journalctl's man page,
there doesn't seem to be a way to specify a time interval. Given
/run/nologin's timestamp, it should be possible to track down what was
started in that timeframe, but I do not see a way to specify a
timeframe. Furthermore, journalctl's output seems to consist of merely
log messages from systemd-started processes, rather than the actual log
of what was started, and when.
'journalctl --since=-600' will show all log messages for the last 600
seconds (10 minutes). Or you can use
'journalctl --since="2014-01-08 00:00:00"' for everything since midnight
today. You get the idea. "man journalctl" and look at the "--since" and
"--until" bits. You can even combine the two:
journalctl --since="2014-01-08 00:00:00" --until="2014-01-08 08:00:00"
to get stuff between midnight and 8 a.m.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Let us think the unthinkable. Let us do the undoable. Let us -
- prepare to grapple with the ineffable itself, and see if we may -
- not eff it up after all. -
- -- Douglas Adams -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
