[K12OSN] yum update broke my 5.0.0

[Eric Harrison]

On Tue, 6 Jun 2006, Rob Owens wrote:

> I did a yum update on K12LTSP 5.0.0 and my system is
> hosed!  One of the bootup messages I get is something
> like "libpam.so.O cannot open shared object"...
>
> What's the easiest way to fix my system?  I googled
> and tried rpm -Uhv --rollback 'june 5' and it seemed
> to do something, but didn't fix my problem.  (My
> machine is dual-boot, and I used the chroot command
> from my good system to try this command).
>
> I cannot log in through GDM, ssh, or a shell.  Any
> help would be appreciated.
>
> -Rob

The pam (Pluggable Authentication Modules) package was recently 
updated, given your errors that is a good place to start ;-)

There are two possible causes come to mind: 1) the post-install
script failed or 2) the package failed mid-installation.

The way a package upgrade works is that the new package is installed,
then the old package is removed. If the update failed mid-process (#2),
the old libraries should be there and everything should still work. So
I'm guessing that the post-install script (#1) is the problem.

So lets see if I guessed correctly... (NOTE: I assume that you are
using the 32bit version, if you have the 64bit version installed these
instructions will have to be modified slightly - let us know if that is 
the case)

1) boot up on your working partition, mount the broken partition (but
    don't do the chroot yet!). Let's use /mnt/broken for this example

2) cd to the new mount point

         cd /mnt/broken

3) fetch a copy of the latest pam package, just in case we need to
    reinstall it later. You can get this from any Fedora updates
    mirror, for simplicitie's sake here is a direct link to the
    K12LTSP mirror:

         wget ftp://k12linux.mesd.k12.or.us/pub/K12LTSP/testing/5.0.0-32bit/updates/pam-0.99.4.0-fc5.4.i386.rpm

4) now chroot to your broken partition (chroot /mnt/broken)

5) check to see if the pam libraries are there, the out put should look
    exactly like this:

     # ls -l /lib/libpam*
     lrwxrwxrwx 1 root root    17 Jun  6 20:46 /lib/libpamc.so.0 -> libpamc.so.0.81.0*
     -rwxr-xr-x 1 root root 10052 May 24 06:26 /lib/libpamc.so.0.81.0*
     lrwxrwxrwx 1 root root    21 Jun  6 20:46 /lib/libpam_misc.so.0 -> libpam_misc.so.0.81.2*
     -rwxr-xr-x 1 root root  8952 May 24 06:26 /lib/libpam_misc.so.0.81.2*
     lrwxrwxrwx 1 root root    16 Jun  6 20:46 /lib/libpam.so.0 -> libpam.so.0.81.3*
     -rwxr-xr-x 1 root root 48056 May 24 06:26 /lib/libpam.so.0.81.3*


   The really import files are /lib/libpamc.so.0.81.0,
   /lib/libpam_misc.so.0.81.2, and /lib/libpam.so.0.81.3. If those are there,
   all you will probably need to do is run ldconfig. If not, we'll need
   to reinstall the pam package.

   If the /lib/libpam*.so.0.81.* files exist:

     1) run:

         ldconfig

     2) double-check that the symlinks are now correct by running ls again:

         ls -l /lib/libpam*

     3) if it looks right now, you should be able to reboot and be back
        in business


   If the /lib/libpam*.so.0.81.* files DO NOT exist:

     1a) run:  (reinstall the pam package you downloaded earlier)

             rpm -Uhv /pam-0.99.4.0-fc5.4.i386.rpm

     1b) if that bombs out with an error, run this instead:

             cd /
             rpm2cpio  /pam-0.99.4.0-fc5.4.i386.rpm | cpio -id

     2) tell the system to go check for new libraries:

             ldconfig

     3) and double-check that the symlinks are now correct by running ls again:

             ls -l /lib/libpam*

     4) if it looks right now, you should be able to reboot and be back
        in business



Finally, once all is working, double-check that the RPM database has the
right information. Run this command:

 	rpm -V pam

It should either run without output, or a single line that looks like this:

 	S.5....T. c /etc/pam.d/system-auth

If it says that the package is not installed or lists a whole bunch of lines,
let us know and we'll jump through a few more hoops...

-Eric