Patch 122035-01 and 122857-02
Sendmailpatch cannot be installed because patch 122035-01 fails.
/var/adm/messages:
root: [ID 702911 user.crit] => com.sun.patchpro.util.PatchBundleInstaller@6b62d1 <=Policy does not allow installation of patches. 122035-01
Apr 24 10:00:31 root: [ID 702911 user.error] => Thread[Thread-21,5,main] <=Problem installing patches: CRITICAL: Das Patch 122035-01 macht den Kernel instabil, ist veraltet oder gem溥 der Richtlinie unzul鋝sig.
is the patch not correct?
[501 byte] By [
hseidl] at [2007-11-26 6:42:43]
# 1
Hello hseidl,
Unfortunately support for this product is supplied in English only.
Patch 122035-01 is a dependancy patch of 122857-02, there is not enough information from your post to determine why the installation of this patch is failing.
Please can you provide a larger extract (50 lines above and below) of the log from around this period and translate the Greman to English.
Regards,
# 3
Apr 24 08:42:56 SRxVSP103 genunix: [ID 408114 kern.info] /pci@0,0/pci17c0,4006@1
d/mouse@2 (hid1) online
Apr 24 09:45:07 SRxVSP103 root: [ID 702911 user.crit] => com.sun.patchpro.util.
PatchBundleInstaller@1f195fc <=Policy does not allow installation of patches. 12
2035-01
Apr 24 09:45:07 SRxVSP103 root: [ID 702911 user.error] => Thread[Thread-21,5,ma
in] <=Problem installing patches: CRITICAL: Das Patch 122035-01 makes the kernel unstable, is obsolete or is forbidden by policy.
Apr 24 09:45:38 SRxVSP103 root: [ID 702911 user.error] => Thread[Thread-21,5,ma
in] <=Problem installing patches: NOTICE: Patch 118376-09 cannot be installed un
til the next system shutdown.
Apr 24 09:45:44 SRxVSP103 root: [ID 702911 user.error] => Thread[Thread-21,5,ma
in] <=Problem installing patches: NOTICE: Patch 120993-02 cannot be installed un
til the next system shutdown.
Apr 24 09:54:36 SRxVSP103 root: [ID 702911 user.crit] => com.sun.patchpro.util.
PatchBundleInstaller@6b62d1 <=Policy does not allow installation of patches. 122035-01
All other Updates from this morning are ok.
I have the same mistake on 2 systems (Server and Laptop).
# 4
i find some issue in SunSolve:
Asset Id:1-26-101688-1
Title:Multiple Patching and Packaging Issues for Solaris 10
Synopsis:Multiple Patching and Packaging Issues for Solaris 10
Update Date:Fri Apr 07 00:00:00 MDT 2006
Solaris 10 x86 Platform Solaris 10 Note: Solaris 7, 8 and 9 are not affected by this issue. Always install the the latest patch and packaging utility patches before performing installation or removal of other patches or packages. At the time of publication of this document, the following patches address this issue. However, subsequent patches may be developed to address this issue. SPARC Platform Solaris 10 Patch 119254 (Install and Patch Utilities)Patch 119317 (SVr4 Packaging Commands (usr))Patch 119683 (lib/svc/bin/svc.configd)Patch 121297 (fgrep)Patch 122034 (nawk patch) x86 Platform Solaris 10 Patch 119255 (Install and Patch Utilities)Patch 119318 (SVr4 Packaging Commands (usr))Patch 119684 (lib/svc/bin/svc.configd)Patch 121296 (fgrep)Patch 122035 (nawk patch) NOTE: The issue is not fully resolved and additional patches will be addressing the issue. Please install the most current versions of any patch and packaging patches before performing installation or removal of other patches or packages. Customers must always be current with their patch and packaging patches for all releases but this is a special issue for Sol 10 at this time. There are a number of bugs fixed, others are in the works, and others are yet to be worked on. What we have so far: 1. 119254-02 SunOS 5.10: Install and Patch Utilities Patch 119255-02 SunOS 5.10_x86: Install and Patch Utilities Patch /usr/lib/patch/patchadd /usr/lib/patch/patchrm Problem Description: BugID 6233738: patchadd of certain patches in x86 s10 GA fails BugID 5045607: patchadd failed to create backout file without any error BugID 6224767:
Kernel 118855-02
wbr
hans
# 5
Bug id # 6408378 is currently under investigation for this issue with patch 122035-01.
Note that this bug is currently not publicly viewable.From reading the bug details it's likely that it will require a new revision of the patch to resolve the issue but it is still under investigation.
