Differences

This shows you the differences between two versions of the page.

--- linux:redhat:troubleshooting [2019/10/07 13:44] – lunetikk
+++ linux:redhat:troubleshooting [2019/10/07 13:49] (current) – lunetikk
@@ Line 17: / Line 17: @@
 >Verify your yum cache is up to date with the repo
-        # yum clean all
+><code># yum clean all</code>
-        List out all the packages and check to see if everything is available that you need available
+>List out all the packages and check to see if everything is available that you need available
-        # yum list all --showduplicates
+><code># yum list all --showduplicates
-        # yum list <package> --showduplicates
+# yum list <package> --showduplicates</code>
-    Verify there are no excludes or version locks applied to your system
+>Verify there are no excludes or version locks applied to your system
-        # grep exclude /etc/yum.conf
+><code>
-        # yum versionlock list
+# grep exclude /etc/yum.conf
-        # subscription-manager release
+# yum versionlock list
+# subscription-manager release</code>
-    Check for pre-existing problems in the rpm database
+>Check for pre-existing problems in the rpm database
-        # yum check
+><code>
-        # package-cleanup --dupes
+# yum check
-        # package-cleanup --problems
+# package-cleanup --dupes
+# package-cleanup --problems</code>
-    Rebuild the database with
+>Rebuild the database with
-    rpm --rebuilddb
+><code># rpm --rebuilddb</code>
-Removing the Conflicting Packages
-    If only after you have run the yum clean commands and rebuilt the database and you are still receiving the issue, then the only other option is to remove the package forcefully. But please note: If the package has many core dependencies and its removed, then this could break the server and it would be very difficult to recover from. Therefore this option is not recommended, in this case seek Red Hat support
-    For non production servers, use this option at your own risk.
+>Removing the Conflicting Packages\\ If only after you have run the yum clean commands and rebuilt the database and you are still receiving the issue, then the only other option is to remove the package forcefully. But please note: If the package has many core dependencies and its removed, then this could break the server and it would be very difficult to recover from. Therefore this option is not recommended, in this case seek Red Hat support. For non production servers, use this option at your own risk.
 -Red Hat [[https://access.redhat.com/solutions/2801851|KB 2801851]]

Lunetikk's IT Wiki

User Tools

Site Tools

Differences

Page Tools