Zypper dup - 11.0 -> 11.1, login issue

I can’t login, when I try from console (to see the error) I get “Module not found”

What package could be causing this? :frowning:

Luckily I can still shell into my box…

It’ll probably be something to do with PAM “Pluggable Authentication Modules”, which I have as

rob@fir:~> rpm -qa |grep pam
pam-1.0.2-13.4
pam-config-0.68-1.4
spamassassin-3.2.5-26.5
yast2-pam-2.17.1-1.25
pam_apparmor-2.3-2.65
perl-spamassassin-3.2.5-26.5
pam-modules-11.1-5.1

And config files in /etc/pam.d/

I did zypper ve, that didn’t fix it either.

Oh, and the error was “Module is unknown” :\

I did zypper ve, that didn’t fix it either.

Oh, and the error was “Module is unknown” :\

Edit:

Thanks robo. Should I remove the module or change something in that config file?

Look, I’ve been cautious all over this forum about ‘upgrade’, I have never done it, as in past I’ve seen too many reports of issues. I just don’t trust them!

So I’m afraid I suspect it’s an ‘interesting’ problem, which would take some digging around. If you’re lucky someone else will have already come across it and solved it.

Perhaps someone who recommends “zypper dup” to go from one release to another, will know exactly what it is already.

You could try searching Bugzilla.

I will at least post my /etc/pam.d here: (might help if it is related)

" ============================================================================
" Netrw Directory Listing                                        (netrw v109)
"   /etc/pam.d
"   Sorted by      name
"   Sort sequence: \/]$,\.h$,\.c$,\.cpp$,\.[a-np-z]$,*,\.info$,\.swp$,\.o$\.obj
"   Quick Help: <F1>:help  -:go up dir  D:delete  R:rename  s:sort-by  x:exec
" ============================================================================
../
./
atd
chage
chfn
chsh
common-account
common-account-pc
common-account.pam-config-backup
common-account.rpmnew
common-auth
common-auth-pc
common-auth.pam-config-backup
common-auth.rpmnew
common-password
common-password-pc
common-password.pam-config-backup
common-password.rpmnew
common-session
common-session-pc
common-session.pam-config-backup
common-session.rpmnew
crond
cups
gdm
gdm-autologin
gnome-passwd
gnome-screensaver
gnome-screensaver-smartcard
gnomesu-pam
kcheckpass
login
login.old
other
passwd
polkit
ppp
rpasswd
samba
shadow
smtp
sshd
su
su-l
sudo
useradd
xdm
xdm-np
xlock
xscreensaver

Hmm, this looks like the issue:

# tail -f /var/log/messages
Dec 18 17:46:18 linux-dx5z login[2921]: PAM unable to dlopen(/lib64/security/pam_resmgr.so): /lib64/security/pam_resmgr.so: cannot open shared object file: No such file or directory
Dec 18 17:46:18 linux-dx5z login[2921]: PAM adding faulty module: /lib64/security/pam_resmgr.so
Dec 18 17:46:19 linux-dx5z login[2921]: FAILED LOGIN 1 FROM /dev/tty1 FOR UNKNOWN, User not known to the underlying authentication module

Here is the issue, weird: https://bugzilla.novell.com/show_bug.cgi?id=304695

sed -i 's/session  required       pam_resmgr.so//g' *

cd to /etc/pam.d then run the above code, that should fix it… Finally! :’(

I had this exact problem last night when I tried to do an update, Thanks for posting a possible solution, just hope I can get into a shell to run the code.

Well done!

Though I didn’t know the answer, I thought you might discover something if you knew what area to look in.

in the PAM stuff you will probably fix it properly.

Darn it, only 10 mins to edit :frowning:

That’s my lib64 root partition, on x86_amd 11.1

fir:/mnt # ls  /mnt/lib64/security/
pam_access.so        pam_homecheck.so  pam_permit.so      pam_time.so
pam_apparmor.so      pam_issue.so      pam_pwcheck.so     pam_tty_audit.so
pam_ck_connector.so  pam_keyinit.so    pam_pwhistory.so   pam_umask.so
pam_cracklib.so      pam_lastlog.so    pam_rhosts.so      pam_unix.so
pam_debug.so         pam_limits.so     pam_rootok.so      pam_unix2.so
pam_deny.so          pam_listfile.so   pam_rpasswd.so     pam_unix_acct.so
pam_echo.so          pam_localuser.so  pam_securetty.so   pam_unix_auth.so
pam_env.so           pam_loginuid.so   pam_selinux.so     pam_unix_passwd.so
pam_exec.so          pam_mail.so       pam_sepermit.so    pam_unix_session.so
pam_faildelay.so     pam_make.so       pam_shells.so      pam_userdb.so
pam_filter           pam_mkhomedir.so  pam_stress.so      pam_warn.so
pam_filter.so        pam_motd.so       pam_succeed_if.so  pam_wheel.so
pam_ftp.so           pam_namespace.so  pam_tally.so       pam_xauth.so
pam_group.so         pam_nologin.so    pam_tally2.so

The cleanest fix most likely involves finding your pam configuration in /etc/pam.d that differs, from 11.1, and applying the change.

Not much fun, and then what other problems do you have lurking, due to misconfigurations?