Issue Updating To 7.6

Home » CentOS » Issue Updating To 7.6
CentOS 2 Comments

Hi all… Great work on 7.6!

I updated a number of boxes – all good! This “one” server I lost connection through the internet or something… Anyway 702 transactions left and its not happy. When I run yum-complete-transaction I get “many”

Removing man-db.x86_64 0:2.6.3-9.el7 – ud from the transaction Removing man-db.x86_64 0:2.6.3-11.el7 – u from the transaction Removing python-ethtool.x86_64 0:0.8-5.el7 – ud from the transaction Removing python-ethtool.x86_64 0:0.8-7.el7 – u from the transaction Removing iprutils.x86_64 0:2.4.15.1-1.el7 – ud from the transaction Removing iprutils.x86_64 0:2.4.16.1-1.el7 – u from the transaction Removing strace.x86_64 0:4.12-6.el7 – ud from the transaction Removing strace.x86_64 0:4.12-9.el7 – u from the transaction

and then nothing happens…. (This is just a short list) many are printed.

Thoughts? What next?

Jerry

2 thoughts on - Issue Updating To 7.6

  • Not of any direct help to you now, but I learned the hard way that it’s always wise to run yum in a screen session when updating anything other than your local computer. That way if your connection to the box drops everything will just keep on truckin’ anyway and you can reconnect any time and it’s just like nothing bad happened at all.

  • I had a spurious problem on updating large number of packages which would cause a similar problem. I needed to break the update on these systems into 2 transactions:
    1. yum update –skip-broken –exclude=”gdm*” –exclude=”java-1.7.0″
    –exclude=”NetworkManager*” –exclude=”ModemManager*”
    2. yum update

    Not every system did this and there didn’t seem to be a rhyme or reason on why it happened for the ones I ran into it (plenty of memory, plenty of CPU, etc etc)