Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Server gives conflicting status, or just doesn seem to work. How can I fix it?

April 26, 2017conflicting gives server Status

0

Posted

Server gives conflicting status, or just doesn seem to work. How can I fix it?

1 Answer

0

Posted

In Solaris Management Console 2.0, it is possible to stumble into catch-22 situation where init.wbem stop indicates the server is not running, yet init.wbem start indicates it already is! One way for this to happen is to run /etc/init.d/init.wbem start when smcboot is running. Other ways would be if the server daemon crashed or was manually killed. If you find yourself in this situation, implement the following steps: • su root • kill all instances of the smcboot process (if any are running) • kill all instances of the cimomboot process (if any are running) • kill all instances of Solaris Management Console-related JVMs. These will contain either “-Dviper.fifo.path=” or “-Djava.security.policy=” in their command paths. • rm -rf /tmp/smc where is usually 898 Then, invoking /etc/init.d/init.wbem start will successfully start the smcboot process, and the server will be available upon the next connection from the console.