RE: cimprovider/cimconfig commands will crash cimserver if configured for non-standard http(s) port

Hello Venkate

  Thanks for the  info. I think my build was corrupted as I was trying 2-3 versions of Pegasus.  I did the fresh built of the latest version 2.11.0 and behavior is as you noted.
Thank you for the suggestion.

Thanks
Veeresh



From: Venkateswara R Puvvada [mailto:[email protected]]
Sent: Friday, September 09, 2011 3:56 PM
To: Yaligar, Veeresh S (USD SRDL)
Cc: [email protected]
Subject: Re: cimprovider/cimconfig commands will crash cimserver if configured for non-standard http(s) port

Veeresh,

The CIMServer administrative commands does not work if standard ports are changed on Windows. On UNIX systems, these commands connects to CIMServer through local domain socket and changing the port number is not a problem. Since there is no way to specify port number to these commands, either CIMServer should run on standard ports or etc\services file can be updated with the non standard port number on Windows. Its weird that you are observing the CIMServer crash instead of  error message saying  "The CIM server may not be running". Provide stack trace or open a bug with details to analyze the problem further.

Venkat




From:        "Yaligar, Veeresh S \(USD SRDL\)" <[email protected]>
To:        "[email protected]" <[email protected]>
Date:        08/09/2011 22:19
Subject:        cimprovider/cimconfig commands will crash cimserver if configured for non-standard http(s) port
________________________________



Hi
  On a windows setup I have cimserver configured to with non-standard port. The service will crash as soon as I execute cimprovider –ls or cimconfig –lc commands.
This does not happened if its configured to default ports like 5988 and 5989..
This is observed both in 2.10.0 and 2.11.0 versions.
Any clue ?

Thanks
Veeresh