SMC (off-topic) but if you can help... I will appreciate it.

Question

On a fresh install of Sparc Solaris 9 - the SMC app works. Upon patching to yesterday's 9_Recommended - it fails - the applets all have red stop signs in the console, and it says someting like - 'There is no server running...' and 'No Solaris Management Console server was available on the specified server.'
This is in the console:
kermit console login: java.io.FileNotFoundException: /var/sadm/smc/properties/.s
erver (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at com.sun.management.viperimpl.util.security.SMCSSLConfig.setu pServer(S
MCSSLConfig.java:114)
at com.sun.management.viperimpl.server.ViperWbemServer.main(Vip erWbemSer
ver.java:61)
Starting Solaris Management Console server version 2.1.0.
endpoint created: :898
Solaris Management Console server is ready.
I have tried to stop/start/restart the server with the init.wbem script in /etc/init.d
Thanks for any hints.
S7

Answer 1

With S10 06/06 + recommended patches I had a problem starting SMC. On starting smc (/usr/bin/smc &), I get this error message:
No Server Running
No Solaris Management Console server was available on the specified server. Please ensure there is a Solaris Management Console server available on the specified host and that it is running.
I spent quite some time on this and found the solution, which is to stop SMC, remove all SMC packages, add SMC packages and start SMC. SMC then starts OK. Even if I re-add the SMC patches, it still works OK, so here' s the procedure:
su root
Run /etc/init.d/init.wbem stop
kill all instances of the smcboot process, if any
kill all instances of the cimomboot process, if any
kill all instances of SMC-related JVMs, if any. These will contain
either"-Dviper.fifo.path=" or "-Djava.security.policy=" in their command
paths.
Solaris 9 & 10: rm -rf /var/run/smc<port> where <port> is usually 898
De-install these pkgs
SUNWadmj SUNWwbapi SUNWwbcou SUNWwbcor SUNWwbdev SUNWwbdoc SUNWwbpro
SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev SUNWmgapp SUNWmga
SUNWdclnt SUNWpmgr SUNWrmui SUNWlvmr SUNWlvma SUNWlvmg
Then any SMC localization pkgs (if applicable):
SUNWjadcl SUNWjlvmg SUNWjmga SUNWjrmui
Then any Applications localization pkgs (if applicable).
Run "pkginfo <pkg>.2" If it exists, then run "pkgrm <pkg>.2"
Repeat this N times for make sure all <pkg>.N are purged, but 2 or 3
should be
sufficient "rm -rf /var/sadm/smc"
Install the pkgs exactly in the order specified:
All the WBEM pkgs must be installed first in this order:
SUNWadmj SUNWwbapi SUNWwbcou SUNWwbcor SUNWwbdev SUNWwbdoc SUNWwbpro
Then the SMC pkgs in this order:
SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev
Then the Applications pkgs in this order.
SUNWmgapp SUNWmga SUNWdclnt SUNWpmgr SUNWrmui
SUNWlvmr SUNWlvma SUNWlvmg
Then any SMC localization pkgs (if applicable):
SUNWjadcl SUNWjlvmg SUNWjmga SUNWjrmui
Then any Applications localization pkgs (if applicable).
Then invoking /etc/init.d/init.wbem start will successfully start the server.
To avoid this problem, supposely all you have to do is restart SMC after applying patches. I haven't gone back and tried to recreate the problem to verify this though:
/etc/init.d/init.wbem stop
/etc/init.d/init.wbem start