smpatch analyze problems
Spmatch analyze has stopped working on one of our servers for no apparent reason.
It happens to be the local patch proxy.
That functionality is still working so ironically it can patch other machines, just not itself
The following errors appear in /var/adm/messages
Feb 27 10:35:31 cracow CNS Transport[669]: [ID 617356 daemon.error] Could not send message from queue: /var/tmp/cc-transport/CCTQueueStore/store/queues/REGISTRATION/registration
Feb 27 10:36:45 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@7a36a2 <=non-descript failure while closing database. String index out of range: -1
Feb 27 10:36:45 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@7a36a2 <=java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Feb 27 10:36:45 cracow at java.lang.String.substring(String.java:1768)
Feb 27 10:36:45 cracow at com.sun.patchpro.patch.PatchSequencer.removeObsoleteFromRequired(PatchSequencer .java:350)
Feb 27 10:36:45 cracow at com.sun.patchpro.patch.PatchSequencer.evaluatePatchList(PatchSequencer.java:330 )
Feb 27 10:36:45 cracow at com.sun.patchpro.patch.PatchSequencer.getPatchList(PatchSequencer.java:251)
Feb 27 10:36:45 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@7a36a2 <= at com.sun.patchpro.patch.PatchSequencer.getPatchList(PatchSequencer.java:221)
Feb 27 10:36:45 cracow at com.sun.patchpro.patch.GroupPatchSequencer.getPatchLists(GroupPatchSequencer.ja va:115)
Feb 27 10:36:45 cracow at com.sun.patchpro.model.PatchProModel.runSequencer(PatchProModel.java:1903)
Feb 27 10:36:45 cracow at com.sun.patchpro.model.PatchProStateMachine$9.run(PatchProStateMachine.java:482 )
Feb 27 10:36:45 cracow at com.sun.patchpro.util.State.run(State.java:266)
Feb 27 10:36:45 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@7a36a2 <=nullat java.lang.Thread.run(Thread.java:595)
Any suggestions?
# 1
How is "smpatch analyze" failing? Is the command hanging or is it exiting with an error?
The first error in the messages for "CNS Transport" relates to need to update the certificates for use with the Update Connection portal for remote patching (by applying patch 122231-01 for SPARC or patch 122232-01 for x86/x64). It does not affect patch analysis or patch downloading.
The other Java errors in the messages are likely to be the problem. Can you please check the installed version of Update Connection;
$ showrev -p | egrep '119107|121118'
# 2
It exits fine, it just doesnt show any patches to install.And I know there are available patchesThe patches installed arePatch: 119107-06Patch: 121118-05I left out all the dependencies that were being picked up by matching on the requires fields etc.
# 3
Can you please check what the following command prints to standard output and to the /var/adm/messages file.$ smpatch analyze -C patchpro.log.level=3 -C patchpro.debug=true
# 4
Stdout
cracow# smpatch analyze -C patchpro.log.level=3 -C patchpro.debug=true
Effective proxy host : ""
Effective proxy port : ""
Effective proxy user : ""
Effective proxy host : ""
Effective proxy port : ""
Effective proxy user : ""
Effective proxy host : ""
Effective proxy port : ""
Effective proxy user : ""
Effective proxy host : ""
Effective proxy port : ""
Effective proxy user : ""
No patches required.
cracow#
/var/adm/messages
Feb 27 18:11:34 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@198c6f3 <=non-descript failure while closing database. String index out of range: -1
Feb 27 18:11:34 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@198c6f3 <=java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Feb 27 18:11:34 cracow at java.lang.String.substring(String.java:1768)
Feb 27 18:11:34 cracow at com.sun.patchpro.patch.PatchSequencer.removeObsoleteFromRequired(PatchSequencer .java:350)
Feb 27 18:11:34 cracow at com.sun.patchpro.patch.PatchSequencer.evaluatePatchList(PatchSequencer.java:330 )
Feb 27 18:11:34 cracow at com.sun.patchpro.patch.PatchSequencer.getPatchList(PatchSequencer.java:251)
Feb 27 18:11:34 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@198c6f3 <= at com.sun.patchpro.patch.PatchSequencer.getPatchList(PatchSequencer.java:221)
Feb 27 18:11:34 cracow at com.sun.patchpro.patch.GroupPatchSequencer.getPatchLists(GroupPatchSequencer.ja va:115)
Feb 27 18:11:34 cracow at com.sun.patchpro.model.PatchProModel.runSequencer(PatchProModel.java:1903)
Feb 27 18:11:34 cracow at com.sun.patchpro.model.PatchProStateMachine$9.run(PatchProStateMachine.java:482 )
Feb 27 18:11:34 cracow at com.sun.patchpro.util.State.run(State.java:266)
Feb 27 18:11:34 cracow root: [ID 702911 user.error] => com.sun.patchpro.model.PatchProModel@198c6f3 <=nullat java.lang.Thread.run(Thread.java:595)
# 5
Hi,Can you confirm if this box has Java Enterprise System 4 installed.A similar problem has been reported when this software has been installed.Scott
# 6
The internal bug id is : 6386686
# 7
Yes, there is a test copy of jes messenging there
# 8
And uninstalling the JES suite has fixed the problem.
# 9
I have the same problem here. Is there any fix that don't require uninstalling of JES ?thanx a lot,bilke
bilke at 2007-7-6 13:33:22 >
# 10
I solved problem.
1. start /usr/bin/updatemanager
2. go to installed updates tab and select sun update connection clinet, system edition 1.0.4
3. click uninstall 1 selected update
4. after uninstallation close update manager
5. start /usr/bin/updatemanager and you will see missing patches
best regards,
bilke
bilke at 2007-7-6 13:33:22 >
# 11
Well, its presumably fixable since we have a bunch of machines running the jes suite, but I only saw the problem on that one machine.
I'm not sure what the difference is.
The other machines were installed as 2005q1 and later upgraded to 2005q4 whereas the machine with the problem started as 2005q4 I think.
Also the machine with the problem is a fair way behind on the jes recommended patch set.
# 12
Has this been "fixed fixed" ? Just today I had to remove this _again_ to get the UM to work.
# 13
If you have Sun Messaging installed then upgrading to 118207-51 solved it for me.
# 14
I spoke too soon.This has now started happening on multiple hosts.Even the ones without sun messenger installed.
# 15
Just for your information, bug ID 6386686 which addresses this issue is currently at 'Fix In Progress' status.
# 16
That bug ID implies its connected to java enterprise.But as far as I can tell, its now happening on all our solaris 10 machines regardless of whether they have any jes components installed.
# 17
Well, as suddenly as it appeared, it has vanished.smpatch analyze has started working again. And the error messages have stopped appearing.The whole sun update connection thing feels kind of fragile...It doesnt take much to upset it.
