This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-cim] Re: Wbemcli setup question

To: <Lukasz.Szymanski@xxxxxxxxxx>
Subject: [Xen-cim] Re: Wbemcli setup question
From: "Jim Fehlig" <jfehlig@xxxxxxxxxx>
Date: Fri, 04 Aug 2006 09:47:56 -0600
Cc: xen-cim@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Aug 2006 08:48:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx

Not sure why you have 3 openwbem.conf files.  Seems like you have some
kind of strange installation which may be the cause of your problem. 
Did you install openwbem when you installed SLES 10?  If so (or you
installed it later via YaST) then the conf file in /etc/openwbem is the
one being used.  You could see what package owns these various conf
files, e.g. 'rpm -qf /etc/openwbem/openwbem.conf' will display the
owning package.

Probably best to just use the openwbem that comes with SLES 10.  I have
some patches to that version which fix some bugs in the CMPI interface,
but I don't think any of the bugs will affect work you are doing.  If
you have access to Novell's bugzilla here are the bugs I have
found/logged against openwbem while working on the xen providers:


FYI, I usually run openwbem from a terminal so I can see output of
cimom, providers, etc.
  - Stop currently running instance: /etc/init.d/owcimomd stop
  - Start cimom with debug flag: /usr/sbin/owcimomd -d

As far as the conf file goes, there are three directives I usually

1. 'owcimomd.allow_anonymous = true' will allow anyone access
2. 'http_server.http_port = 5988' to allow http access.  https only is
the default install setting.
3. 'cmpiprovifc.prov_location = /usr/lib/cmpi:/usr/local/lib/cmpi' to
specify where cimom will look for and load cmpi providers.  You can add
multiple search paths to this directive.

I see you have http access open so don't know why you are seeing the SSL
error.  Are you specifying a http model path in wbemcli, e.g. wbemain

I'll be around today for a few more hours so let me know if you have
additional questions.


Jim Fehlig
Software Engineer

Novell, Inc.
Software for the Open Enterprise

>>> "Szymanski, Lukasz K" <Lukasz.Szymanski@xxxxxxxxxx> 08/04/06 8:47 AM

I just upgraded to SLES 10 and have set up yawn mostly successfully.  I
had wbemcli set up before on SLES 9 but now I get is this error whenever
I try to run the sample code:

[47955036746064] SSL Handshake failed: SSLSocketImpl ctor: SSL accept
error while connecting to
47955036746064:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http

Attached is the openwbem.conf file.  I am not sure how this happened,
but I eneded up with 3 such files.  I have one in /etc/openwbem,
/tmp/openwbem-3.2.0/etc, and /tmp (all of my sblim, openwben, etc etc
files are in /tmp).  I am sending you the latest one, but I am not
exactly sure where it ought to go what I should do with the others.


Xen-cim mailing list

<Prev in Thread] Current Thread [Next in Thread>