Bug 85314 - up2date hangs when invoked from firstboot
up2date hangs when invoked from firstboot
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-27 16:53 EST by Tom Riddle
Modified: 2007-04-18 12:51 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-20 16:10:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tom Riddle 2003-02-27 16:53:46 EST
Description of problem:
Performed an install from CD using anaconda.  Selected Custom/Everything,
everything else left as default.  Installed packages ok, rebooted, registered
for rhn from within firstboot, changed up2date config to remove kernel* from and
add kde-i18n-* to skiplist, ran up2date.  It downloaded rpms ok, but hung on
installing first package (WindowMaker). By hung, I mean the window stopped
refreshing.  I telnet'ed in from another machine and discovered a couple of
curious things:

- the size of my RPM database was huge: Packages file was ~40Mb, Basename was
~10Mb, whereas on another identical install these files as ~16Mb and ~2.7Mb
- strace of the up2date process revealed that it was looping in:
select(0,NULL,NULL,NULL,{1,0}) = Timeout
- attempts to use rpm command resulted in the same strace

Version-Release number of selected component (if applicable):


How reproducible:
unable to reproduce


Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:

Note You need to log in before you can comment on or make changes to this bug.