login refused

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

login refused

Felix Miata-3
chroot from Fedora 26 install a 4.14.13 kernel after the first failure with
freshly installed 4.13.12. Newest prior kernel before these is 4.10.1 installed
with March dup last prior to 20180119.

All kernels now refuse valid user name to login, reporting invalid login simply
entering the username with no opportunity to provide password, all in runlevel
3. In KDM3 greeter, nothing but a flashing "login failed" message on a rastered
backgound. Only login to runlevel 1 works.

Attachment is output from journalctl -b -1 | grep PAM

I don't see an applicable BOO bug. What's wrong? Is new bug needed? Anyone else
having this trouble?
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

pamtroublt.txt (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: login refused

Jiri Slaby-6
On 01/21/2018, 11:02 AM, Felix Miata wrote:
> Jan 21 04:17:33 gx28c login[926]: PAM unable to dlopen(/lib/security/pam_unix2.so): /lib/security/pam_unix2.so: cannot open shared object file: No such file or directory
> Jan 21 04:17:33 gx28c login[926]: PAM adding faulty module: /lib/security/pam_unix2.so
> Jan 21 04:17:33 gx28c login[926]: PAM unable to dlopen(/lib/security/pam_pwcheck.so): /lib/security/pam_pwcheck.so: cannot open shared object file: No such file or directory

pam_unix2 was removed long time ago. You need to update your pam
configuration (switch it to pam_unix).

The other module, I don't know, so perhaps just remove it from the configs.

--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: login refused

Andreas Schwab-2
On Jan 21 2018, Jiri Slaby <[hidden email]> wrote:

> On 01/21/2018, 11:02 AM, Felix Miata wrote:
>> Jan 21 04:17:33 gx28c login[926]: PAM unable to dlopen(/lib/security/pam_unix2.so): /lib/security/pam_unix2.so: cannot open shared object file: No such file or directory
>> Jan 21 04:17:33 gx28c login[926]: PAM adding faulty module: /lib/security/pam_unix2.so
>> Jan 21 04:17:33 gx28c login[926]: PAM unable to dlopen(/lib/security/pam_pwcheck.so): /lib/security/pam_pwcheck.so: cannot open shared object file: No such file or directory
>
> pam_unix2 was removed long time ago. You need to update your pam
> configuration (switch it to pam_unix).
>
> The other module, I don't know, so perhaps just remove it from the configs.

Both were part of pam-modules which no longer exists.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]