System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

cimservera not running after WBEMServices upgrade

SOLVED
Go to solution
Scott Lindstrom_2
Regular Advisor

cimservera not running after WBEMServices upgrade

I upgraded WBEMServices from A.02.05.04 to A.02.07.02. The release notes say I should have cimserver, cimservera, and cimserverd running after the swinstall. I have no cimservera process running.

Here are the processes that were running before the upgrade:

root 16338 16335 0 16:34:03 ? 0:00 /opt/wbem/lbin/cimprovagt 11 10 EMSHAProviderModule
root 16352 16335 0 16:34:05 ? 0:04 /opt/wbem/lbin/cimprovagt 20 18 HPUXLANIndicationProviderModule
root 16336 16335 0 16:34:02 ? 0:03 /opt/wbem/lbin/cimservera
root 2526 1 0 Feb 22 ? 0:42 /opt/wbem/lbin/cimserverd
wbemusr 3466 16335 0 18:25:54 ? 0:01 /opt/wbem/lbin/cimprovagt 35 30 HPUXFCIndicationProviderModule
root 16335 1 0 16:34:02 ? 13:34 /opt/wbem/lbin/cimserver
wbemusr 3468 16335 0 18:25:54 ? 0:01 /opt/wbem/lbin/cimprovagt 43 39 HPUXLANIndicationProviderModule
root 16339 16335 0 16:34:03 ? 6:15 /opt/wbem/lbin/cimprovagt 14 11 SFMProviderModule
wbemusr 3467 16335 0 18:25:54 ? 0:00 /opt/wbem/lbin/cimprovagt 39 35 HPUXIOTreeIndicationProviderModule
root 16350 16335 0 16:34:04 ? 0:05 /opt/wbem/lbin/cimprovagt 16 14 HPUXFCIndicationProviderModule
root 16351 16335 0 16:34:05 ? 1:55 /opt/wbem/lbin/cimprovagt 18 16 HPUXIOTreeIndicationProviderModule


and here are the ones afterwards:

root 18314 18296 0 15:34:46 ? 0:00 /opt/wbem/lbin/cimprovagt 0 5 10 root EMSHAProviderModule
root 18319 18296 0 15:34:48 ? 0:00 /opt/wbem/lbin/cimprovagt 0 5 10 root HPUXFCIndicationProviderModule
root 18320 18296 0 15:34:49 ? 0:00 /opt/wbem/lbin/cimprovagt 0 5 10 root HPUXIOTreeIndicationProviderModule
root 18315 18296 5 15:34:46 ? 0:06 /opt/wbem/lbin/cimprovagt 0 5 10 root SFMProviderModule
cimsrvr 18297 18296 15 15:34:45 ? 0:02 cimservermain --executor-socket 5
wbemusr 18325 18296 0 15:34:50 ? 0:00 /opt/wbem/lbin/cimprovagt 0 5 10 wbemusr HPUXIOTreeIndicationProviderModule
root 18296 1 0 15:34:45 ? 0:00 /opt/wbem/lbin/cimserver
wbemusr 18324 18296 0 15:34:50 ? 0:00 /opt/wbem/lbin/cimprovagt 0 5 10 wbemusr HPUXFCIndicationProviderModule
root 18321 18296 2 15:34:49 ? 0:00 /opt/wbem/lbin/cimprovagt 0 5 10 root HPUXLANIndicationProviderModule
wbemusr 18326 18296 0 15:34:50 ? 0:00 /opt/wbem/lbin/cimprovagt 0 5 10 wbemusr HPUXLANIndicationProviderModule
root 18422 1 0 15:34:50 ? 0:00 /opt/wbem/lbin/cimserverd
.

As you can see cimservera was running beforehand but not afterwards.

The swinstall ran clean:

* Target connection succeeded for "xxx:/".
* Source connection succeeded for "yyy:/depot/11.23/apps".
* Source: yyy:/depot/11.23/apps
* Targets: xxx:/
* Software selections:
WBEMSvcs,r=A.02.07.02,a=HP-UX_B.11.23_IA/PA,v=HP
WBEMServices.WBEM-CORE,r=A.02.07.02,a=HP-UX_B.11.23_IA/PA,v=HP,fr=A.02.07.02,fa=HP-UX_B.11.23_IA
WBEMServices.WBEM-CORE-COM,r=A.02.07.02,a=HP-UX_B.11.23_IA/PA,v=HP,fr=A.02.07.02,fa=HP-UX_B.11.23_IA/PA
WBEMServices.WBEM-MAN,r=A.02.07.02,a=HP-UX_B.11.23_IA/PA,v=HP,fr=A.02.07.02,fa=HP-UX_B.11.23_IA/PA
WBEMServices.WBEM-MX,r=A.02.07.02,a=HP-UX_B.11.23_IA/PA,v=HP,fr=A.02.07.02,fa=HP-UX_B.11.23_IA/PA
* Selection succeeded.


* Beginning Analysis and Execution
* Session selections have been saved in the file
"/root/.sw/sessions/swinstall.last".
* The analysis phase succeeded for "xxx:/".
* The execution phase succeeded for "xxx:/".
* Analysis and Execution succeeded.

When I try to stop/start cimserver, cimserverd will not end. I can [re]start cimserver without any errors (the old cimserverd is still running), but no cimservera starts.

Any suggestions or thoughts from anyone?
5 REPLIES
G V R Shankar
Valued Contributor
Solution

Re: cimservera not running after WBEMServices upgrade

Hi,

This is a expected behaviour. Please refer to the release notes page number 20.

http://docs.hp.com/en/B8465-90040/B8465-90040.pdf

Cheers,

Ravi.
Armin Kunaschik
Esteemed Contributor

Re: cimservera not running after WBEMServices upgrade

cimserver is really a bitch of a software, isn't it :-)

Sometimes some cim* daemons hang and need to be killed with signal 9. cimserverd will be restarted from inittab, so don't worry if it comes back instantly.

Maybe the upgrade went wrong. This happens very often (from my experience) with various symptoms like missing shared library dependencies or broken provider registrations. In this case forcibly re-install the WBEM filesets! Sometimes it's even necessary to reinstall all providers (or you figure out how to re-register the providers with their *.mof files manually)
Check the provider registrations and states with "cimprovider -ls"

My 2 cents,
Armin
And now for something completely different...
Scott Lindstrom_2
Regular Advisor

Re: cimservera not running after WBEMServices upgrade

Ravi - this is odd. I have the A.02.07 March *2008* release notes (recently downloaded from HP). The phrase about the change in behaviour for cimservera is not in there. Thanks for finding this for me!
G V R Shankar
Valued Contributor

Re: cimservera not running after WBEMServices upgrade

Hi Scott,

Recently I have download it from the following URL.

http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=WBEMSvcs

It says march 2009 release. I don't think there was March 2008 release for the version A.02.07.02

If you have downloaded it recently, then it has to be March 2009.

Cheers,
Ravi.
Scott Lindstrom_2
Regular Advisor

Re: cimservera not running after WBEMServices upgrade

The link I followed (by searching www.hp.com/go/softwaredepot) got me to these release notes:

HP WBEM Services Version A.02.07, Release Notes

Manufacturing Part Number: B8465-90037 March 2008

which did not contain the statement you pointed me to in this section:

To see if the CIM Server is running, issue the following command to check for the cimserver process: ps -ef | grep cimserver. You should see three processes: cimserver,
cimservera, and cimserverd (cimserverd is a daemon process that monitors cimserver to
ensure it remains available).

I am very grateful you were able to find a more recent copy of these release notes for me and solve my question!

Scott