# smpatch analyze -C patchpro.log.level=3 -C patchpro.debug=true
Try the command above. Also, make sure you have the latest versions of the PM 2.0 patches installed including the LPS patches if applicable. If you are suing an lps you can also review the lps to see if there are any problems indicated there.
Thanks for that. The command you gave hangs with no output on three different machines. All have PM patch 112945-44 installed. We are not using a Local Patch Server. Here is the config, same on all machines:
ls0003: smpatch get
patchpro.backout.directory-""
patchpro.download.directory-/var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.source-https://updateserver.sun.com/solaris/
patchpro.patchset-patchdb1
patchpro.proxy.host -""
patchpro.proxy.passwd********
patchpro.proxy.port -8080
patchpro.proxy.user -""
patchpro.sun.passwd ********
patchpro.sun.user-""
Thanks again. Using patchdb server rather than patchdb1 causes the analyze to say "No patches required." Removing and reapplying the PM patch did not help.
In studying the system, the behavior is always the same: the java process stops receiving data from the update server but the TCP connection remains open. If I run several times, I get the hang always at a different place, sometime while the /var/sadm/spool/cache files are being downloaded, sometimes in the middle of a particular patch. On a few occasions, as many as three patches will come across the wire before the hang.
I tried adding the debug options you gave to the "smpatch update" and "smpatch download" commands but it won't accept those args.
Any other ideas?
Hi
Please show us the output of the following search for Update Connection related patches :
# showrev -p | egrep '^Patch: (11978[8|9]|12033[5|6]|12108[1|2])'
# showrev -p | egrep '^Patch: (12111[8|9]|12145[3|4]|12156[3|4])'
# showrev -p | egrep '^Patch: (12223[1|2]|12300[3|4|5|6]|124463|12461[4|5])'
I believe the patchsource url you are using is deprecated. However we should check out these patches first.
Mod.
Apologies for that, they are indeed the Solaris 10 patches.
Have you tried clearing out the cache directory and restarting the wbem service?
# rm /var/sadm/spool/cache/*
# /etc/init.d/init.wbem stop
# /etc/init.d/init.wbem start
If this does not work, have there been any changes made to the system recently such as upgrading Java?
I had tried clearing the cache, but not bouncing wbem; the latter did not help either.
Here is the Java version on all four machines:
ls0003: /usr/bin/java -version
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
I really need to get these machines updated!