• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

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 change the UUID of the filesystem
  2. awk Command Examples in Linux
  3. pngcrush for image optimization
  4. ifenslave Command Examples in Linux
  5. The Ultimate Beginner’s Guide to Static Website Hosting With Google Firebase (for FREE)
  6. “Leap status Not synchronised” – On running ‘chronyc tracking’
  7. “mount.nfs: access denied by server while mounting” – how to resolve
  8. Patch Management of Linux Servers Using Spacewalk
  9. restorecon: command not found
  10. How to Change the VNC Server Resolution in Linux

You May Also Like

Primary Sidebar

Recent Posts

  • qm Command Examples in Linux
  • qm wait Command Examples in Linux
  • qm start Command Examples in Linux
  • qm snapshot Command Examples in Linux

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright