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

Venkateswara R Puvvada <[email protected]>
Newsgroups gmane.network.open-pegasus.general
Message-ID <OF97C654A1.B31D7CBC-ON65257906.00259173-65257906.00395A11@in.ibm.com>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.