Why does debian get an error when booting the system: su: Permission denied (ignored)?

U

ur3ckr2013-12-21 15:36:54

linux

ur3ckr, 2013-12-21 15:36:54

Hello. An interesting situation:
we have a mini server with the Debian 6 console installed.
There was a problem with the disk, the Ext3 file system fell off.
The pmagic lifesd turned out to be at hand and with the help of the wonderful fsck command, the partition was restored, but several libraries were broken (libreadline, libpam*, etc. ) The libraries were copied from lifesd and the system, although with an error about the wrong libreadline file, started up. Then I tried to restore the native debian libraries with the command apt-get install --reinstall <package name>
The system wrote about restoring the library to its original state. And successfully worked half a day. After rebooting the system, we have the following problem: su: Permission denied (ignored) login
is written 4 times :
But when entering the login of both a simple user and root, the system issues - login incorrect - and I can’t log in
. In safe mode, it lets root under the password, but when typing su or sudo -i, it also gives Permission denied (ignored)
In the system log there is such

CRON[4831]: PAM (other) no module name supplied
CRON[4832]: PAM (other) illegal module type: @include

Googling on this topic did not help much, or rather found a similar topic , but without an answer.
There is a backup, but it's more interesting to play around with this situation.
I'll be glad for any hint.

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

Y

Yuri Yarosh, 2013-12-21
@d00mko

You need to completely reinstall pam
apt-get install -f --reinstall libpam0g libpam-cracklib libpam-modules libpam-modules-bin libpam-runtime
apt-get purge libpam0g libpam-cracklib libpam-modules libpam-modules-bin libpam-runtime
apt- get install -f --reinstall libpam0g libpam-cracklib libpam-modules libpam-modules-bin libpam-runtime

U

ur3ckr, 2013-12-21
@ur3ckr

Unfortunately it didn't help

P

proDOOMman, 2013-12-21
@proDOOMman

1) Check the checksums of all packages and reinstall the broken ones.
The check is run like this:
# apt-get install debsums
# debsums -as
2) Check manually the pam configs in the /etc/pam.d/ directory.

V

Valentine, 2013-12-22
@vvpoloskin

Disable pam from livecd, boot into normal system. If everything is good and if it is interesting to play around, we take and put in turn the original Debian libs from deb-packages.