- 论坛徽章:
- 0
|
版本solaris express：08/06 for x86:
---------------感谢sun smc技术支持工作人员---------------------------
总结和摘抄：
customizing the solaris management console
基本内容:
描述solaris管理控制工具箱编辑器的一些操作
使用solaris管理控制工具箱编辑器
启动solaris管理控制台包括三个部分:
1,solaris管理控制台服务
2,控制台
3,solaris管理控制台工具箱编辑器
判断solaris管理控制台服务程序是否可用,用下面的命令:
# /etc/init.d/init.wbem status
停止它的使用:
# /etc/init.d/init.wbem stop
开始它的使用:
# /etc/init.d/init.wbem start
可以以一般用户来开启solaris管理控制台，但是一些功能和应用程序可能不会加载，除非用root用户登陆
启用solaris管理控制台:# smc
使用工具箱编辑器: # smc edit
在运行solaris管理控制台并执行某些改动之前必须对其中的两个文件进行备份:
# cd /var/sadm/smc/toolboxes
# cp smc/smc.tbx smc.tbx.orig
# cp this_computer/this_computer.tbx this_computer.tbx.orig
除了图形界面下添加工具箱URL，也可以通过命令行的方式来添加工具箱URL，使用smcregister命令可以对工具箱进行添加、移除、详细列表的功能.但是使用这个命令能够完成的功能较之图形化下面操作很有限.
用smcregister命令添加工具箱URL：
# /usr/sadm/bin/smcregister toolbox add tbxURL http://sys43:898/toolboxes/this_computer.tbx
-B /var/sadm/smc/toolboxes/smc/smc.tbx
要注意的一点是,在管理控制台中添加了新的工具或新增加了其他功能，要想使用这些功能，必须重新启动
管理控制台才能生效
用smcregister命令添加工具：
# /usr/sadm/bin/smcregister toolbox add tool com.sun.admin.diskmgr.client.VDiskMgr -H sys43:898
loading...
实战经验：
in solaris express b_44,to start smc:
1.please refresh the remained unuseful file & process:
You may need to just first start wbem with command:
/etc/init.d/init.wbem start
Then run smc&
But if problem persists the commands below can be used to restart all of smc and wbem...
Sometimes when the smc or wbem processes do not come down gracefully, init.wbem is no longer successful in fully stopping or starting the wbem server daemon, subsequently a side-affect is smc will fail to launch, or other smc anomolies may occur.
To resolve for SMC 2.1, perform steps as follows:
Open a termal,
* /usr/dt/bin/dtterm -C
* su root
* /etc/init.d/init.wbem stop
* kill all instances of the smcboot process (if any are running), ie:
# ps -ef|grep smcboot (manually kill any running processes)
* kill all instances of the cimomboot process (if any are running), ie:
# ps -ef|grep cimom (manually kill any running processes)
* kill all instances of Solaris Management Console-related JVMs. These will contain
either "-Dviper.fifo.path=" or "-Djava.security.policy=" in their command paths, ie:
# /usr/ucb/ps -wwax | grep viper (manually kill any running processes)
* Remove the /var/run/smc<port> where <port> is usually 898, ie:
# rm -rf /var/run/smc898
at last: # rm -rf /var/sadm/smc
# rm -rf /var/sadm/wbem
# rm -rf /tmp/smc898
2.please listen tcp/ip port:
# svcadm disable wbem
# svcadm enable wbem
# svcadm disable wbem
# ps -ef | grep smc
root 3025 2979 0 20:16:50 pts/4 0:00 grep smc
# /etc/init.d/init.wbem startnow
# Starting Solaris Management Console server version 2.1.0.
endpoint created: localhost/127.0.0.1:898
Registration setup: 8/8 (Executing SUNWpmgr_reg.sh)
Registering components: 64/64 (Registering PatchMgrCli.jar) er)
Solaris Management Console server is ready.
# /etc/init.d/init.wbem status
Solaris Management Console server version 2.1.0 running on port 898.
# smc &
4526
# Java Accessibility Bridge for GNOME loaded.
* Now try to start wbem, wait several minutes,
# /etc/init.d/init.wbem start (be patient, this can take several minutes)
# /etc/init.d/init.wbem status
3.how to trace smc debug message:
Please follow the below steps to enable debugging and let me know what is failing.
1) Stop the Solaris Web-Based Enterprise Management server:
> /etc/init.d/init.wbem stop
2) Edit the line below, in the file: /etc/init.d/init.wbem
$VIPER_HOME/bin/smcwbemserver -p $SMC_PORT start >/dev/msglog 2>&1 &
If you want to redirect the debug messages to a file, replace
/dev/msglog with the absolute path of the file name.
Example:
$VIPER_HOME/bin/smcwbemserver -p $SMC_PORT start >/tmp/debugLog 2>&1 &
Otherwise, for the debug messages to be printed on the terminal, remove
the redirection
Example:
$VIPER_HOME/bin/smcwbemserver -p $SMC_PORT start
3) Edit the file: /usr/sadm/lib/smc/bin/smcwbemserver and add the lines
below:
-Dwbem.debug.level=3m \
-Dwbem.debug.device=stderr \
Insert them between the following lines:
-Xmx128m \
-Djava.security.policy=${VIPER_HOME}/policy/smcwbemserver.policy \
So, after modification, the file: /usr/sadm/lib/smc/bin/smcwbemserver
will contain:
....
....
-Xmx128m \
-Dwbem.debug.level=3m \
-Dwbem.debug.device=stderr \
-Djava.security.policy=${VIPER_HOME}/policy/smcwbemserver.policy \
....
....
4) Now start the WBEM server using
/etc/init.d/init.wbem startnow( There is a small correction stop the smcboot process by the command
/etc/init.d/init.wbem stop
and start it using the below command
/etc/init.d/init.wbem startnow)
Then run "smc -d 0" command in another terminal and observe
the terminal in which you have started the /etc/init.d/init.wbem
process.
4.the related work explain:
Nicolas Linkert wrote:
>I have installed snv 41 and have just noticed that I cannot start smc. Is this a known issue?
>
>Server not running. On this server no Solaris management Console server was found.
>
>
There are a few known issues with SMC in B41. It is now an SMF
service so
you can issue "svcadm enable wbem". It will listen only on
127.0.0.1 as per
the requirements of the Secure By Default project. To enable
listening on all
interfaces you can stop it and execute
"svccfg -s wbem setprop options/tcp_listen=true"
But note that there exist several bugs.
These are fixed in B42 and enabling/disabling listening for remote
connections
is done via SBD profiles. |
|
免费注册
发表于 2006-08-29 20:53
