Up2date Misbehaves...Slowly

billg billg at f-m.fm
Fri Dec 26 23:06:55 UTC 2003


I did a fresh FC1 install today on a machine that has previously run
Fedora quite happily and glitch free.  

Today, though, up2date is misbehaving.

Here's the story:

1.  Select the "Install Everything" option and feed the machine all 3
CD's
2.  When the install is over, firstboot runs with no problems.
3.  This is a desktop machine, so turn off a bunch of services.
4.  Run up2date (no tweaking of souces)
5.  Opt to download every update, including kernels
6.  Download proceeds as if in thick molasses, with bogus GPG error
flashing several times thanks to overwhelmed server
7.  After several hours, downloads complete.  I tell up2date to go ahead
and install
8.   Happily spinning hourglass appears...and spins for 45 minutes or so.
 Progress bar does not progress across the graphic.  Hard drive is not
busy.
9.  I kill up2date and relaunch it.  Up2date proceeds to start
downloading everything again.
10. Sigh....

Now, I run up2date from the commandline, and sometime before I relaunched
it, it produced this error message:

"[root at slipstream root]# up2date
"Traceback (most recent call last):
"  File "/usr/share/rhn/up2date_client/gui.py", line 2070, in
doInstallation
"    kernelsToInstall = up2date.installPackages(self.selectedPkgList,
self.rpmCal lback)
"  File "/usr/share/rhn/up2date_client/up2date.py", line 619, in
installPackages
"    raise up2dateErros.RpmError("%s" % e)
"NameError: global name 'up2dateErros' is not defined
"[root at slipstream root]# up2date
"[root at slipstream root]#"

What's happening?  Where are all the downloaded packages?  Can they be
installed manually? 

Thanks,

Billg





More information about the users mailing list