updatemanager and patch failure
Recently I installed a number of patches that required a restart. During the shutdown processing I noticed that a few patches returned a failed status. After the system came back up, I restarted updatemanager and looked to see if there was any info on the failures but I did not see any sign which patches were not installed. Shouldn't updatemanger present this info to me?
# 4
I just grep'ed -i through all the patch log for fail or error and the only thing I see is:
patch/119107-01/log:compress(1) returned error code 2
patch/119562-01/log:compress(1) returned error code 2
patch/120099-01/log:compress(1) returned error code 2
patch/119414-02/log:compress(1) returned error code 2
patch/119414-02/log:compress(1) returned error code 2
patch/119315-02/log:compress(1) returned error code 2
patch/118822-08/log:compress(1) returned error code 2
patch/120135-01/log:compress(1) returned error code 2
patch/119107-03/log:compress(1) returned error code 2
patch/119107-03/log:compress(1) returned error code 2
patch/119107-03/log:compress(1) returned error code 2
patch/120339-01/log:compress(1) returned error code 2
patch/118822-11/log:compress(1) returned error code 2
patch/120099-02/log:compress(1) returned error code 2
patch/119315-03/log:compress(1) returned error code 2
patch/119107-06/log:compress(1) returned error code 2
patch/120467-02/log:compress(1) returned error code 2
patch/120776-03/log:compress(1) returned error code 2
patch/118822-18/log:compress(1) returned error code 2
patch/118822-19/log:compress(1) returned error code 2
but these patches appear to have been successfully installed on my system. I do not see any indication of any patch showing a failed status. I do notice however that there are these files in /var/sadm/spool:
119828-03.jar
120824-02.jar
120844-01.jar
Shouldn't these have been installed during the shutdown processing?
# 5
When a patch that requires a restart fails to install, it is also minimally logged in /var/sadm/spool/disallowed_patch_report. The Update Manager does not currently use this file to determine what succeeded or failed during the restart. Failed patches will continue to show in the Available tab since smpatch analysis will continue to report it as a recommended update.
Two bugs exist to improve error reporting. The first RFE 6331309 is for patchpro to log all output and errors to the disallowed_patch_list_report file. The second RFE 6332728 is to add a UI to the Update Manager to report the status of the patches which were previously pending for install.
The compress error, as documented in the man page for compress, indicates that one or more files were not compressed because they would have increased in size. It is not problem.
# 6
A couple comments. In regards to the compress error, it would be nice if this log output:
compress(1) returned error code 2
The SUNWbreg backout package will not be compressed.
Continuing to process backout package.
were reworded to be less alarming. If a return code of 2 from compress is not an error then why log it? Why not just log that the backout package could not be compressed because no space will be saved?
Second, I look at /var/sadm/patch/disallowed_patch_list and see:
119689-06
119578-09
119012-03
120844-01
118712-06
When I look at disallowed_patch_list_report I see:
STATUS INSTALL BEGIN 118822-19
Transition old-style patching.
STATUS INSTALL END 118822-19 INSTALL.0
STATUS INSTALL BEGIN 120807-01
Transition old-style patching.
STATUS INSTALL END 120807-01 INSTALL.0
STATUS INSTALL BEGIN 118927-02
Transition old-style patching.
STATUS INSTALL END 118927-02 INSTALL.0
STATUS INSTALL BEGIN 120844-01
Transition old-style patching.
STATUS INSTALL END 120844-01 INSTALL.8
STATUS INSTALL BEGIN 120251-02
Transition old-style patching.
STATUS INSTALL END 120251-02 INSTALL.0
STATUS INSTALL BEGIN 119828-04
Transition old-style patching.
STATUS INSTALL END 119828-04 INSTALL.0
STATUS INSTALL BEGIN 120064-01
Transition old-style patching.
STATUS INSTALL END 120064-01 INSTALL.0
STATUS INSTALL BEGIN 120900-01
Transition old-style patching.
STATUS INSTALL END 120900-01 INSTALL.0
and so on.
I don't see anything that tells me why the patches in disallowed_patch_list are in that list.