Can not update a freshly loaded Red Hat Enterprise Linux AS

Robert Williams rwilliams at covenantdata.com
Wed May 18 15:45:09 UTC 2005


I also ran into the problem during installation.  It also has to do
something with either the physical hard drive or the main board.  It might
be helpful to make sure all the machines (if you can) are identical to avoid
that and to narrow down the possible problems.

 
Robert Williams
Programmer / Web Developer / Network Administrator
Covenant Data Systems, Inc.
http://www.covenantdata.com
rwilliams at covenantdata.com  
 

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com]
On Behalf Of Robert Williams
Sent: Wednesday, May 18, 2005 10:29 AM
To: 'General Red Hat Linux discussion list'
Subject: RE: Can not update a freshly loaded Red Hat Enterprise Linux AS

I have ran into that same problem from time to time.  I am using Fedora Core
3 and sometimes get errors like that.  I just ignore the updates until
either later on in the day or the next day.  It could be too many updates on
the same network.  I know Red Hat use to have a distribution method for
installing updates across multiple servers.  But that was back in the day of
RH 7.2

 
Robert Williams
Programmer / Web Developer / Network Administrator
Covenant Data Systems, Inc.
http://www.covenantdata.com
rwilliams at covenantdata.com  
 

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com]
On Behalf Of Dave Basener
Sent: Wednesday, May 18, 2005 10:06 AM
To: General Red Hat Linux discussion list
Subject: Can not update a freshly loaded Red Hat Enterprise Linux AS

I have a new academic license for 9 machines.  The first machine went 
fine, but the second machine has been the same problem after 4 separate 
full, clean installs.  I have varied the package mix and in the latest I 
used the default packages.

When I run up2date it downloads the 2 up2date packages that it suggests 
I update first  and then hangs.  The log file has:

[Wed May 18 09:31:35 2005] up2date updating login info
[Wed May 18 09:31:35 2005] up2date logging into up2date server
[Wed May 18 09:31:36 2005] up2date successfully retrieved authentication 
token from up2date server
[Wed May 18 09:31:47 2005] up2date availablePackageList from network
[Wed May 18 09:33:10 2005] up2date solving dep for: ['up2date']
[Wed May 18 09:33:12 2005] up2date solving dep for: ['up2date']
[Wed May 18 09:34:10 2005] up2date installing packages: 
['up2date-4.4.5.6-2', 'up2date-gnome-4.4.5.6-2']
[Wed May 18 09:34:16 2005] up2date RPM dependency error. The message was:
Dependencies should have already been resolved, but they are not.

==============================


The response to the command line (up2date) is:

Traceback (most recent call last):
  File "/usr/share/rhn/up2date_client/gui.py", line 2158, in doInstallation
    kernelsToInstall = up2date.installPackages(self.selectedPkgList, 
self.rpmCallback)
  File "/usr/share/rhn/up2date_client/up2date.py", line 752, in 
installPackages
    runTransaction(ts, added, removed,rpmCallback, rollbacktrans = 
rollbacktrans)
  File "/usr/share/rhn/up2date_client/up2date.py", line 618, in 
runTransaction
    "but they are not."), deps)
up2date_client.up2dateErrors.DependencyError: RPM dependency error. The 
message was:
Dependencies should have already been resolved, but they are not.

===============================

If I just try to rpm the 2 up2date rpms:

rpm --install up2date-4.4.5.6-2.i386.rpm up2date-gnome-4.4.5.6-2.i386.rpm
error: rpmdbNextIterator: skipping h#      74 Header V3 DSA signature: 
BAD, key ID db42a60e
error: rpmdbNextIterator: skipping h#     102 Header V3 DSA signature: 
BAD, key ID db42a60e
error: rpmdbNextIterator: skipping h#      74 Header V3 DSA signature: 
BAD, key ID db42a60e
error: rpmdbNextIterator: skipping h#      74 Header V3 DSA signature: 
BAD, key ID db42a60e
error: rpmdbNextIterator: skipping h#      65 Header V3 DSA signature: 
BAD, key ID db42a60e
error: Failed dependencies:
        /usr/bin/python is needed by up2date-4.4.5.6-2.i386
        mkinitrd >= 3.2.2 is needed by up2date-4.4.5.6-2.i386
        python >= 2.2.2 is needed by up2date-4.4.5.6-2.i386
        python-optik is needed by up2date-4.4.5.6-2.i386
        sh-utils is needed by up2date-4.4.5.6-2.i386
        /usr/bin/python is needed by up2date-gnome-4.4.5.6-2.i386
    Suggested resolutions:
        coreutils-5.2.1-31.i386.rpm
        mkinitrd-4.1.18-2.i386.rpm
        python-2.3.4-14.i386.rpm

=============================

Now, I already have coreutils-5.2.1-31 
<https://rhn.redhat.com/network/software/packages/details.pxt?sid=1005568695
&id_combo=35203%7c251001> 
, mkinitrd-4.1.18-2 
<https://rhn.redhat.com/network/software/packages/details.pxt?sid=1005568695
&id_combo=500000012%7c90945>, 
python-2.3.4-14 
<https://rhn.redhat.com/network/software/packages/details.pxt?sid=1005568695
&id_combo=500000210%7c37620> 
but I'm a good sport and so I downloaded these from RH and ran the rpm 
again:

I am now given a new list of RPMs that I should get - which I, according 
to RHN, already have, but that's OK, I'm game - I download   
ncurses-5.4-13 
<https://rhn.redhat.com/network/software/packages/details.pxt?sid=1005568695
&id_combo=500000009%7c241139> 
and module-init-tools-3.1-0.pre5.3 
<https://rhn.redhat.com/network/software/packages/details.pxt?sid=1005568695
&id_combo=38423%7c247334> 
and try again.

Now I just get:
"error: rpmdbNextIterator: skipping h#      65 Header V3 DSA signature: 
BAD, key ID db42a60e"
repeated until universal heat-death.

BTW, querying a package doesn't work either:
rpm --query python-2.3.4-14.i386 coreutils-5.2.1-31
error: rpmdbNextIterator: skipping h#      74 Header V3 DSA signature: 
BAD, key ID db42a60e
error: rpmdbNextIterator: skipping h#      65 Header V3 DSA signature: 
BAD, key ID db42a60e


Does any one have any suggestions?  Anything obvious that I am doing 
wrong?  RedHat has already told me that they don't want to talk to me 
because I have an Academic License. At some point I am going to conclude 
that being unable to upgrade a machine because of errors that their tool 
tells me it should have been able to avoid is a violation of the license.

Thanks for any help at all.

Dave Basener

-- 
"... be the change you wish to see in the world."  - Gandhi

David Basener               http://www.aurora.edu/~dbasener
System Administrator                Dave.Basener at aurora.edu
Aurora University                              630 844 4889

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list






More information about the redhat-list mailing list