After installing GLIBC 2.3.2 -> No Login possible
 

Hi,

I can't login to my system. After typing the username a "Login Incorrect" appears, without having a chance typing my password.

The log-file says:

su: PAM unable to dlopen(/lib/security/pam_unix.so)
su: PAM [dlerror: /lib/libnss_nisplus.so.2: versioin 'GLIBC_2.1' not found (required by /lib/security/pam_unix.so)]

My System is a
Suse Linux 7.2 distribution
on a
ProLiant 1600 Server

What I did before the crash (Damn, I am a stupid Boy :)):
I updated my glibc to 2.3.2, after that I wasn't able to login...

I am able to login using "LINUX = SINGLE" at the boot prompt, but then I have a read-only-filesystem, so I can't downgrade the GLIBC. :-(

--- EDITED on 08/14/04 02:20---
Ok, I found out, that I am able to remount the filesystem to a writeable one.

But "rpm -e glibc...." doesn't work because it only prompts: "glibc... is not installed"

:(

help

--- END ---

Any ideas?

thank you

Timo Meinen
meinen@gmx.de

You may want to try updating pam.
Simon

hmmm... something else occurs: since rpm -e glibc... dosn't work 'cause it says it's not installed, try rpm -U glibc... and see if it says it's installed.
Simon

I know it's not what you want to hear, but I imagine you suspect it already. You basically hosed your system. Updating glibc is a _very_ risky thing to do, and shouldn't be attempted unless:

1. You have a desperate need to update.
2. You know exactly what you're doing.

The reason is that glibc (the gnu c library) is used by almost every binary executable on your system and something _will_ break. If rpm is in fact still funtional you might try reverting to the earlier version of glibc, something like rpm -Uvh --force packagename.rpm. Be warned that is rather drastic and I can't guarrantee a good outcome.

Good luck. Kevin

Solution
 

Thanks for your posts.

We got the system back to work. The solution:

- booting in single mode (at boot: linux init=/bin/bash)
- remounting the harddrive, to be writeable (mount -o remount,rw /)
- we copied the old glibc-2.2.2-38 from the distribution cd (SuSE 7.2 in path /full-names/i386/) to the harddrive
- deinstalling the new glibc (rpm -e glibc-2.3.2-92 --nodeps)
- installing the old glibc-2.2.2-38 (rpm -ivh glibc-2.2.2-38.rpm)

Thanks a lot.


Timo