[rhn-users] Up2date failure message - OSError - no such file or directory

[Wakeman, Lindsay]

Hi,

 I ran up2date on a RHEL3 system this morning to pick up some new kernel
updates. It displayed an error (see below) and the GUI hung, eventually
requiring interruption. However, the RHN database claimed that the
updates were reported as installed successfully. 

           Here's the error:

[root at lx-dev-max root]# up2date -i
Traceback (most recent call last):
  File "/usr/share/rhn/up2date_client/gui.py", line 2150, in
doInstallation
    kernelsToInstall = up2date.installPackages(self.selectedPkgList,
self.rpmCallback)
  File "/usr/share/rhn/up2date_client/up2date.py", line 629, in
installPackages
    hdr = getRealHeader(pkg)
  File "/usr/share/rhn/up2date_client/up2date.py", line 171, in
getRealHeader
    fd = os.open(fileName, os.R_OK)
OSError: [Errno 2] No such file or directory:
'/var/spool/up2date/kernel-2.4.21-32.0.1.EL.i686.rpm'

           [ had to be aborted here]

The same process worked fine on 2 other machines and these 2 report an
extra RPM that is missing on the failed system -
kernel-source-2.4.21-32.0.1.EL

 Anyone know what may have caused the error, and/or the hangup, and how
I should recover?

  TIA

  Lindsay

**************************************************************************
 
Experience the British Library online at www.bl.uk
 
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook
 
**************************************************************************
 
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the postmaster at bl.uk : The contents of this e-mail must not be disclosed or copied without the sender's consent. 
 
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author. 
 
**************************************************************************