On Fri, 21 Feb 2003, Harry Putnam wrote: > I've gotten myself into quite a pickle with todays attempt to update. > > up2date -u showed these: > > lynx-2.8.5-7.1.i386.rpm pam-devel-0.75-46.8.0.i386.rpm > pam-0.75-46.8.0.i386.rpm shadow-utils-20000902-12.8.i386.rpm > > I downloaded them since I have up2date set to only download. Had a > look, then ran up2date -u -i -k /var/spool/up2date which in my case > would just rescan for needed packages then install them from where I > downloaded them. Its how I've been doing it for a while now. > > The installation started ok, with lynx. Ran through the hash siqns > lynx ################################## 100 percent > > And then just stopped, but never returned the prompt. I thought > maybe a network drop might cause that, if up2date was still talking > to rhn. But no, its something worse. > > I killed that process and ran `rpm -q lynx' to see if that had gotten > installed. Again the process hung. > > So I guessed it may be related to the `pam' stuff somehow. So tried > `rpm -Uvh pam*.rpm'. Again it just hangs. Tailing /var/log/messages > gives nothing usefull about this that I can see. > > I can't run any rpm commands as root or even with sudo without it just > hanging. User can run rpm commands fine. > > I'm reasonably sure its related to a failed install of pam rpms in > some way, but can't see anything to do about it. > Maybe going to telinit 1 and shuting down everthing shuttable will be > a way out. > > Wondered if anyone else had seen anything weird like this? yes, have it seen 2 or 3 times, it's more or less a feature. To work-around, you have to recreate the rpm database. You will see that lynx got installed, and the rest not. Cheers, Michael -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
