Smpatch failing?

hello, i try to install patch 112960-61 , it's on sunsolve page, but when i try to use smpatch for this, it says there is no such patch.
smpatch works for some patches, and for other it doesn't. i have ppro 2.2 installed
bash-2.05# smpatch download -i 112960-61
The following patches were not downloaded:
112960-61 Patch does not exist.
i've set up sunsolve user and password through pprosetup
any idea what might be the reason? when i use option -u root i see this
bash-2.05# smpatch download -u root -i 112960-61
Authenticating as user: root
Type /? for help, pressing <enter> accepts the default denoted by [ ]
Please enter a string value for: password ::
Loading Tool: com.sun.admin.patchmgr.cli.PatchMgrCli from serv1
Login to serv1 as user root was successful.
Download of com.sun.admin.patchmgr.cli.PatchMgrCli from serv1 was successful.
Requested patches:
112960-61
Downloading the requested patches
Could not download patch. com.sun.patchpro.util.CannotConnectException: Cannot connect to retrieve detectors: Default SSL context init failed: Keystore was tampered with, or password was incorrect.
bash-2.05#
i know that i need SUNWcert package probably to create/export keys, but i don't have this package, and i was not able to find it on Solaris CD or sapplement software cd or some software companion cd.
link give on sun page to SUNWcert is failing to show up ( https://sunsolve.sun.com/SUNWcert )
i have no idea what to do
Edited by: juice99 on Jan 30, 2009 4:11 AM

We assure our detectors and current files are kept up to date daily. (we're not updateconnection newbies ;-))
We are not in the practice of doing the leg work for Sun support (especially since we pay for support), please ask them to do their own analysis of the patches they are supplying and QA work.
Veritas provides very nice packages for both the SF packages and their patches, Sun should be directing customers to use those rather than going off and doing their own thing when it comes to Veritas products. Our sysadmins (all 20 of them) agree we should not allow Sun to patch our Veritas products, especially considering the ongoing QA issues with Sun's patch products.
Thanks for responding.

Similar Messages

119116-20 - ERROR: Failed to validate the digital signature(s).

Hi I am getting such errors when I use smpatch:
bash-3.00# smpatch download -i 119116-20
com.sun.patchpro.util.Percentage@1c4ff2c
119116-20 cannot be validated.
Unexpected Failure: java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
Can you please help me fix this?
Thanks,
Mayuresh

I'm getting the same problem ; smpatch fails to validate signed patches.
I followed the instructions at:
http://forum.sun.com/jive/thread.jspa?threadID=108470&messageID=369154
However, 112945-43 is obsoleted by 112945-44, which I installed instead. I also installed this certificate, as the instructions indicate:
http://www.sun.com/pki/certs/ca/Object_Signing_CA-cert.der
Using pkgadm addcert -t -f der ./Object_Signing_CA-cert.der. I can see that it is installed:
# pkgadm listcert
 Keystore Alias: Object Signing CA
 Common Name: Object Signing CA
Certificate Type: Trusted Certificate
Issuer Common Name: Sun Microsystems Inc Root CA
 Validity Dates: <Jun 2 00:00:00 2005 GMT> - <Jun 1 23:59:59 2015 GMT>
 MD5 Fingerprint: A9:C8:BE:5E:79:67:42:A2:31:77:17:B9:0A:80:F8:F1
SHA1 Fingerprint: C7:CA:40:96:E7:DC:D8:59:01:07:76:B1:7A:FF:C0:B4:C3:27:A5:40However, 'smpatch update' still produces:
Error: PatchPro failed: ERROR: Failed to validate the digital signature(s).
/var/sadm/spool/113434-33.jar cannot be validated.I'm guessing that the Object Signing CA on http://www.sun.com/pki/certs/ca/ is not the correct certificate that I need to verify the signed patches. Can anyone point me in the right direction?
Thanks.

Smpatch analyze fails to run on Solaris 10 Sparc systems

I have two Sparc Solaris 10 systems that I am unable to get to successfully patch. The 'sconadm' tool runs correctly, but smpatch bombs out with one of the following two errors:
Failure: Cannot connect to retrieve current2.zip: You are not authorized to access this service.
Failure: Cannot connect to retrieve detectors.jar: You are not authorized to access this service.'dmesg' suggests that it is failing to send the correct credentials to the update server:
Aug 18 12:23:01 pheasant root: [ID 702911 user.crit] => com.sun.patchpro.cli.PatchServices@1bcdbf6 <=Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://getupdates1.sun.com/database/current2.zipIf I attempt to download this file in a web browser, my Sun Online credentials allow me to do so, so they are valid.
I've found threads of people with similar issues, but none of the presented solutions have worked for me. I've tried updating all the related patches, but to no avail.
I've downloaded the 'suc.sh' tool and supplied the output from one of my servers:
# ./suc.sh
User: root
Logname: root
Tue Aug 18 12:30:20 BST 2009
pheasant
smpatch settings:
patchpro.backout.directory - ""
patchpro.baseline.directory - /var/sadm/spool
patchpro.download.directory - /var/sadm/spool
patchpro.install.types - rebootafter:reconfigafter:standard
patchpro.patch.source - https://getupdates1.sun.com/
patchpro.patchset - current2
patchpro.proxy.host - ""
patchpro.proxy.passwd **** ****
patchpro.proxy.port - 8080
patchpro.proxy.user - ""
smpatch analyze:
Failure: Cannot connect to retrieve current2.zip: You are not authorized to access this service.
Entitlement:
cat: cannot open /var/sadm/spool/cache/entitlement/*entitlement_client
Sun UC patch revision:
120335-04
121081-06
121081-08
121118-16
121453-02
122231-01
123003-03
123005-07
123630-03
123893-05
123893-15
124171-07
137137-09
Solaris release:
 Solaris 10 5/09 s10s_u7wos_08 SPARC
 Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
 Use is subject to license terms.
 Assembled 30 March 2009
Solaris Kernel: Generic_141414-07
Machine Type: sun4v
Platform: SUNW,SPARC-Enterprise-T5120
Java versions:
System default:
java version "1.5.0_19"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_19-b02)
Java HotSpot(TM) Server VM (build 1.5.0_19-b02, mixed mode)
Java 5:
java version "1.5.0_19"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_19-b02)
Java HotSpot(TM) Server VM (build 1.5.0_19-b02, mixed mode)
Java 6:
Unable to locate JRE meeting specification "1.6*"
Java used by smpatch and updatemanager:
/usr/sbin/pprosvc:JAVACMD="/usr/jdk/latest/bin/java -version:1.5+"
/bin/updatemanager:JAVA_EXEC="/usr/jdk/latest/bin/java -version:1.5+"
Cacao Java version:
java-home=/usr/jdk/jdk1.5.0_19
Cacao Base Directories:
cacao.install.rt.base.dir=/
cacao.install.etc.base.dir=/
Software Cluster:
CLUSTER=SUNWCXall
All ccr properties:
18:
Property not defined: 18
cns.assetid:
EpZ/R8Qb0Pm6RveZcxEkQs65/+Q=
cns.br.SunUCenabled:
true
cns.ccr.keyGenPath:
/usr/lib/cc-ccr/bin/ccrKeyGen
cns.clientid:
ba7a3b27-d847-4abc-9453-ba80d2f6c2b0
cns.httpproxy.auth:
cns.httpproxy.ipaddr:
cns.httpproxy.port:
cns.regtoken:
3912c9d8-22e8-41d9-8e09-e7b50f186b44:1280448000000:T
cns.security.password:
tKb+Hl+DUx8YZdtTk4Dw+keG66XcqAr7FgkCJ2LT96im
cns.security.privatekey:
-----BEGIN ENCRYPTED PRIVATE KEY-----
MIICxjBABgkqhkiG9w0BBQ0wMzAbBgkqhkiG9w0BBQwwDgQIp3u860rdprUCAggA
MBQGCCqGSIb3DQMHBAh/OGl0hwjEkASCAoAm9jJrEjhB0wKNCKR3LlrREJAcmRFP
2wkS0e7CNt+W8dMRJf5I7D/eRIxaa3INaGdSiuMCHJit44tcnQaB9L31EH3xAkLB
9afGErebRM9ldlt4ScZJ6LNlgeRYu+QO4dNGjsor5XVeGaAqhGaODqFdh1tLP6eI
r2UAkRJ6ATThIPhbtvNqBZ3Dq/UyJLS3sGSh6zBo/WA/poYHzOq0tuvrYZ4wd9PH
G5LW4wGac2vEL8/FlI8dSYDYY5ENsPxTC/AzYBdldcK0gmpLZpfQO7NnHo8Hipk3
/gVRLUIKbN2nX0pT5rA4AGxj/gNiBqGY9YnEp1np1W/ZaPuqwjXFNgWUBDwI6PmR
0mae0qbNIP9UHew+r9PfNd2YQrKwjZM7lUU4y04Y1mUjziy+jThAWBKP3VAsc0a2
Ztr4EN5dofGHO54Q8gyUyh3raV0HSSyjdGwOvmo/visRmhQ/SYT6gr+aGPd3RhjA
WJN2OwRWgO6GyZWqZP47CuS6sn1R9NSVgyNIyBf7rdXHNre6Y9FhYJFYYa0DzofB
iMb/z0fQpmUtRul/8AhlSSmwS1ZCzmpH5vADPMMvjOZrjsUV7n2Fi8pZ8pzXT06W
oHccis3qDSsp/PsIaK+bCKqcFimYWHblxgCle2gtI0+p47gE9zthLeNgGiYrV3bH
8MdrMgafggL9Tmu8lPBOTpkM2DMBdRkGf63g1WVlkw3Huq5mOAzCzywvxsOhqpf2
tX7aIzBSe1z9iWkyzBUWKCObrtZmGUkD6iHQIbhCPAObv8g+0odV3kiDHxnuMp8o
tjiVQMBiThzCBfypGiv5ub96SO2in693YybafQdOl2ZdGkHYq1975jIn
-----END ENCRYPTED PRIVATE KEY-----
cns.security.publickey:
-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDKy2n+88gjTxo/4za2Q92l4XBQ
ZqCpJq0WFpdRvaEiRFXQJHtv66+XfKTUufq8CuFR8OLTSrA/PpTqSNTEBvmBJf7n
NG6lXBM2fvgakxTwjtaZkvZl3Yhf8gBJp8pptuyMihStlt+u+0CBdwMmrz91wGDQ
3MNdlDRdukKn66llLwIDAQAB
-----END PUBLIC KEY-----
cns.swup.UMautolaunch:
false
cns.swup.autoAnalysis.enabled:
true
cns.swup.checkinInterval:
2
cns.swup.lastCheckin:
0
cns.swup.patchbaseline:
current
cns.swup.regRequired:
true
cns.transport.serverurl:
https://cns-transport.sun.com
patchsvr not installed.
Sun UC package status:
SUNWbreg not installed
SUNWdc not installed
Services in maintenance/disabled state:

Hi, I'm also experiencing this issue. Is there an rss or bug list I can follow to check for eta/resolution?

Smpatch PatchPro failed: ERROR: Failed to validate the digital signature

Hello,
I 'm trying to update solaris 9 (5.9 Generic_118558-03 sun4u sparc) using smpatch.
I get the following error from all - to be installed - patches!!
Downloading the required patches for machine "xxx". Please wait...
Error: PatchPro failed: ERROR: Failed to validate the digital signature(s).
/var/sadm/spool/112941-10.jar.tmp cannot be validated.
I have read that you need to install patchid 112945-44 so i have installed it with no solution.
I have cleared the /var/tmp/patches/ directory:
# rm /var/tmp/patches/*.jar.tmp
# rm /var/sadm/spool/*.jar
I would be grateful if you reply me with any help.
Thanks,

I thought this solution:
To download signed patch 112945-45 and:
# mv 112945-45.jar /var/sadm/spool/
# smpatch add -i 112945-45
On machine ""xxx"...
Installing patch 112945-45 ...
Error: PatchPro failed: Received a Manipulable event.
Error: PatchPro failed: Received a Manipulable event.
Error: PatchPro failed: ALERT: Failed to install a patch. 112945-45
/var/sadm/spool/patchpro_dnld_2007.06.14@12:22:38:EEST.txt has been moved to /var/sadm/spool/patchproSequester/patchpro_dnld_2007.06.14@12:22:38:EEST.txt
Problem Summary:
Inside /var/log/messages :
Jun 14 12:44:05 polymnia root: [ID 702911 user.error] Thu Jun 14 12:44:05 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Problem installing patches: Received a Manipulable event.
Jun 14 12:44:05 polymnia root: [ID 702911 user.alert] Thu Jun 14 12:44:05 EEST 2007(ALERT) => com.sun.patchpro.manipulators.SunOSSunPatchInstaller@73a5d3 <=112945-45 validation failed.
Jun 14 12:44:05 polymnia root: [ID 702911 user.crit] Thu Jun 14 12:44:05 EEST 2007(CRITICAL) => com.sun.patchpro.manipulators.SunOSSunPatchInstaller@73a5d3 <=com.sun.patchpro.security.SignatureValidationException: ERROR: Failed to validate the digital signature(s) for:
Jun 14 12:44:05 polymnia at com.sun.patchpro.manipulators.Installer.extractPatch(Installer.java:314)
Jun 14 12:44:05 polymnia at com.sun.patchpro.manipulators.SunOSSunPatchInstaller.install(SunOSSunPatchInstaller.java:46)
Jun 14 12:44:05 polymnia at com.sun.patchpro.manipulators.Installer.run(Installer.java:134)
Jun 14 12:44:05 polymnia at java.lang.Thread.run(Thread.java:536)
Jun 14 12:44:06 polymnia root: [ID 702911 user.error] Thu Jun 14 12:44:05 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Problem installing patches: Received a Manipulable event.
Jun 14 12:44:06 polymnia root: [ID 702911 user.alert] Thu Jun 14 12:44:06 EEST 2007(ALERT) => com.sun.patchpro.util.PatchBundleInstaller@9360e7 <=Failed to install a patch. 112945-45
Jun 14 12:44:06 polymnia patchadd utility failed. Reason code :0
Jun 14 12:44:06 polymnia root: [ID 702911 user.error] Thu Jun 14 12:44:06 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Problem installing patches: ALERT: Failed to install a patch. 112945-45
Also i have just seen that messages complains for the digital cert when i am tryring to download the patch using smpach
Jun 14 12:49:20 polymnia root: [ID 702911 user.error] Thu Jun 14 12:49:20 EEST 2007(ERROR) => com.sun.patchpro.server.ServerPatchServiceProvider@92425a <=com.sun.patchpro.security.NotSignedByKnownCertificateException: 112945-45/prepatch CN=Enterprise Services Patch Management, O=Sun Microsystems Inc
Jun 14 12:49:20 polymnia at com.sun.patchpro.security.SignatureValidationUtil.validateJarFile(SignatureValidationUtil.java:232)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.validatePatchBundle(ServerPatchServiceProvider.java:1837)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.requestDownload(ServerPatchServiceProvider.java:1437)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.performDownloadPatches(ServerPatchServiceProvider.java:739)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.downloadPatches(ServerPatchServiceProvider.java:585)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.PatchServerProxy.downloadPatches(PatchServerProxy.java:130)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.GroupPatchDownloader.downloadPatches(GroupPatchDownload
Jun 14 12:49:20 polymnia root: [ID 702911 user.error] Thu Jun 14 12:49:20 EEST 2007(ERROR) => com.sun.patchpro.server.ServerPatchServiceProvider@92425a <=Failed to validate the digital signature(s). for: /var/sadm/spool/112945-45.jar.tmp: 112945-45/prepatch CN=Enterprise Services Patch Management, O=Sun Microsystems Inc
Jun 14 12:49:20 polymnia root: [ID 702911 user.error] Thu Jun 14 12:49:20 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Error: downloading patches.ERROR: Failed to validate the digital signature(s).
The following patches were not downloaded. Contact your Sun Microsystems support provider for more information.
112945-45
Message was edited by:
sapila

Smpatch update ALERT: Failed to install patch

I do not even know where to start. Since installing Solaris 10 0606 it
seems every time I try to patch the system I get failures of one type
or another. One problem today has to do with zones:
"To install the new instance of this package in all zones you must
first remove the existing instance of this package from the global
zone first (via pkgrm) and then install the new instance of this
package in all zones."
If sun already knows a pkgrm must be run why can't the smpatch command
just do it?
Another problem seems to be
For patch 121018-03, required patch 120759-04 does not exist
If sun knows a patch is required which is not on the system just Getit
and install it.
Also, what is up with having to reboot the box to install patches?
Why? Has this always been a required step? Do these reboots pertain only to kernel patches .etc?
I have seen other postings in this forum expressing unhappiness with
the patch system, some mentioning testing lab/group or certification
issues. I think smpatch should have an option to send smpatch results
back to sun for review. That way the Certification Group could have
real life situations to investigate. Or do they know the problems
already and just dont want to fix them? Just once I would love it if
smpatch came back with no failures and I was assured the system was
patched, up to date and secure.
Regards
# smpatch update
Update 120759-07 will not be downloaded since it already exists in the
download directory.
Update 121018-03 will not be downloaded since it already exists in the
download directory.
Update 121016-03 will not be downloaded since it already exists in the
download directory.
Update 121020-02 will not be downloaded since it already exists in the
download directory.
Update 121616-02 will not be downloaded since it already exists in the
download directory.
Update 120762-02 will not be downloaded since it already exists in the
download directory.
Installing patches from /var/sadm/spool...
Failed to install patch 120759-07.
patchadd utility failed. Reason code :0
Validating patches...Loading patches installed on the
system...Done!Loading patches requested to install.Done!Checking
patches that you specified for installation.Done!Approved patches will
be installed in this order:120759-07 Preparing checklist for
non-global zone check...Checking non-global zones...The following
requested patches rejected on non-global zone.Entire installation is
possible but those patcheswill not be installed on non-global
zone.myzone: Packages from patch 120759-07 are not installed on the
system.myzone2: Packages from patch 120759-07 are not installed on the
system.This patch passes the non-global zone check.None.Summary for
zones:Zone myzoneRejected patches:120759-07 Patches that passed the
dependency check:None.Zone myzone2Rejected patches:120759-07 Patches
that passed the dependency check:None.Patching global zoneAdding
patches...Checking installed patches...Verifying sufficient filesystem
capacity (dry run method)...Patch 120759-07 failed to install due to a
failure produced by pkgadd.See /var/sadm/patch/120759-07/log for
detailsPatchadd is terminating. WARNING: patchadd returned <5> for
global zone
ALERT: Failed to install patch 120759-07.
Failed to install patch 121018-03.
patchadd utility failed. Reason code :0
Validating patches...Loading patches installed on the
system...Done!Loading patches requested to install.Done!Checking
patches that you specified for installation.Done!The following
requested patches will not be installed becauseno patches required by
the patch are installed on this system. 0 For patch 121018-03,
required patch 120759-04 does not exist.No patches to install.
ALERT: Failed to install patch 121018-03.
Failed to install patch 121016-03.
patchadd utility failed. Reason code :0
Validating patches...Loading patches installed on the
system...Done!Loading patches requested to install.Done!Checking
patches that you specified for installation.Done!The following
requested patches will not be installed becauseno patches required by
the patch are installed on this system. 0 For patch 121016-03,
required patch 120759-06 does not exist.No patches to install.
ALERT: Failed to install patch 121016-03.
Failed to install patch 121020-02.
patchadd utility failed. Reason code :0
Validating patches...Loading patches installed on the
system...Done!Loading patches requested to install.Done!Checking
patches that you specified for installation.Done!The following
requested patches will not be installed becauseno patches required by
the patch are installed on this system. 0 For patch 121020-02,
required patch 120759-01 does not exist.No patches to install.
ALERT: Failed to install patch 121020-02.
Failed to install patch 121616-02.
patchadd utility failed. Reason code :0
Validating patches...Loading patches installed on the
system...Done!Loading patches requested to install.Done!Checking
patches that you specified for installation.Done!Approved patches will
be installed in this order:121616-02 Preparing checklist for
non-global zone check...Checking non-global zones...The following
requested patches rejected on non-global zone.Entire installation is
possible but those patcheswill not be installed on non-global
zone.myzone: Packages from patch 121616-02 are not installed on the
system.myzone2: Packages from patch 121616-02 are not installed on the
system.This patch passes the non-global zone check.None.Summary for
zones:Zone myzoneRejected patches:121616-02 Patches that passed the
dependency check:None.Zone myzone2Rejected patches:121616-02 Patches
that passed the dependency check:None.Patching global zoneAdding
patches...Checking installed patches...Verifying sufficient filesystem
capacity (dry run method)...Patch 121616-02 failed to install due to a
failure produced by pkgadd.See /var/sadm/patch/121616-02/log for
detailsPatchadd is terminating. WARNING: patchadd returned <5> for
global zone
ALERT: Failed to install patch 121616-02.
Failed to install patch 120762-02.
patchadd utility failed. Reason code :0
Validating patches...Loading patches installed on the
system...Done!Loading patches requested to install.Done!Checking
patches that you specified for installation.Done!Approved patches will
be installed in this order:120762-02 Preparing checklist for
non-global zone check...Checking non-global zones...The following
requested patches rejected on non-global zone.Entire installation is
possible but those patcheswill not be installed on non-global
zone.myzone: Packages from patch 120762-02 are not installed on the
system.myzone2: Packages from patch 120762-02 are not installed on the
system.This patch passes the non-global zone check.None.Summary for
zones:Zone myzoneRejected patches:120762-02 Patches that passed the
dependency check:None.Zone myzone2Rejected patches:120762-02 Patches
that passed the dependency check:None.Patching global zoneAdding
patches...Checking installed patches...Verifying sufficient filesystem
capacity (dry run method)...Patch 120762-02 failed to install due to a
failure produced by pkgadd.See /var/sadm/patch/120762-02/log for
detailsPatchadd is terminating. WARNING: patchadd returned <5> for
global zone
ALERT: Failed to install patch 120762-02.
/var/sadm/spool/patchpro_dnld_2006.08.22@11:16:20:EDT.txt has been
moved to
/var/sadm/spool/patchproSequester/patchpro_dnld_2006.08.22@11:16:20:EDT.txt
#

Enterprise users have strict policies on change management so dependent patches are not automatically installed when using "smpatch add". Neither are packages blithly uninstalled for zones if currently only existing in the global zone.
For your needs using "smpatch update" should analyse, download and install dependant patches in order for patches specified on the command line or for a global update. Note that that is with the exception of patches not matching the currently defined patch policy such as those needing a reboot. See the smpatch man page for information on policies.
Patches requiring reboots or being installed in single user mode are primarily for kernel and driver patches.
Your problems installing the Sun Studio 11 patches have been encountered previously in regards to globally installed packages (and are covered in this forum) and is due to a combination of bug ID's 6337009, 6214678 and 6374972 for the patching utilities of which the last is still open.
You will currently have to manually install the patches using patchadd with the "-G" flag whilst in the global zone to install them in the global zone only.

S10u 7 - smpatch in BE fails - patchadd: /dev/null: cannot create

Solaris 10 5/09 s10x_u7wos_08 X86 with ZFS Root + Zones
smpatch on non active BE with Zones fails:
# smpatch update -b s10x_u7wos_08p1
Ckecking the currently running boot enviornment ...
Currently running boot enviornment name is [s10x_u7wos_08p].
Checking the destination boot environment [s10x_u7wos_08p1] ...
Installing patches from /var/sadm/spool...
Copying the currently running BE into inactive BE [s10x_u7wos_08p1] ...
(This process will take some time, please wait a moment.)
Installing update(s) onto the inactive boot environment [s10x_u7wos_08p1] ...
Failed to install patch 119901-07.
Utility used to install the update failed with exit code 1.
System has findroot enabled GRUBNo entry for BE <s10x_u7wos_08p1> in GRUB menuValidating the contents of the media </var/sadm/spool/119901-07.jar.dir>.The media contains
1 software patches that can be added.All 1 patches will be added because you did not specify any specific patches to add.Mounting the BE <s10x_u7wos_08p1>.Adding patche
s to the BE <s10x_u7wos_08p1>.Validating patches...Loading patches installed on the system...Done!Loading patches requested to install.Done!Checking patches that you spe
cified for installation.Done!Approved patches will be installed in this order:119901-07 Preparing checklist for non-global zone check...Checking non-global zones...This
patch passes the non-global zone check.119901-07 Summary for zones:Zone master-templateRejected patches:None.Patches that passed the dependency check:119901-07 Zone mast
er-template-cloneRejected patches:None.Patches that passed the dependency check:119901-07 Patching global zoneAdding patches...Checking installed patches...Verifying suf
ficient filesystem capacity (dry run method)...Installing patch packages...Patch 119901-07 has been successfully installed.See /a/var/sadm/patch/119901-07/log for detail
sPatch packages installed: SUNWPython SUNWTiff SUNWTiff-devel SUNWgnome-img-viewer-shareDone!Patching non-global zones...Patching zone master-templateAdding patches.
..Checking installed patches...Patchadd is terminating.Done!Unmounting the BE <s10x_u7wos_08p1>.The patch add to the BE <s10x_u7wos_08p1> failed (with result code <8>).
/usr/lib/patch/patchadd[4]: /dev/null: cannot create/usr/lib/patch/patchadd[6]: /dev/null: cannot createsort: insufficient available file descriptorsPatch 119901-07 fail
ed in non-global zone SUNWlu-master-template.Patch 119901-07 wasn't installed in zones:master-template-clone
Failed to install patch 119901-07.
ALERT: Failed to install patch 119901-07.
Any ideas?
TIA.
/phs
Peter H. Seybold

Post your question in the Developer Forums:
http://discussions.apple.com/category.jspa?categoryID=164

Smpatch update ALERT: Failed to install patch 121616-02

I am getting various Failed to install patch alerts when doing smpatch update. Many patches are aparently applied successfuly, but others are not. I do not have Sun Support since it is my personal X86 box. Are other people getting these failures? If so, what is done to investigate / fix the problems? If I had support what would Sun recommend be done to correct the problem? Should smpatch always run clean with no errors? Regards.

I will post to the other forum as well, but I can't think of a more "general" Solaris discussion topic than how to / what to expect when applying patches. I am not sure I agree with your comment "it's best to only install the patches that are really needed". I thought smpatch update "decided" which patches are needed given the system it is run on.
Is your comment based upon best practices published somewhere? How do you as a sysAdmin decide which patches are really needed?
I would like to hear from the community how they patch their boxes and if smpatch is working for them, especially in a production environment. I have a stand alone system, but how are people in an environment with test systems patching? Are they using smpatch? In general, how are people keeping their systems updated, reliable, bug free and secure?
Regards,

Smpatch add -b fails for ZFS root

This is Solaris-10U6, x86, patched to current patchlevels as of this afternoon:
# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
be20081218 yes no no yes -
be20081229 yes yes yes no -
# smpatch analyze 2>&1 | tee /var/tmp/,patchlist
122912-14 SunOS 5.10_x86: Apache 1.3 Patch
# lucreate -n testbe
Checking GRUB menu...
System has findroot enabled GRUB
Analyzing system configuration.
Comparing source boot environment <be20081229> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <testbe>.
Source boot environment is <be20081229>.
Creating boot environment <testbe>.
Cloning file systems from boot environment <be20081229> to create boot environment <testbe>.
Creating snapshot for <rpool/ROOT/be20081229> on <rpool/ROOT/be20081229@testbe>.Creating clone for <rpool/ROOT/be20081229@testbe> on <rpool/ROOT/testbe>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/testbe>.
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <be20081218> as <mount-point>//boot/grub/menu.lst.prev.
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <testbe> as <mount-point>//boot/grub/menu.lst.prev.
File </boot/grub/menu.lst> propagation successful
Copied GRUB menu from PBE to ABE
No entry for BE <testbe> in GRUB menu
Population of boot environment <testbe> successful.
Creation of boot environment <testbe> successful.
# smpatch download -x idlist=/var/tmp/,patchlist
122912-14 has been validated.
# smpatch add -b testbe -x idlist=/var/tmp/,patchlist
Ckecking the currently running boot enviornment ...
Currently running boot enviornment name is [be20081229].
Checking the destination boot environment [testbe] ...
Copying the cuurently running BE into inactive BE [testbe] ...
This grogess will take you a long time, please wait a moment.)
ERROR: File systems on ABE <testbe> have insufficient space for repopulation from boot environment <be20081229>. It is recommended to delete this BE and create a fresh BE.
/usr/sbin/lumake: lumake into testbe failed
#

I think the problem is generated by the following line in /usr/sbin/lumake:
$LUBIN/lucomp_size -p $PBE_NAME -i ${ICF} -O $INODE_ICF -n $ABE_NAMEThis command calls /usr/lib/lu/lucomp_size and it is this which is returning a 1, and ultimately causes the "insufficient space" error.
To find out what is going wrong when lumake checks the size, please enable the printing of commands and arguments and run the command again:
# script /var/tmp/smpatch.out
# set -x
# smpatch add -b testbe -x idlist=/var/tmp/,patchlist
# set +x
# exitOnce this has completed, please look through the /var/tmp/smpatch.out and then run the corresponding lucomp_size command and check the output and exit code:
# /usr/lib/lu/lucomp_size <args>
# echo $?If you are absolutely certain that there is enough space and just want to make this work now, you could remove the following lines from lumake:
$LUBIN/lucomp_size -p $PBE_NAME -i ${ICF} -O $INODE_ICF -n $ABE_NAME
if [ "$?" -ne "0" ] ; then
 # Size is not sufficient
 ${LUPRINTF} -Eelp2 "`gettext 'File systems on ABE <%s> have insufficient \
space for repopulation from boot environment <%s>. It is recommended to \
delete this BE and create a fresh BE.'`" "${ABE_NAME}" "${PBE_NAME}"
 err_exit_script 1
fiI would recommend that you open a support call so that the issue can be progressed more quickly.

Smpatch download: Failed to validate the digital signature

Hello,
what's the trick to download the patches?
# smpatch download
127732-01 cannot be validated.
123328-01 cannot be validated.
128495-01 has been validated.
125917-02 has been validated.
122537-02 cannot be validated.
121944-03 has been validated.
118667-14 cannot be validated.
Failure: ERROR: Failed to validate the digital signature(s).
# uname -a
SunOS mantis 5.10 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T1000
# smpatch get
patchpro.backout.directory      ""              ""
patchpro.baseline.directory     -               /var/sadm/spool
patchpro.download.directory     /var/sadm/spool /var/sadm/spool
patchpro.install.types          -               rebootafter:reconfigafter:standard
patchpro.patch.source           -               https://getupdates1.sun.com/
patchpro.patchset               current         current
patchpro.proxy.host             172.x.x.xxx    ""
patchpro.proxy.passwd           ****            ****
patchpro.proxy.port             8080            8080
patchpro.proxy.user             ""              ""-- Nick

I can echo this behavior here....
Also, I can isolate it (right now) to two patches. Looks like other people had more affected. Tomorrow, maybe it affects more for me too, I don't know. Manually downloading the two patches signed jar files, it seems like something is corrupt in the jar file:
# jar tvf 123328-01.jar
    76 Mon Jun 05 14:11:28 CDT 2006 123328-01/.diPatch
   236 Mon Jun 05 14:11:30 CDT 2006 123328-01/patchinfo
   424 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWcsu/pkgmap
   538 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWcsu/pkginfo
4985 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/checkinstall
    93 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/copyright
5768 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/i.none
1555 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/patch_checkinstall
   824 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/patch_postinstall
6916 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/postinstall
7437 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/preinstall
18996 Mon Jun 05 15:59:36 CDT 2006 123328-01/SUNWcsu/reloc/usr/bin/expr
   464 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWxcu4/pkgmap
   533 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWxcu4/pkginfo
4985 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/checkinstall
    93 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/copyright
5768 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/i.none
1555 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/patch_checkinstall
   824 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/patch_postinstall
6703 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/postinstall
7437 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/preinstall
19060 Mon Jun 05 15:59:36 CDT 2006 123328-01/SUNWxcu4/reloc/usr/xpg4/bin/expr
   464 Mon Jun 05 16:04:26 CDT 2006 123328-01/SUNWxcu6/pkgmap
   533 Mon Jun 05 16:04:26 CDT 2006 123328-01/SUNWxcu6/pkginfo
4985 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/checkinstall
    93 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/copyright
5768 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/i.none
1555 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/patch_checkinstall
   824 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/patch_postinstall
6703 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/postinstall
7437 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/preinstall
18996 Mon Jun 05 15:59:36 CDT 2006 123328-01/SUNWxcu6/reloc/usr/xpg6/bin/expr
2380 Tue Jun 20 06:52:26 CDT 2006 123328-01/README.123328-01
13272 Mon Sep 26 22:46:30 CDT 2005 123328-01/LEGAL_LICENSE.TXT
5197 Tue Jun 20 07:00:18 CDT 2006 META-INF/manifest.mf
java.util.zip.ZipException: invalid entry size (expected 5305 but got 8321 bytes)
        at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:371)
        at java.util.zip.ZipInputStream.read(ZipInputStream.java:148)
        at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92)
        at sun.tools.jar.Main.list(Main.java:863)
        at sun.tools.jar.Main.run(Main.java:212)
        at sun.tools.jar.Main.main(Main.java:1022)The two patches I currently have affected are 123328-01.jar and 122537-02.jar

How to remove a patch via smpatch in fail safe mode

After installing patch
139556-08 SunOS 5.10_x86: Kernel Patch
my system can not restart. Even after uopdating my boot archive the "normal" boot process fails every time and the system keeps restarting.
I would like to remove the patch in fail safe mode, but I do not know how to do it, when my system is mounted under /a.
Any advice, or alternative of how to get my system back online, would be greatly appreciated.
Thanks for your help

I had the exact same problem with the same patch. I brought up the box in failsafe mode, mounted the zfs filesystem where my patches were located, cd'd to the patch directory, then re-applied the patch using:
patchadd -R /a 139556-08I didn't bother to do a patchrm first. After I re-ran the patch, I also did a force update of the boot archive,
bootadm update-archive -R /aFollowed by
shutdown -i 6 -y -g 0And everything was good. Seems there are a number of folks having trouble with this kernel patch.
=N=

Smpatch analyze fails

When I run "smpatch analyze" on my Solaris 10 x86 10/08 system, I get:
Failure: Response code was 500What does this mean and what can I do to fix it?
Thanks.

ForumModerator wrote:
Thanks for the file.
Following analysis we have determined:
1. Java version installed 1.6.01_11 has been known in exceptional circumstances to cause problems. Please revert to java version 1.5* using the following commands.
# cacaoadm stop
# cacaoadm set-param java-home=/usr/jdk/jdk1.5.0_16
# cacaoadm startDone. No change.
2. Basic Update Connection patches are in order. Is this a proxy patch server or an agent??I'm not sure I understand the question. This is a desktop system.
3.
Can you please check that the system has no connectivity issues, what is the output of the following commands:
# telnet sun.com 80
# telnet cns-services.sun.com 443
# telnet getupdates1.sun.com 443
# telnet a248.e.akamai.net 443
Please also supply the output of the following commands:
# svcs -xv
# ifconfig -a
please upload the results as previously done
Done. The file is "cores/command_output.txt." I have no other connectivity problems. I'm connecting to these forums using the box in question.
Thanks.

Failed to install patch 126411-01

I had patched my system using smpatch but failed.
#uname -a
SunOS SunOS 5.10 Generic_138889-08 i86pc i386 i86pc
#smpatch analyze
You have new messages. To retrieve: smpatch messages [-a]
125556-03 SunOS 5.10_x86: patch behavior patch
126411-01 StarOffice 8 (Solaris_x86): ARCH patch to enable install of >= Update 6
120186-17 StarOffice 8 (Solaris_x86): Update 12
# smpatch update
You have new messages. To retrieve: smpatch messages [-a]
125556-03 has been validated.

126411-01 has been validated.
120186-17 has been validated.
Installing patches from /var/sadm/spool...
125556-03 has been applied.

Failed to install patch 126411-01.
Utility used to install the update failed with exit code 8.
Validating patches...Loading patches installed on the system...Done!Loading patches requested to install.Done!The following requested patches have packages not installed on the systemPackage SUNWstaroffice-core01 from directory SUNWstaroffice-core01.i in patch 126411-01 is not installed on the system. Changes for package SUNWstaroffice-core01 will not be applied to the system.Package SUNWstaroffice-core01 from directory SUNWstaroffice-core01 in patch 126411-01 is not installed on the system. Changes for package SUNWstaroffice-core01 will not be applied to the system.Checking patches that you specified for installation.Done!The following requested patches will not be installed becausethe packages they patch are not installed on this system. 0 No Packages from patch 126411-01 are installed on the system.No patches to install.

Failed to install patch 126411-01.
ALERT: Failed to install patch 126411-01.
Failed to install patch 120186-17.

Utility used to install the update failed with exit code 2.
......

The StarOffice patches are most likely being recommended as there are one or more SUNWstaroffice packages installed on the system, but the patch installation cannot complete due to an incomplete installation of StarOffice. Check for any installed StarOffice packages and remove them if present:
# pkginfo | grep SUNWstaroffice

Smpatch no longer works after update from SUC proxy!

Hi,
I ran smpatch update against our local SUC proxy. It said some patches needed a reboot so I did "init 6" after it finished and the system shutdown, installing some patches, and then booted again...
Now the system as such seems to work fine but "smpatch analyze" fails with this weird error:
Exception java.lang.OutOfMemoryError: requested -4 bytes for size_t in /BUILD_AREA/jdk1.5.0_21/hotspot/src/os/solaris/vm/os_solaris.cpp. Out of swap space?
And just running "java" fails with the same error message.
However running "java -client" works!
Any ideas how to fix this?!?
I tried to install the latest recommended patch cluster but that did not help. )-:
Alternatively is there a way to make smpatch use "java -client" so that it works?
Thanks a lot in advance!
Best regards,
Anton

krubar wrote:
I have same problem on Sparc system (Solaris 10). Does anybody know how to fix it ? I can't change symbolic link for javaAre you certain that you are experiencing exactly the same issue? Did you follow the hyperlinks to the Sun Solve documents above?
The Sun Solve document itself states:
1. Solaris 8 and 9 and OpenSolaris and Solaris 10 on the SPARC platform are not impacted by this issue.I would suggest that you open a Support Call with your local solutions centre.

Solaris 10 x86 Update Manager & smpatch errors

I've recently installed Solaris 10 on two x86 machines and, even after installing patch 121119-15, I'm having Update Manager and smpatch issues. It appears to be due to certificate troubles.
I've followed several sets of instructions (including cacaoadm stop/start and registration) and nothing has seemed to work.
I have successfully connected to:
# telnet sun.com 80
# telnet cns-services.sun.com 443
# telnet getupdates1.sun.com 443
# telnet a248.e.akamai.net 443
I have also tried:
# cacaoadm stop
# cacaoadm status
# /usr/lib/cc-ccr/bin/eraseCCRRepository
# rm /var/scn/persistence/SCN*
# cacaoadm start
Reregistering didn't change anything.
Thanks in advance for everyone's help!
~~~~~~~~
Output of smpatch analyze:
bash-3.00# smpatch analyze -C patchpro.debug=true
Effective proxy host : ""
Effective proxy port : ""
Effective proxy user : ""
Last Modified Date read: Wed Dec 31 19:00:00 EST 1969
... Submitting download request against a GUUS server
... ... Hostname of URL is getupdates1.sun.com
... ... Filename of URL is /xml/motd.xml
... ... File path portion of URL is /xml/motd.xml
Defining request header : IF_MODIFIED_SINCE... valueWed Dec 31 19:00:00 EST 1969
Key 1 : Server = Sun-Java-System-Web-Server/7.0
Key 2 : Date = Mon, 11 May 2009 20:43:31 GMT
Key 3 : Content-disposition = attachment; filename=xml/motd.xml
Key 4 : Content-type = text/xml
Key 5 : Content-length = 10513
Key 6 : Set-Cookie = 01SessionID=0xe2849044; path=/
Last Modified Date value written to /var/sadm/spool/cache/xml/https%3A%2F%2Fgetupdates1.sun.com%2F%2Fmotd.xml.lmd is 0
Date format for this value: Wed Dec 31 19:00:00 EST 1969
Last Modified Date file updated : /var/sadm/spool/cache/xml/https%3A%2F%2Fgetupdates1.sun.com%2F%2Fmotd.xml.lmd
Last Modified Date read: Wed Dec 31 19:00:00 EST 1969
... Submitting download request against a GUUS server
... ... Hostname of URL is getupdates1.sun.com
... ... Filename of URL is /xml/motd.xml
... ... File path portion of URL is /xml/motd.xml
Defining request header : IF_MODIFIED_SINCE... valueWed Dec 31 19:00:00 EST 1969
Key 1 : Server = Sun-Java-System-Web-Server/7.0
Key 2 : Date = Mon, 11 May 2009 20:43:31 GMT
Key 3 : Content-disposition = attachment; filename=xml/motd.xml
Key 4 : Content-type = text/xml
Key 5 : Content-length = 10513
Key 6 : Set-Cookie = 01SessionID=0xfb9fa105; path=/
Last Modified Date value written to /var/sadm/spool/cache/xml/https%3A%2F%2Fgetupdates1.sun.com%2F%2Fmotd.xml.lmd is 0
Date format for this value: Wed Dec 31 19:00:00 EST 1969
Last Modified Date file updated : /var/sadm/spool/cache/xml/https%3A%2F%2Fgetupdates1.sun.com%2F%2Fmotd.xml.lmd
Effective proxy host : ""
Effective proxy port : ""
Effective proxy user : ""
... Submitting download request against a GUUS server
... ... Hostname of URL is getupdates1.sun.com
... ... Filename of URL is /database/current2.zip
... ... File path portion of URL is /database/current2.zip
Effective proxy host : ""
Effective proxy port : ""
Effective proxy user : ""
... Submitting download request against a GUUS server
... ... Hostname of URL is getupdates1.sun.com
... ... Filename of URL is /detector/detectors.jar
... ... File path portion of URL is /detector/detectors.jar
Defining request header : IF_MODIFIED_SINCE... valueWed Dec 31 19:00:00 EST 1969
Defining request header : IF_MODIFIED_SINCE... valueWed Dec 31 19:00:00 EST 1969
Failure: Cannot connect to retrieve current2.zip: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
~~~~~~~~~~~~~~~~~~~~~~
Output of suc.sh:
bash-3.00# ./suc.sh
User: root
Logname: root
Mon May 11 16:44:15 EDT 2009
opc-sec-fimdev3
smpatch settings:
patchpro.backout.directory "" ""
patchpro.baseline.directory - /var/sadm/spool
patchpro.download.directory /var/sadm/spool /var/sadm/spool
patchpro.install.types - rebootafter:reconfigafter:standard
patchpro.patch.source - https://getupdates1.sun.com/
patchpro.patchset current2 current2
patchpro.proxy.host "" ""
patchpro.proxy.passwd **** ****
patchpro.proxy.port "" 8080
patchpro.proxy.user "" ""
smpatch analyze:
Failure: Cannot connect to retrieve current2.zip: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Entitlement:
Solaris10Security
SolarisSecurityUpdates
SolarisDataIntegrityUpdates
SolarisHardwareUpdates
SolarisUtilityUpdates
Public
Solaris10
SolarisAllUpdates
ContractRequired
Sun UC patch revision:
119789-09
120336-04
121082-06
121119-13
121119-15
121454-02
123004-03
123006-07
123631-03
123896-05
124187-07
Solaris release:
Solaris 10 10/08 s10x_u6wos_07b X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 27 October 2008
Solaris Kernel: Generic_137138-09
Machine Type: i86pc
Platform: i86pc
Java -version:
java version "1.5.0_16"
Java(TM) Platform, Standard Edition for Business (build 1.5.0_16-b02)
Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode, sharing)
Cacao Java version:
java-home=/usr/jdk/jdk1.5.0_16
Software Cluster:
CLUSTER=SUNWCall
All ccr properties:
20:
Property not defined: 20
cns.assetid:
8kh0OIj4ADe5LdHlrU88bic3Lps=
cns.br.SunUCenabled:
true
cns.ccr.keyGenPath:
/usr/lib/cc-ccr/bin/ccrKeyGen
cns.clientid:
a1b19f4d-37db-446f-9707-181b8e47f0d6
cns.httpproxy.auth:
cns.httpproxy.ipaddr:
cns.httpproxy.port:
cns.patchsvr.cachelocation:
/var/sadm/spool/patchsvr
cns.patchsvr.patchsource:
https://getupdates.sun.com
cns.regtoken:
1c230c7b-4d6c-43f8-9802-c2c89f96493d:1269820800000:T
cns.security.password:
IJ3RI+p/Cb9M2qyVpqnw7ycp6tXQkSGkhIT/D/0KiPtH
cns.security.privatekey:
-----BEGIN ENCRYPTED PRIVATE KEY-----
REMOVED
-----END ENCRYPTED PRIVATE KEY-----
cns.security.publickey:
-----BEGIN PUBLIC KEY-----
REMOVED
-----END PUBLIC KEY-----
cns.swup.UMautolaunch:
false
cns.swup.autoAnalysis.enabled:
true
cns.swup.checkinInterval:
2
cns.swup.lastCheckin:
0
cns.swup.patchbaseline:
current
cns.swup.regRequired:
true
cns.transport.serverurl:
https://cns-transport.sun.com
patchsvr settings:
Patch source URL: https://getupdates.sun.com
Cache location: /var/sadm/spool/patchsvr
Sun UC package status:
SUNWbreg not installed
SUNWdc not installed

I added patch 121082-08 and 123896-10 and modified the entries in /usr/sbin/pprosvc and /usr/bin/updatemanager.
I am now unable to register the system using the Registration Wizard or sconadm (Invalid Sun Online credentials which I know are correct).
Also, smpatch analyze exits with a timeout.
~~~~~reginfo.txt~~~~~~
userName=[obfuscated]
password=[obfuscated]
hostName=
subscriptionKey=
portalEnabled=false
proxyHostName=
proxyPort=
proxyUserName=
proxyPassword=
sconadm register -a -r /tmp/reginfo.txt
~~~~~basicreg.log~~~~~
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.BasicReg loadPropertiesFromHomeDir
INFO: properties file loaded from the default config.properties
May 12, 2009 11:46:53 AM com.sun.scn.util.Utils getLocalHostNames
INFO: get hostname 172.28.121.3
May 12, 2009 11:46:53 AM com.sun.scn.util.Utils getLocalHostNames
INFO: first returned hostname 172.28.121.3
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.cacao.NetworkProxyCacaoAdapter setProxy
INFO: SCNNetworkProxyConfigMBean.setHost() = null
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.cacao.NetworkProxyCacaoAdapter setProxy
INFO: SCNNetworkProxyConfigMBean.setPort() = null
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.cacao.NetworkProxyCacaoAdapter setProxy
INFO: SCNNetworkProxyConfigMBean.setUser() = null
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.cacao.NetworkProxyCacaoAdapter setProxy
INFO: SCNNetworkProxyConfigMBean.setPassword() = null
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: userName = [obfuscated]
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: password = *****
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: hostName =
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: subscriptionKey = ********
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: portalEnabled =false
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.BasicRegCLI run
INFO: Authenticating user ...
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter getSCNClientSession
INFO: CREATING SCNClientSession
May 12, 2009 11:46:53 AM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter$LoginAccountCallbackHandler handle
INFO: account callback setting username: [obfuscated]
May 12, 2009 11:47:14 AM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter loginAccount
SEVERE: Error: login account exception: AccessDeniedFault
May 12, 2009 11:47:14 AM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter loginAccount
SEVERE:
com.sun.scn.jmx.impl.UISClientLoginModule.login(UISClientLoginModule.java:216)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
javax.security.auth.login.LoginContext$5.run(LoginContext.java:706)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:703)
javax.security.auth.login.LoginContext.login(LoginContext.java:575)
com.sun.scn.jmx.impl.UISClientLogin.login(UISClientLogin.java:201)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
javax.management.StandardMBean.invoke(StandardMBean.java:323)
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:203)
com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:783)
com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInterceptor.java:638)
com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)
com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefaultForwarder.java:126)
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
java.security.AccessController.doPrivileged(Native Method)
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350)
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
sun.rmi.transport.Transport$1.run(Transport.java:153)
java.security.AccessController.doPrivileged(Native Method)
sun.rmi.transport.Transport.serviceCall(Transport.java:149)
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
java.lang.Thread.run(Thread.java:595)
May 12, 2009 11:47:14 AM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter getLoginResult
INFO: SCN Fault: AccessDeniedFault
May 12, 2009 11:47:14 AM com.sun.cns.basicreg.BasicRegCLI run
SEVERE: Sun On-line Account authentication failed
~~~~~~~~~~~~

X86 via patchsvr, "Failed to validate the digital signature(s)"

Been running very well for a while, now I'm getting these errors after an smpatch update/
bash-3.00# smpatch update
com.sun.patchpro.util.Percentage@96b5c2
119146-05 has been validated.
com.sun.patchpro.util.Percentage@5db5ae
119253-05 has been validated.
com.sun.patchpro.util.Percentage@42f352
119316-03 has been validated.
com.sun.patchpro.util.Percentage@1df2964
119251-03 has been validated.
com.sun.patchpro.util.Percentage@1ab600f
119255-06 has been validated.
com.sun.patchpro.util.Percentage@2fb002
120475-02 has been validated.
com.sun.patchpro.util.Percentage@cc7439
118924-02 has been validated.
com.sun.patchpro.util.Percentage@e2892b
118727-03 has been validated.
com.sun.patchpro.util.Percentage@9b688e
120236-01 has been validated.
com.sun.patchpro.util.Percentage@ed5d9d
120544-01 has been validated.
com.sun.patchpro.util.Percentage@1682a53
com.sun.patchpro.util.Percentage@7a9224
118891-01 has been validated.
com.sun.patchpro.util.Percentage@110b640
119686-03 has been validated.
com.sun.patchpro.util.Percentage@2d59a3
119076-06 has been validated.
com.sun.patchpro.util.Percentage@158015a
120010-01 has been validated.
com.sun.patchpro.util.Percentage@c0c8b5
119716-03 has been validated.
com.sun.patchpro.util.Percentage@b914b3
119108-06 has been validated.
com.sun.patchpro.util.Percentage@13fba1
120777-03 has been validated.
com.sun.patchpro.util.Percentage@1ed27e4
118345-04 has been validated.
com.sun.patchpro.util.Percentage@d61aef
118372-04 has been validated.
com.sun.patchpro.util.Percentage@82674b
119997-01 has been validated.
com.sun.patchpro.util.Percentage@14b84c7
119995-01 has been validated.
com.sun.patchpro.util.Percentage@fa5ff3
120037-01 has been validated.
com.sun.patchpro.util.Percentage@1b17d49
120035-01 has been validated.
com.sun.patchpro.util.Percentage@19855ed
119991-01 has been validated.
com.sun.patchpro.util.Percentage@31688f
120252-02 has been validated.
com.sun.patchpro.util.Percentage@1c794cc
120738-01 has been validated.
com.sun.patchpro.util.Percentage@1f9e31e
119987-01 has been validated.
com.sun.patchpro.util.Percentage@adf5be
119375-05 has been validated.
com.sun.patchpro.util.Percentage@e0c7c3
120665-01 has been validated.
com.sun.patchpro.util.Percentage@15b123b
118873-02 has been validated.
com.sun.patchpro.util.Percentage@9fdee
120051-01 has been validated.
com.sun.patchpro.util.Percentage@1fe4169
118851-02 has been validated.
com.sun.patchpro.util.Percentage@178920a
118863-01 has been validated.
com.sun.patchpro.util.Percentage@bbfa5c
120049-01 has been validated.
com.sun.patchpro.util.Percentage@131de9b
120347-01 has been validated.
com.sun.patchpro.util.Percentage@10d95cd
120720-01 has been validated.
com.sun.patchpro.util.Percentage@e5f46e
com.sun.patchpro.util.Percentage@1128f5a
118885-01 has been validated.
com.sun.patchpro.util.Percentage@1818f80
120470-02 has been validated.
com.sun.patchpro.util.Percentage@f42160
120468-02 has been validated.
com.sun.patchpro.util.Percentage@1bb326c
120047-01 has been validated.
com.sun.patchpro.util.Percentage@eb7331
120628-01 has been validated.
com.sun.patchpro.util.Percentage@1d7b222
119585-01 has been validated.
com.sun.patchpro.util.Percentage@1efe475
com.sun.patchpro.util.Percentage@7ff5b6
118847-01 has been validated.
com.sun.patchpro.util.Percentage@dc9065
com.sun.patchpro.util.Percentage@8beff2
com.sun.patchpro.util.Percentage@1362a63
119118-05 cannot be validated.
com.sun.patchpro.util.Percentage@c67a88
119417-01 cannot be validated.
com.sun.patchpro.util.Percentage@96ad7c
120455-01 cannot be validated.
com.sun.patchpro.util.Percentage@57ae58
120283-01 has been validated.
com.sun.patchpro.util.Percentage@775121
119373-02 has been validated.
com.sun.patchpro.util.Percentage@1f8acdc
120459-01 has been validated.
com.sun.patchpro.util.Percentage@11cc367
119543-05 has been validated.
com.sun.patchpro.util.Percentage@160c4b0
119411-02 has been validated.
com.sun.patchpro.util.Percentage@114025
119413-06 has been validated.
com.sun.patchpro.util.Percentage@8a52b6
120457-01 has been validated.
com.sun.patchpro.util.Percentage@13c550f
119549-02 has been validated.
com.sun.patchpro.util.Percentage@1f488f1
120297-01 has been validated.
com.sun.patchpro.util.Percentage@14a9387
120136-01 has been validated.
com.sun.patchpro.util.Percentage@11b86c7
com.sun.patchpro.util.Percentage@2da5a6
Unexpected Failure: java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
bash-3.00#
And there it dies. here's the client's version information
bash-3.00# pkginfo -l SUNWppror
PKGINST: SUNWppror
NAME: PatchPro core functionality (Root)
CATEGORY: system
ARCH: i386
VERSION: 5.0,REV=2005.01.09.21.19
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: PatchPro core functionality (Root)
PSTAMP: pm8-20020050222115150
INSTDATE: Jun 20 2005 12:41
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 15 installed pathnames
8 shared pathnames
3 linked files
9 directories
1 executables
5 blocks used (approx)
bash-3.00# pkginfo -l SUNWpprou
PKGINST: SUNWpprou
NAME: PatchPro core functionality (Usr)
CATEGORY: system
ARCH: i386
VERSION: 5.0,REV=2005.01.09.21.19
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: PatchPro core functionality (Usr)
PSTAMP: pm8-20020050222115151
INSTDATE: Jun 20 2005 12:41
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 25 installed pathnames
7 shared pathnames
10 directories
5 executables
bash-3.00# uname -a
SunOS dns01 5.10 Generic_118844-01 i86pc i386 i86pc
bash-3.00#
Help?
Thanks,
Doug
1630 blocks used (approx)

Unfortunatly the update server is having some very strange hicups every now and then. I've been able to reproduce this once on a sparc box. What I did was basicly running 'smpatch analyze' for a second time, followed by the regular 'update' command after which things worked out for me.
Some strange things also occur when you sometimes run the 'analyze' command, and then run it again. Sometimes you'll be presented with 2 different lists of available updates.

Smpatch failing?

Similar Messages

Maybe you are looking for