I’ve a Rhel 6 client installed in my Bigfix server. I MANUALLY installed a package “nfs-utils-lib-1.1.5-6.el6.x86_64” then I used a task “uninstall RPM Packages” to uninstall “nfs-utils-lib-1.1.5-6.el6.x86_64” the action status shows completed .
Then I switch to client’s machine (rhel 6) to check if the package “nfs-utils-lib-1.1.5-6.el6.x86_64” is still exists or not. I found that it is still exits on machine.
Then I tried to uninstall manually and get the exception “libnfsidmap.so.0()(64bit) is needed by (installed) nfs-utils-1:1.2.3-36.el6.x86_64” which shows that this package has dependency issues and BigFix cannot uninstall it. I Agree.
But my question is how can i see this exception in my console that why the package failed to uninstall and which dependency is restricting it from uninstalling?
Is there any analysis that need to be activated or anything else which can show up the dependency issues on console?
Though switching to clients machine and manually check is not the solution.
The Client’s log doesn’t show any information regarding those dependencies which prevent an RPM Package to uninstall.
Neither there is any analysis in Bigfix console (as far as i know).
I’m not referring to the client logs. I am referring to the Red Hat system logs and installer logs. If the info is in there, then you can pull that data with an analysis.
If Red Hat does not already log that info automatically, then it should be possible to tell the command that is installing or uninstalling the RPM to log and potentially even tell it where to log.
When I install software using an MSI on Windows, I have to tell MSIEXEC that I want it to log in that command, unless I tell MSIEXEC to always log by doing this: https://support.microsoft.com/en-us/kb/223300
The same is probably true for Red Hat packages. Either it always logs, or you have to tell it to always log, or you can optionally tell it to log with the specific package you are installing at the time. I really don’t know how Red Hat works, but this should be the case.
I’m not familiar with the details of the “uninstalls RPM packages” task you reference; what site is it in?
Whether there is logging available to pull depends on the action script in that task and/or system settings, so you should look at the action script to see if it is redirecting the output to a log file, or check /var/logs to see if RPM logging is capturing what you need. There is no existing analysis that provides this data that I’m aware of, so you will have to create a custom analysis or upload task to pull up the log to the server.
I would also recommend you use our Native Tools sites, which do have corresponding analyses to provide info from the YUM logs, and deal with dependency resolution better.
@steve “uninstall RPM packages” is located in Linux RPM patching site. and the action script of this task shows that it uses “rpm -e” command to uninstall a package. If it uses “YUM remove command” then yum logs can record that event. But also YUM remove command uninstall all those dependencies as well.
