CentOS - Sep 2006 - Safely updating to 4.4 via yum (chicken)

Hi guys:

I saw the pelthora of threads where people had trouble moving to 4.4.  So 
I'm chicken now and I was trying to wait for the dust to settle,  I suppose 
it has and its been long enough I'm nervous about not upgrading.  I need to 
do a  a production server that is located in a data center far away so even 
more than normal I want a smooth upgrade.

Can someone tell the what the concensous was on the best way to do the 
upgrade and avoid problems.  From my notes I got:

yum upgrade python-sqlite
yum upgrade sqllite
yum upgrade yum
yum clean all
yum update

But at least one guy said his box was still hosed with duplicates and a 
broken bind after that.

What's the method to upgrade 4.3-> 4.4 with the highest change of sucess?

Thanks very much for the help.

Scott

techlist wrote:
> Can someone tell the what the concensous was on the best way to do the 
> upgrade and avoid problems.  From my notes I got:
>
> yum upgrade python-sqlite
> yum upgrade sqllite
> yum upgrade yum
> yum clean all
> yum update
>
> But at least one guy said his box was still hosed with duplicates and 
> a broken bind after that.
>
> What's the method to upgrade 4.3-> 4.4 with the highest change of
sucess?

That procedure should be fine.  The broken bind thing happens when 
people have the caching nameserver installed.  I always delete it if the 
machine needs to run as a nameserver.

Cheers,

On 9/24/06, techlist <techlist06 at msws.org>
wrote:
>
> Can someone tell the what the concensous was on the best way to do the
> upgrade and avoid problems.  From my notes I got:
>
> yum upgrade python-sqlite
> yum upgrade sqllite
> yum upgrade yum
> yum clean all
> yum update
I just went through exactly that series and got the futex hang in
cleanup anyway.  On the other hand, on a different machine (used by
only one person and not a server, so less important) I simply did "yum
upgrade" and had no trouble.

The other suggestion that's been on the list that I *didn't* try
(because I wanted to avoid multiple reboots) was:

rm /var/lib/rpm/__db*
shutdown -r now
yum upgrade python-sqlite sqlite yum
yum clean all
yum upgrade
shutdown -r now

To recover from the futex hang on my first pass, I did

rpm -qa --qf "%{NAME}*.%{arch}.rpm\n" | sort | uniq -d | fgrep -v
gpgkey |
   xargs -i find /var/cache/yum -name {} | sort -u > /tmp/reinstall

This produces a list of the packages that failed to clean up properly.
 Edit /tmp/reinstall for sanity, then run

rpm -Uvh --force `cat /tmp/reinstall`

Then run "updatedb" and do a "locate" on rpmnew and rpmsave
to look
for files that may need manual attention.  (William Maltby's
suggestion.)

On Sun, 2006-09-24 at 10:41 -0500, techlist wrote:
> What's the method to upgrade 4.3-> 4.4 with the highest change of
sucess?
	I know this is like a month late and probably not much help but my
server that's running CentOS started at 4.0 installed by CD but then has
been upgraded to 4.1, 4.2, 4.3, 4.4 all through yum.  No problems that I
have found.

-- 
Boring Home Page - http://www.webtrek.com/joe
See my blog, sumo game ranks and other interesting junk