sys-libs/pam does not allow login due to a missing config file. The follow error message was pulled from /var/log/auth.log. Nov 16 20:38:20 localhost login[4783]: PAM _pam_init_handlers: no default config /etc/pam.d/other Nov 16 20:38:20 localhost login[4783]: PAM error reading PAM configuration file Nov 16 20:38:20 localhost login[4783]: PAM pam_start: failed to initialize handlers Nov 16 20:38:20 localhost login[4783]: Couldn't initialize PAM: Critical error - immediate abort Reproducible: Always Steps to Reproduce: 1. install stage3 2004.3 ppc 2. login as an existing user 3. Actual Results: Error message on console "Couldn't initialize PAM: Critical error - immediate abort" and inability to login. Expected Results: successful login.
i'm not exactly sure what solved this but here is what i did right before the problem was resolved: i noticed that /etc/pam.d/ was missing a bunch of files that a x86 box had. #emerge baselayout -uvp (i was on -r4 b4?) then i sftped into a working x86 box and sucked down * and put them all into /etc/pam.d on the box that i couldn't get into... then bingo... all problems solved. --andy richter
*** Bug 71488 has been marked as a duplicate of this bug. ***
*** Bug 71489 has been marked as a duplicate of this bug. ***
*** Bug 71490 has been marked as a duplicate of this bug. ***
I am having the same exact issue with 2004.3 on an iMac. It would appear that with all the issues others are having with PAM in this release, and not just the PPC port, PAM should have been masked as it is not nearly ready for use. Please upgrade this bug to critical and / or priority1 so we can get a resolution. Thanks Ultanium
could you please emerge shadow and tell me if the problem disappear?
Yes, that did the trick. Thanks! Ult
just confirming... this bug is a huge showstopper. I'm new to ppc (still typing ~x86 out of habit), and it took me a while to figure this one out. Emerging shadow worked for me as well.
I've added the pam use flag to the default-2004.3 profile, which should fix this problem. Please reopen the bug if it's still happening.