Pam account management error module is unknown - Исправление ошибок и поиск оптимальных решений проблем

Содержание

PAM: module is unknown
Arch Linux
#1 2015-11-12 07:00:51
sudo: PAM authentication error: Module is unknown
#2 2015-11-12 07:03:11
Re: sudo: PAM authentication error: Module is unknown
#3 2015-11-12 07:04:51
Re: sudo: PAM authentication error: Module is unknown
#4 2015-11-12 07:06:02
Re: sudo: PAM authentication error: Module is unknown
#5 2015-11-12 07:07:46
Re: sudo: PAM authentication error: Module is unknown
#6 2015-11-12 07:08:04
Re: sudo: PAM authentication error: Module is unknown
#7 2015-11-12 07:08:33
Re: sudo: PAM authentication error: Module is unknown
#8 2015-11-12 07:13:06
Re: sudo: PAM authentication error: Module is unknown
#9 2015-11-14 15:26:58
Re: sudo: PAM authentication error: Module is unknown
#10 2015-11-14 15:36:43
Re: sudo: PAM authentication error: Module is unknown
#11 2015-11-14 15:41:12
Re: sudo: PAM authentication error: Module is unknown
#12 2015-11-14 15:42:45
Re: sudo: PAM authentication error: Module is unknown
#13 2015-11-15 02:21:14
Re: sudo: PAM authentication error: Module is unknown
#14 2015-11-15 06:10:09
Re: sudo: PAM authentication error: Module is unknown
#15 2015-11-15 07:03:16
Re: sudo: PAM authentication error: Module is unknown
#16 2015-11-15 07:15:11
Re: sudo: PAM authentication error: Module is unknown
#17 2015-11-15 07:18:36
Re: sudo: PAM authentication error: Module is unknown
#18 2015-11-15 14:18:03
Re: sudo: PAM authentication error: Module is unknown
#19 2015-11-15 17:33:55
Re: sudo: PAM authentication error: Module is unknown
#20 2015-11-15 20:17:27
Re: sudo: PAM authentication error: Module is unknown

PAM: module is unknown

archlinux 3.13.8-1 x64, xfce4

Случайно испортил системные либы в /lib
Переустановкой из кеша и последующим pacman -Syu — оживил систему, но после перезагрузки не могу даже войти.

При логине под юзером или рутом в консоли пишет — login incorrect
Дописал в грубе «rw init=/bin/bash», загрузился и попал в консоль рута.

Делаю passwd:
passwd: Module is unknown
passwd: password unchanged

useradd test:
useradd: PAM: Module is unknown

pacman -Ss pam
core/pam 1.1.8-3 [installed]
pambase тоже

У пакмена ещё есть варнинг:
pacman: /usr/lib/liblzma.so.5: no version information available (required by libselinux)

Пакет xz, в который входит liblzma переставлял многократно.
,
Находил в гугле разные решения проблемы с логином, но ни одна не помогла.

В этой рутовой консоли ещё и инет не работает, хотя это не такая уж и проблема.

Что ещё можно попробовать?

ещё часто советуют запустить pam-auth-update —force, но у меня в системе его нет и не могу найти где можно скачать

1. попробуй поставить где нить рядом дистрибутив этой же версии, запакуй /lib /lib64 и /etc/pam.d и перенеси

2. если первый вариант никак то попробуй пройтись по /lib ldd и проверить /etc/pam.d и проверь что все libpam-modules/script/runtime/etc стоят

3. можешь попробовать запустить через gdb (не уверен что он чтото покажет в страйпаных бинарниках и либах, но чем черт не шутит 🙂 )

1 загрузился в single mode, нажав в grub ‘e’ и дописав слово single к параметрам загрузки ядра
2 запустил journalctl /usr/bin/passwd — там в конце была куча ошибок про модуль /usr/lib/security/pam_unix.so
3 залил новый pam_unix.so (взял с сервака с debian 7 x64)
после чего заработал passwd

Но для обычного входа в систему пришлось ещё сделать journalctl /usr/bin/login, чтобы узнать что pam_access.so тоже поврежден.
Аналогично, взял его из дебиана.

Ну и, успешно войдя в систему, поправил глючащий sudo его переустановкой.

Главное было сообразить, что надо искать логи PAM и по ним разбираться что с ним произошло, а дальше — дело техники.

Источник

Arch Linux

You are not logged in.

#1 2015-11-12 07:00:51

sudo: PAM authentication error: Module is unknown

After I `yaourt -S pam gpm`, I can’t login/ssh to my laptop.
Also `sudo su root`, it just prints out ‘sudo: PAM authentication error: Module is unknown’

[2015-11-12 14:39] [PACMAN] Running ‘pacman —color auto -S extra/libva-mesa-driver extra/libevdev’
[2015-11-12 14:39] [ALPM] transaction started
[2015-11-12 14:39] [ALPM] upgraded libva-mesa-driver (11.0.4-1 -> 11.0.5-1)
[2015-11-12 14:39] [ALPM] upgraded libevdev (1.4.4-1 -> 1.4.5-1)
[2015-11-12 14:39] [ALPM] transaction completed
[2015-11-12 14:41] [PACMAN] Running ‘pacman —color auto -S core/pam core/gpm’
[2015-11-12 14:41] [ALPM] transaction started
[2015-11-12 14:41] [ALPM] upgraded pam (1.2.1-1 -> 1.2.1-2)
[2015-11-12 14:41] [ALPM] upgraded gpm (1.20.7-5 -> 1.20.7-6)
[2015-11-12 14:41] [ALPM] transaction completed

How can I fix this up? I can’t even roll back to older version of pam.
Can I reboot to single user mode?

Also, why does this update cause this problem?

Last edited by JasonZhang (2015-11-12 07:02:41)

#2 2015-11-12 07:03:11

Re: sudo: PAM authentication error: Module is unknown

Update your system, partial updates are not supported. If you ever run pacman -Sy, you’re probably doing it wrong.

Online

#3 2015-11-12 07:04:51

Re: sudo: PAM authentication error: Module is unknown

@Scimmia, thanks for your reply.

But sometimes I don’t want to update some programs which may have different behaviors to the older version or something else.

#4 2015-11-12 07:06:02

Re: sudo: PAM authentication error: Module is unknown

@Scimmia, thanks for your reply.

But sometimes I don’t want to update some programs which may have different behaviors to the older version or something else.

Then you’re using the wrong distro. If you do partial updates, things like this happen. You’re on your own.

Online

#5 2015-11-12 07:07:46

Re: sudo: PAM authentication error: Module is unknown

@Scimmia, thanks for your reply.

But sometimes I don’t want to update some programs which may have different behaviors to the older version or something else.

Then you’re using the wrong distro. If you do partial updates, things like this happen. You’re on your own.

Emm, but how can I fix this issue up?

#6 2015-11-12 07:08:04

Re: sudo: PAM authentication error: Module is unknown

Not a Sysadmin issue, moving to NC.

Registered Linux User #482438

Online

#7 2015-11-12 07:08:33

Re: sudo: PAM authentication error: Module is unknown

Like I said, by updating your system. You may have to boot to a live CD and use pacman —root to do it.

Online

#8 2015-11-12 07:13:06

Re: sudo: PAM authentication error: Module is unknown

Like I said, by updating your system. You may have to boot to a live CD and use pacman —root to do it.

I’ll have a try. Thank you.

#9 2015-11-14 15:26:58

Re: sudo: PAM authentication error: Module is unknown

I have this error from nowhere and nothing in the middle of an upgrade (not a partial upgrade—in the middle of the actual upgrade process).

I need a solution that does not involve rebooting, as there’s a good chance the system will not be recoverable.

I tried to login as root, but this resulted in «login incorrect» before asking for a password.

EDIT: The last successful use of sudo occured when installing libtirpc during the upgrade. I highly suspect this package is broken, which was a known problem in [testing] as of June.

Last edited by quequotion (2015-11-14 15:37:24)

#10 2015-11-14 15:36:43

Re: sudo: PAM authentication error: Module is unknown

I have this error from nowhere and nothing in the middle of an upgrade (not a partial upgrade—in the middle of the actual upgrade process).

What upgrade process would that be?

If you’re stuck as non-root without working pam, I don’t know what else you can do.

Online

#11 2015-11-14 15:41:12

Re: sudo: PAM authentication error: Module is unknown

If you’re stuck as non-root without working pam, I don’t know what else you can do.

If a functional libtirpc package exists, I can install it with pacstrap from the live cd, but it’s a bit of a gamble.

I do not believe a working package exists; I suspect the problem that appeared in testing has passed into the repositories and lots of people are about to have broken PAM.

Last edited by quequotion (2015-11-14 15:42:53)

#12 2015-11-14 15:42:45

Re: sudo: PAM authentication error: Module is unknown

Nope, current libtirpc works fine. I’ve been running it for over a week.

The issue is upgrading it without upgrading pam (ie, partial update).

Last edited by Scimmia (2015-11-14 15:45:56)

Online

#13 2015-11-15 02:21:14

Re: sudo: PAM authentication error: Module is unknown

What upgrade process would that be?

The kind you don’t expect to leave you with a bricked computer.

I was able to get back to a usable state. I rebooted to the livecd and reinstalled libtirpc with pacstrap but that wasn’t enough because the unfinished upgrade had left many version descrepancies, breaking systemd, gnome, etc.

What is wrong with libtirpc? It looks like I found whatever was going on in [testing] back in June, but maybe it only comes out when building from ABS.

#14 2015-11-15 06:10:09

Re: sudo: PAM authentication error: Module is unknown

What upgrade process would that be?

The kind you don’t expect to leave you with a bricked computer.

If you mean building a package, installing it, then building another, that’s an unsupported partial update and this kind of breakage is expected.

Online

#15 2015-11-15 07:03:16

Re: sudo: PAM authentication error: Module is unknown

that’s an unsupported partial update and this kind of breakage is expected.

Rather than play 20 questions, when we both know you’re just looking for an excuse to do nothing and that you will find it; why not consider that there is something very dangerous going on with this package and it’s in everyone’s best interest to do something about it.

Just because it doesn’t happen under perfect conditions with the specific version packaged now doesn’t mean it won’t later or in another version of this package, and it’s really dangerous.

Example: If there were a hand grenade under my pillow, but the pin had not been pulled, I could probably sleep on it safely—but I wouldn’t.

Last edited by quequotion (2015-11-15 07:09:07)

#16 2015-11-15 07:15:11

Re: sudo: PAM authentication error: Module is unknown

I’m just using the fact that I happen to know that you like to build everything on your system without actually knowing what you’re doing.

So answer this simple question: Did you run pacman -Syu and update libtirpc at the same time as all packages that depend on it?

Last edited by Scimmia (2015-11-15 07:16:12)

Online

#17 2015-11-15 07:18:36

Re: sudo: PAM authentication error: Module is unknown

Last edited by ewaller (2015-11-15 07:18:56)

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#18 2015-11-15 14:18:03

Re: sudo: PAM authentication error: Module is unknown

rein it in a little.

Sorry if it sounded contentious, I don’t mean to start a fight.

you like to build everything on your system without actually knowing what you’re doing

There are many reasons why I do this, one of them is to find more bugs, another is to learn more about the individual packages.

I’m willing to go through a lot to contribute to better packages; even if my opinion of «better» isn’t required by arch standards.

Last edited by quequotion (2015-11-15 14:18:41)

#19 2015-11-15 17:33:55

Re: sudo: PAM authentication error: Module is unknown

And you still won’t answer the question.

Online

#20 2015-11-15 20:17:27

Re: sudo: PAM authentication error: Module is unknown

And you still won’t answer the question.

I was pretty sure you’d already understood that I was upgrading by building the packages from source.

If you really need something to point at and say «see that’s exactly why. » then yes, I was upgrading with «yaourt -Syub». Just one b; I skipped building dependencies as well this time.

I don’t see why it’s invalid to ask what in libtirpc could be potentially causing a serious problem anyway, as it does seem to cause this problem under certain conditions ([testing] build, incomplete upgrades, etc) and given that Arch is a rolling release that most users upgrade manually, every single installation exists at a different stage of (partial) upgrade. I find it important to know why this isn’t affecting standard installations when it is very easy to trigger; the possibility that this particular package has potential for catastrophic failure seems worth investigating.

Was there ever a followup after the package was pulled from [testing] in June?

Источник

View previous topic :: View next topic

Author

Message

papandreoos
Apprentice

Joined: 17 Dec 2014
Posts: 163

Posted: Fri Jun 19, 2020 12:28 pm Post subject: [SOLVE]i can’t log in any more (problem with pam, su , sudo)

[i’m on testing branch and also uses systemd and gnome with auto log in into gnome (usind sddm)]

yesterday i tried to solve some emerge conflicts and in this process i removed pam (which is one of the packages that had conflicts).

from this moment i can’t get into gentoo (not into gnome directly (it hangs on black screen with a cursor on the top left corner) and not even if i ALT+CTRL+F3 and try to log in manually from there — i enter my username and then my password but it tells me it isn’t correct).

i have access to gentoo in chroot environment from archlinux (i have dual boot).

i also can emerge things from the chroot environment.

when in the chroot environment, if i command: ‘su — myusername’ i get this:

Code:

su: Module is unknown

(Ignored)

and then it «enter» to my user account (i have my user name before the @ sign).

but then if i try to: sudo emerge -a somepackage, i get this error:

Code:

sudo: PAM account management error: Module is unknown

i did (from the chroot) ‘revdep-rebuild’ and it fixed some things (emerge some packages).

i also did: emerge @preserved-rebuild and it installed: pam, shadow, sudo, samba, sddm and couple of more packages but again after reboot i can’t log in (same situation as i described before).

if you need more information, please let me know.

thanks!

[EDIT]

my user is in this groups:

Code:

groups

lp wheel audio cdrom video usb lpadmin portage myusername

and here are my current conflicts (even if it’s not (so i think) connected to my main problem) when i sync and emerge @world (from the chroot environment):

https://pastebin.com/xXfMJSs2

Last edited by papandreoos on Fri Jun 19, 2020 3:05 pm; edited 1 time in total

fturco
Veteran
Veteran

Joined: 08 Dec 2010
Posts: 1181
Location: Italy

Posted: Fri Jun 19, 2020 1:27 pm Post subject:

Try adding the following lines to /etc/portage/package.mask

Code:

=sys-libs/pam-1.4.0-r2

=sys-auth/pambase-20200618

Basically, it seems that SDDM doesn’t support the latest PAM packages.

papandreoos
Apprentice

Joined: 17 Dec 2014
Posts: 163

Posted: Fri Jun 19, 2020 2:00 pm Post subject:

fturco wrote:

Try adding the following lines to /etc/portage/package.mask

Code:

=sys-libs/pam-1.4.0-r2

=sys-auth/pambase-20200618

Basically, it seems that SDDM doesn’t support the latest PAM packages.

did what you suggested, and then:

Code:

emerge -auND —with-bdeps=y —keep-going @world

and it started emerging 40 packages.

after it will finish i will try to restart and see if the problem solved and update here.

thanks!

papandreoos
Apprentice

Joined: 17 Dec 2014
Posts: 163

Posted: Fri Jun 19, 2020 3:05 pm Post subject:

fturco wrote:

Try adding the following lines to /etc/portage/package.mask

Code:

=sys-libs/pam-1.4.0-r2

=sys-auth/pambase-20200618

Basically, it seems that SDDM doesn’t support the latest PAM packages.

you are great!

thank you very much.

my system is working again and i log into gnome (automatically) as before.

also i can log into my username manually using CTRL-ALT-F3 so everything is as before.

again, thank you very much!

fturco
Veteran
Veteran

Joined: 08 Dec 2010
Posts: 1181
Location: Italy

Posted: Fri Jun 19, 2020 5:02 pm Post subject:

https://github.com/sddm/sddm/issues/1265

wrc1944
Advocate

Joined: 15 Aug 2002
Posts: 3408
Location: Gainesville, Florida

Posted: Sat Jun 27, 2020 1:49 am Post subject:

Anyone know of the status of sddm not working with the latest pam and pambase packages, or even if it is being worked on? I’d like to get rid of the mask as soon as possible. _________________ Main box- AsRock x370 Gaming K4 Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5 OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-12.2.1_p2022625 kernel-6.1.10 USE=experimental python3_11

Ionen
Developer

Joined: 06 Dec 2018
Posts: 2459

Posted: Sat Jun 27, 2020 2:30 am Post subject:

wrc1944 wrote:

Anyone know of the status of sddm not working with the latest pam and pambase packages, or even if it is being worked on?

I’d like to get rid of the mask as soon as possible.

I don’t use sddm so can’t confirm it’s fine but sddm-0.18.1-r3 already got a patch for pam 1.4 on gentoo’s side 6 days ago. Patch was apparently broken in -r2 but I believe -r3 is fine looking at commits.

wrc1944
Advocate

Joined: 15 Aug 2002
Posts: 3408
Location: Gainesville, Florida

Posted: Sat Jun 27, 2020 3:20 am Post subject:

Ionen, Thanks much- good to know. _________________ Main box- AsRock x370 Gaming K4 Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5 OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-12.2.1_p2022625 kernel-6.1.10 USE=experimental python3_11

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

agibsonccc opened this issue

Mar 3, 2020

· 6 comments

Comments

Following up on #671
I am still seeing the same issue on centos 8.

I am still running in to this issue on CentOS 8.
Edit: I tried the workaround specified in #769
just to see if it did anything and it doesn’t.
This happens when I try to run:

sudo microk8s.enable storage

Journalctl output:

ar 02 00:14:35 localhost.localdomain microk8s.daemon-proxy[24706]: I0302 00:14:35.147593   24706 shared_informer.go:204] Caches are synced for service config
Mar 02 00:14:35 localhost.localdomain microk8s.daemon-proxy[24706]: I0302 00:14:35.147604   24706 shared_informer.go:204] Caches are synced for endpoints config
Mar 02 00:14:40 localhost.localdomain sudo[25468]: PAM unable to dlopen(/usr/lib64/security/pam_unix.so): /snap/core/current/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/li>
Mar 02 00:14:40 localhost.localdomain sudo[25468]: PAM adding faulty module: /usr/lib64/security/pam_unix.so
Mar 02 00:14:40 localhost.localdomain sudo[25468]:     root : PAM account management error: Module is unknown ; TTY=pts/0 ; PWD=/home/agibsonccc ; USER=root ; COMMAND=/bin/mkdir -p /var/snap/microk8s/common/defau>
Mar 02 00:14:40 localho

Originally posted by @agibsonccc in #671 (comment)

agibsonccc

changed the title
This has not fixed anything for me. I am still running in to this issue on CentOS 8.

microk8s.daemon-kubelet fail to start on CentOS 8

Mar 3, 2020

I’m also seeing this on a fresh install of CentOS on which I installed snap for centOS, then:

snap install microk8s --classic --channel=1.17/edge

and then it will fail this command:

~# microk8s.enable storage
Enabling default storage class
sudo: PAM account management error: Module is unknown
Failed to enable storage

journalctl:

Mar 23 16:50:51 sudo[24490]:     root : PAM account management error: Module is unknown ; TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/mkdir -p /var/snap/microk8s/common/default-storage
Mar 23 16:50:51 sudo[24490]: PAM adding faulty module: /usr/lib64/security/pam_unix.so
Mar 23 16:50:51 sudo[24490]: PAM unable to dlopen(/usr/lib64/security/pam_unix.so): /snap/core/current/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/lib64/s>
Mar 23 16:50:51 sudo[24490]:     root : problem with defaults entries ; TTY=pts/0 ; PWD=/root ; USER=root ;

Current edge:

1.17/edge:        v1.17.4         2020-03-13 (1261) 179MB classic

This ended up working for me without having to modify the snap itself:
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/lib64" microk8s.enable storage

I was experiencing the same PAM module error.
CentOS Linux release 8.2.2004 (Core)

$ snap version
snap    2.45.1-1.el8
snapd   2.45.1-1.el8
series  16
centos  8
kernel  4.18.0-147.el8.x86_64

snap list
Name      Version    Rev   Tracking       Publisher   Notes
core      16-2.45.1  9436  latest/stable  canonical✓  core
microk8s  v1.18.4    1503  latest/stable  canonical✓  classic

I was unable to reproduce this issue on a Centos 8.2.2004 image from osboxes.org. The image was run in Virtualbox. I tried reproducing with both current stable and 1.17 version of microk8s snap package but enabling storage worked in both cases (see screenshot below).

If this issue is still happening it may be useful to get the output (tarball) of microk8s inspect. Also the output of groups command from the terminal may help.

I tried again today and enable storage works. #1557 fixed it as it replaced sudo with run_with_sudo here. Other issues have since fixed sudo in some of the other places I mentioned earlier.

However, microk8s.disable helm for example results in sudo: PAM account management error: Module is unknown. Please replace sudo in these places.

inspection-report-20201023_161939.tar.gz

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Источник

#1 2015-11-12 07:00:51

JasonZhang: Member; From: Shanghai, P.R.C; Registered: 2013-02-01; Posts: 21

sudo: PAM authentication error: Module is unknown

After I `yaourt -S pam gpm`, I can’t login/ssh to my laptop.
Also `sudo su root`, it just prints out ‘sudo: PAM authentication error: Module is unknown’

/var/log/pacman.log:

How can I fix this up? I can’t even roll back to older version of pam.
Can I reboot to single user mode?

Also, why does this update cause this problem?

Thank you.

Last edited by JasonZhang (2015-11-12 07:02:41)

#2 2015-11-12 07:03:11

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

Update your system, partial updates are not supported. If you ever run pacman -Sy, you’re probably doing it wrong.

#3 2015-11-12 07:04:51

JasonZhang: Member; From: Shanghai, P.R.C; Registered: 2013-02-01; Posts: 21

Re: sudo: PAM authentication error: Module is unknown

@Scimmia, thanks for your reply.

But sometimes I don’t want to update some programs which may have different behaviors to the older version or something else.

#4 2015-11-12 07:06:02

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

JasonZhang wrote:

@Scimmia, thanks for your reply.

But sometimes I don’t want to update some programs which may have different behaviors to the older version or something else.

Then you’re using the wrong distro. If you do partial updates, things like this happen. You’re on your own.

#5 2015-11-12 07:07:46

JasonZhang: Member; From: Shanghai, P.R.C; Registered: 2013-02-01; Posts: 21

Re: sudo: PAM authentication error: Module is unknown

Scimmia wrote:

JasonZhang wrote:

@Scimmia, thanks for your reply.

But sometimes I don’t want to update some programs which may have different behaviors to the older version or something else.

Then you’re using the wrong distro. If you do partial updates, things like this happen. You’re on your own.

Emm, but how can I fix this issue up?

#7 2015-11-12 07:08:33

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

Like I said, by updating your system. You may have to boot to a live CD and use pacman —root to do it.

#8 2015-11-12 07:13:06

JasonZhang: Member; From: Shanghai, P.R.C; Registered: 2013-02-01; Posts: 21

Re: sudo: PAM authentication error: Module is unknown

Scimmia wrote:

Like I said, by updating your system. You may have to boot to a live CD and use pacman —root to do it.

I’ll have a try. Thank you.

#9 2015-11-14 15:26:58

quequotion: Member; From: Oita, Japan; Registered: 2013-07-29; Posts: 801; Website

Re: sudo: PAM authentication error: Module is unknown

I have this error from nowhere and nothing in the middle of an upgrade (not a partial upgrade—in the middle of the actual upgrade process).

I need a solution that does not involve rebooting, as there’s a good chance the system will not be recoverable.

I tried to login as root, but this resulted in «login incorrect» before asking for a password.

EDIT: The last successful use of sudo occured when installing libtirpc during the upgrade. I highly suspect this package is broken, which was a known problem in [testing] as of June.

Last edited by quequotion (2015-11-14 15:37:24)

#10 2015-11-14 15:36:43

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

quequotion wrote:

I have this error from nowhere and nothing in the middle of an upgrade (not a partial upgrade—in the middle of the actual upgrade process).

What upgrade process would that be?

If you’re stuck as non-root without working pam, I don’t know what else you can do.

#11 2015-11-14 15:41:12

quequotion: Member; From: Oita, Japan; Registered: 2013-07-29; Posts: 801; Website

Re: sudo: PAM authentication error: Module is unknown

Scimmia wrote:

If you’re stuck as non-root without working pam, I don’t know what else you can do.

If a functional libtirpc package exists, I can install it with pacstrap from the live cd, but it’s a bit of a gamble.

I do not believe a working package exists; I suspect the problem that appeared in testing has passed into the repositories and lots of people are about to have broken PAM.

Last edited by quequotion (2015-11-14 15:42:53)

#12 2015-11-14 15:42:45

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

Nope, current libtirpc works fine. I’ve been running it for over a week.

The issue is upgrading it without upgrading pam (ie, partial update).

Last edited by Scimmia (2015-11-14 15:45:56)

#13 2015-11-15 02:21:14

quequotion: Member; From: Oita, Japan; Registered: 2013-07-29; Posts: 801; Website

Re: sudo: PAM authentication error: Module is unknown

Scimmia wrote:

What upgrade process would that be?

The kind you don’t expect to leave you with a bricked computer.

What is wrong with libtirpc? It looks like I found whatever was going on in [testing] back in June, but maybe it only comes out when building from ABS.

#14 2015-11-15 06:10:09

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

quequotion wrote:

Scimmia wrote:

What upgrade process would that be?

The kind you don’t expect to leave you with a bricked computer.

Specifically?

If you mean building a package, installing it, then building another, that’s an unsupported partial update and this kind of breakage is expected.

#15 2015-11-15 07:03:16

quequotion: Member; From: Oita, Japan; Registered: 2013-07-29; Posts: 801; Website

Re: sudo: PAM authentication error: Module is unknown

Scimmia wrote:

that’s an unsupported partial update and this kind of breakage is expected.

Example: If there were a hand grenade under my pillow, but the pin had not been pulled, I could probably sleep on it safely—but I wouldn’t.

Last edited by quequotion (2015-11-15 07:09:07)

#16 2015-11-15 07:15:11

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

I’m just using the fact that I happen to know that you like to build everything on your system without actually knowing what you’re doing.

So answer this simple question: Did you run pacman -Syu and update libtirpc at the same time as all packages that depend on it?

Last edited by Scimmia (2015-11-15 07:16:12)

#17 2015-11-15 07:18:36

ewaller: Administrator; From: Pasadena, CA; Registered: 2009-07-13; Posts: 19,010

Re: sudo: PAM authentication error: Module is unknown

Okay guys, rein it in a little.
https://wiki.archlinux.org/index.php/Fo … ther_users

Last edited by ewaller (2015-11-15 07:18:56)

#18 2015-11-15 14:18:03

quequotion: Member; From: Oita, Japan; Registered: 2013-07-29; Posts: 801; Website

Re: sudo: PAM authentication error: Module is unknown

ewaller wrote:

rein it in a little.

Sorry if it sounded contentious, I don’t mean to start a fight.

Scimmia wrote:

you like to build everything on your system without actually knowing what you’re doing

There are many reasons why I do this, one of them is to find more bugs, another is to learn more about the individual packages.

I’m willing to go through a lot to contribute to better packages; even if my opinion of «better» isn’t required by arch standards.

Last edited by quequotion (2015-11-15 14:18:41)

#19 2015-11-15 17:33:55

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

And you still won’t answer the question.

#20 2015-11-15 20:17:27

quequotion: Member; From: Oita, Japan; Registered: 2013-07-29; Posts: 801; Website

Re: sudo: PAM authentication error: Module is unknown

Scimmia wrote:

And you still won’t answer the question.

I was pretty sure you’d already understood that I was upgrading by building the packages from source.

If you really need something to point at and say «see that’s exactly why…» then yes, I was upgrading with «yaourt -Syub». Just one b; I skipped building dependencies as well this time.

Was there ever a followup after the package was pulled from [testing] in June?

#21 2015-11-15 20:26:13

jasonwryan: Anarchist; From: .nz; Registered: 2009-05-09; Posts: 30,376; Website

Re: sudo: PAM authentication error: Module is unknown

quequotion wrote:

Arch is a rolling release that most users upgrade manually, every single installation exists at a different stage of (partial) upgrade.

This is only true for people that don’t -Syu: which is why it is unsupported. The Arch model depends upon full system upgrades.

Arch + dwm • Mercurial repos • Surfraw

Registered Linux User #482438

#22 2015-11-15 20:30:59

Scimmia: Fellow; Registered: 2012-09-01; Posts: 10,046

Re: sudo: PAM authentication error: Module is unknown

quequotion wrote:

Scimmia wrote:

And you still won’t answer the question.

I was pretty sure you’d already understood that I was upgrading by building the packages from source.

If you really need something to point at and say «see that’s exactly why…» then yes, I was upgrading with «yaourt -Syub». Just one b; I skipped building dependencies as well this time.

So yes, your entire problem comes from the partial update. This is not supported for exactly this reason.

quequotion wrote:

I don’t see why it’s invalid to ask what in libtirpc could be potentially causing a serious problem anyway

It doesn’t, though. It’s a soname bump the same as hundreds of soname bumps that Arch has had.

quequotion wrote:

as it does seem to cause this problem under certain conditions ([testing] build, incomplete upgrades, etc) and given that Arch is a rolling release that most users upgrade manually, every single installation exists at a different stage of (partial) upgrade.

This is flat out false. A partial upgrade is when you update a library or program without updating everything else on your system to the most current version available at exactly the same time. No Arch installations should exist in this state.

quequotion wrote:

I find it important to know why this isn’t affecting standard installations when it is very easy to trigger; the possibility that this particular package has potential for catastrophic failure seems worth investigating….

Was there ever a followup after the package was pulled from [testing] in June?

It was fixed immediately.
https://projects.archlinux.org/svntogit … 89441b01d0
This has nothing to do with that at all.

#23 2015-11-28 17:19:35

amaro: Member; From: 5.11.1-1-ck-ivybridge, xfce; Registered: 2014-05-09; Posts: 354

Re: sudo: PAM authentication error: Module is unknown

I had this problem recently. I fixed it from an existing LMDE I have on a different partition.
I boot into LMDE

$ su root
# fdisk -l
/dev/sda4       446341120 976773119 530432000   253G 83 Linux
# mkdir /mnt/sda4
# mount /dev/sda4 /mnt/sda4
# cd /mnt/sda4
# mount -t proc proc proc/
# mount --rbind /sys sys/
# mount --rbind /dev dev/
# cp /etc/resolv.conf etc/resolv.conf
# chroot /mnt/sda4
# pacman -Syyu
:: Proceed with installation? [Y/n] y
# exit
# cd /
# umount --recursive /mnt/sda4/
# reboot

Last edited by amaro (2015-11-30 13:44:07)

#24 2015-11-30 10:50:10

quequotion: Member; From: Oita, Japan; Registered: 2013-07-29; Posts: 801; Website

Re: sudo: PAM authentication error: Module is unknown

amaro wrote:

I had this problem recently. I fixed it from an existing LMDE I have on a different partition.

This is a very helpful reply, and it reminds me that we might need a wiki page especially for ways to recover «bricked» installations.

#25 2015-11-30 10:56:24

WorMzy: Forum Moderator; From: Scotland; Registered: 2010-06-16; Posts: 11,019; Website

Re: sudo: PAM authentication error: Module is unknown

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Источник

This document (7022033) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)
SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)
SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)
SUSE Linux Enterprise Server 12

Situation

When logging into the ncurses console as root, an error is displayed «Module is unknown» and root cannot login. Other login methods seem to work, like ssh. The system log /var/log/messages shows the following:

2017-10-06T10:27:01.754068-06:00 sles12sp3 login: PAM unable to dlopen(/lib/security/pam_limits.so): /lib/security/pam_limits.so: cannot open shared object file: No such file or directory
2017-10-06T10:27:01.754981-06:00 sles12sp3 login: PAM adding faulty module: /lib/security/pam_limits.so
2017-10-06T10:27:02.761812-06:00 sles12sp3 login: pam_unix(login:session): session opened for user root by LOGIN(uid=0)

The /etc/pam.d/login file shows the following:

session required /lib/security/pam_limits.so

Resolution

Provide a correct path to the pam_limits.so module. Edit /etc/pam.d/login and change:

session required /lib/security/pam_limits.so

to this:

session required pam_limits.so

Likewise, if the module name is incorrect, like pam_limit.so instead of pam_limits.so, the same error would occur.

Cause

Invalid PAM module path.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented «AS IS» WITHOUT WARRANTY OF ANY KIND.

Document ID:7022033
Creation Date:
06-Oct-2017
Modified Date:03-Mar-2020
- SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

Источник