On 05/02/16 16:37, Pat Barnes wrote:
On Fri, 2016-02-05 at 08:37 +0000, martynvidler wrote:
On 05/02/16 04:19, Douglas R. Reno wrote:
On Tue, Feb 2, 2016 at 4:46 PM, Pat Barnes <pat.bar...@charter.net>
wrote:
On Tue, 2016-02-02 at 17:19 -0500, Munir Contractor wrote:
>
>
> On Tue, Feb 2, 2016 at 1:03 PM, Pat Barnes
<pat.bar...@charter.net>
> wrote:
> On Mon, 2016-02-01 at 22:24 +0000, spiky wrote:
> > Hi
> >
> > I have just installed Linux-pam 1.2.1 then
reinstalled
> shadow as
> > required from BLFS systemd, I am unable to login
as my user
> I get
> > "System is booting up. See pam_nologin(8)",
root can login
> with the
> > same message between login and password. I am
then able to
> su - user
> > once root has logged in. I have a file
in /var/run/nologin
> with the
> > same message in.
> > I tried creating a new user to see if they could
login same
> problem.
> > Googling has thrown up this issue but no clear
way to
> resolve.
> >
> >
> > I have just built lfs systemd svn
>
> The problem is that "something" is setting the
nolgin file
> during the
> boot process, but is not deleting it after it is
safe. I
> worked through
> this problem a few months back but can't remember
what it was
> that was
> setting the file.
>
> The workaround is to edit the /etc/pam.d/login
file and
> comment out he
> entry for pam_login.so. e.g.,
>
> #auth requisite pam_login.so
>
> Do this until you find out what is creating the
file and how
> to get it
> to turn it off.
>
> Perhaps someone else on this list can remember
what it that
> causes this
> problem and how to fix it.
>
> In the meantime, assuming that this is for a
personal
> computer, there is
> no harm in disabling the nologin check. It is
really designed
> for use
> with multi-user servers to allow the administrator
to disable
> logins
> during maintenance
>
> Pat
>
>
> Hi,
>
>
> I had the exact same issue with PAM, shadow and systemd.
> The fix I had to do was delete $LFS/run/nologin from the
host, then
> login to my LFS system and rebuild systemd.
>
>
> For me, the file /run/nologin was getting created by
systemd sometime
> during the shutdown process.
> I couldn't pinpoint what exactly was creating the file or
why the file
> was created, but after I figured out that it was a systemd
issue, I
> rebuilt systemd and my login worked fine.
>
>
> A little bit of googling revealed that
systemd-user-sessions.service
> is supposed to delete this file during boot, but it seems
that without
> PAM+shadow support built into systemd, it fails to delete
it.
> Again, this is just my guess since rebuilding systemd
fixed the issue
> for me and I didn't probe further.
YES - That is the exact fix I couldn't remember. If you look
in the BLFS
book for systemd, it will mention that you need to rebuild
Systemd in
order for the systemd-logind + pam to work correctly
Pat
>
>
Yes, that is the exact solution. Should DJ and I make a change (e.g.
a note or warning) to ensure that our users understand that we must
rebuild Systemd in order for PAM / Shadow to work right?
Douglas R. Reno
--LFS/BLFS systemd Maintainer
Hi
I was going to mention that there is no mention of reinstalling
Systemd on Linux-pm page which would help users, so I think that it
would be a good idea.
Yes, I also thought about that after responding to the original post. I
remembered that I had found the fix, but not where. When doing my next
build, I would probably forget it again if there is no note on the
linux-pam page to remind me to rebuild systend
Pat
Hi
Just been building blfs again, thks for adding "systemd reinstall" it
did/will help
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
