Becareful with up2date over SSH session

Stephen Smoogen <[email protected]> Sat, 31 Jul 2004 11:03:22 -0600 (MDT)
Newsgroups gmane.linux.redhat.taroon
Message-ID <[email protected]>
I tried bringing up a RHEL ES system yesterday to the beta channel 
yesterday. I followed the usual procedure I do with any RHEL box which 
is to log in via SSH and then do a /usr/sbin/up2date --nox -u

This normally works and works in most of my beta testing before. However 
right after downloading all the packages and beginning to update 
packages, ssh was killed after glibc was updated. This killed the 
up2date and the DB was in a bad state. It looks like about 20 packages 
were still on the disk but not in the database so when I was able to get 
the system going again.. I needed to do a manual rebuild of the RPM 
database, and then an rpm -Uvh --force /var/spool/up2date/*rpm and then 
go through the various .rpmsave/new/orig files to see what had been 
'lost'. Thankfully not a lot that I can tell.

The second problem was that I had prelinked the system and so various
libraries and binaries (/bin/su, /usr/bin/write, various pbm libs) items
came up as being bad. To get around that I needed to un-pre-link the
items, and then rpm -Uvh --force the affected packages again. I havent 
tried prelinking them again until after U3 is done. :).

-- 
Stephen John Smoogen		[email protected]
Los Alamos National Lab  CCN-5 Sched 5/40  PH: 4-0645
Ta-03 SM-1498 MailStop B255 DP 10S  Los Alamos, NM 87545
-- "We cannot have a free government without elections; and if the
-- rebellion could force us to forgo, or postpone, a national election,
-- it might fairly claim to have already conquered us." Abraham Lincoln


--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list