Suppose there are a number of updates to download to a given machine.
Up2date accurately identifies them, offers them to the user and downloads
the .hdr files. It then properly begins downloading file one. After the
file has reached 100% downloaded (top status bar), the update agent seems
to just hang, and the second status bar (overall progress) doesn't update.
If the user runs xkill to kill the agent, they can then rerun the agent. It
will offer the same files(which the user again selects), recognizes the
.hdr files are already there, recognizes the first file is already
downloaded and update the overall status bar. The download of the next file
then begins, but hangs at the end of the download of that file. Again,
xkilling the agent and following the same process allows the user to
continue through the selected patches.
Once this process has been repeated for the remaining updates, the
installation occurs normally, but the .hdr files are not automatically
something strange must be happening on your system. can you run 'up2date' from
the command line, not from the menu, and see if any errors appear in the
terminal window at the point where it hangs please?
That produced the following error:
Traceback (innermost last):
File "/usr/share/rhn/up2date/gui.py", line 350, in doRetrieval
File "/usr/share/rhn/up2date/up2date.py", line 527 in getPackage
up2date.CommunicationError: Error communicating with server. The message was:
Invalid RPM package requested:
Does this mean there is no source package available, or is it looking in the
source package retrieval should be fixed at this moment, but I am asking the
developer to double check. For now, if you are still experiencing trouble, a
simple work around would be to turn off the "retrieve source packages" option
in the /etc/sysconfig/rhn/up2date config file.
Cristian, can you check the source package retrieval code please?
souce package retrieval has been corrected in up2date 2.1.7.