• Skip to primary navigation
  • Skip to content
  • Skip to primary sidebar

The Geek Diary

HowTos | Basics | Concepts

  • Solaris
    • Solaris 11
    • SVM
    • ZFS
    • Zones
    • LDOMs
    • Hardware
  • Linux
    • CentOS/RHEL 7
    • RHCSA notes
    • SuSE Linux Enterprise
    • Linux Services
  • VCS
    • VxVM
  • Interview Questions
  • oracle
    • ASM
    • mysql
    • RAC
    • oracle 12c
    • Data Guard
  • DevOps
    • Docker
    • Shell Scripting
  • Hadoop
    • Hortonworks HDP
      • HDPCA
    • Cloudera
      • CCA 131

understanding “yum history” command output

By admin

“yum history” is an often overlooked but really useful feature provided in the CentOS/RHEL/Fedora systems. It allows you to perform a load of additional features that can save your skin in an enterprise environment.

It allows you to turn back the proverbial clock to the last functioning state of an application should there be an issue with a package update, without having to worry about dependencies and so on. Shown below is an example of “yum history” command output.

yum history command CentOS RHEL

Understanding the “yum history” command output

Possible values and descriptions of the columns are shown below when checking a system’s yum transactions history. The “yum history” command outputs a table with the following columns:

ID

The ID number of the transaction detailed in that row.

Login user

The user that executed the action. It can show the Full Name and/or username in system. When showing “System [unset]” its because it was not executed by a normal user but instead by system for an automatic update.

Date and time

The time stamp (DATE + TIME) of the transaction start execution.

Action(s)

Possible action executed in the transaction.

Value Action Description
I Install Package(s) installed.
U Update Package(s) updated to a newer version.
E Erase Package(s) removed.
D Downgrade Package(s) downgraded to an older version.
O Obsoleting Package(s) marked as obsolete.
R Reinstall Package(s) reinstalled.

Altered

Number of packages altered in the transaction, followed by some extra information if any available.

Value Description
< The rpmdb database was changed outside Yum before the transaction ending.
> The rpmdb database was changed outside Yum after the transaction ended.
* The transaction failed to finish
# Finished successfully, but yum returned a non-zero exit code.
E Finished successfully, but an error or a warning was displayed.
P Finished successfully, but problems already existed in the rpmdb database.
s Finished successfully, but the –skip-broken command-line option was used and certain packages were skipped.
“yum history” command examples to display, rollback, redo, undo yum transactions
CentOS / RHEL 6,7 : How to use yum history to roll back a yum update
CentOS / RHEL : How to view the commands executed in yum history command output

Filed Under: CentOS/RHEL 6, CentOS/RHEL 7, Linux

Some more articles you might also be interested in …

  1. CentOS / RHEL : How To Check FC Brocade HBA Firmware
  2. CentOS / RHEL 7 : How to enable or disable automatic updates (via packagekit)
  3. CentOS / RHEL : How to set chroot jail for vsftp only for specific users
  4. What are different Samba Server Types
  5. CentOS / RHEL : Begginners guide to cron
  6. CentOS / RHEL : How to migrate storage (LVM) with pvmove Command
  7. How to send Audit Logs to Remote Rsyslog Server in CentOS/RHEL 6,7
  8. RedHat / CentOS : How to change currently active slave interface of bonding online
  9. CentOS / RHEL : How to assemble a software RAID in Rescue mode
  10. Replacing a Failed Mirror Disk in a Software RAID Array (mdadm)

You May Also Like

Primary Sidebar

Recent Posts

  • How to set the order to load certain modules in CentOS/RHEL 7 and 8
  • How to configure initrd / initramfs to including kernel modules in CentOS/RHEL
  • How to configure systemd.path to trigger an event when any changes made to a directory
  • Script to monitor RMAN Backup and Restore Operations
  • Oracle RMAN Backup Shell Script Example
  • Archives
  • Contact Us
  • Copyright

© 2019 · The Geek Diary