Re: [Xen-cim] Re: Wbemcli setup question

[Gareth S Bestor <bestor@xxxxxxxxxx>]

Luke, if you are getting an SSL authentication from wbemcli please feel free to post a sample here and to the SBLIM milaing list (see http://lists.sourceforge.net/mailman/listinfo/sblim-devel).

As Jim suggests, my first recommendation would be to ensure regular http acess is enabled for OpenWBEM. But wbemcli should be able to handle https access either way, so if it looks like a wbemcli problem (as opposed you your https OpenWBEM setup) I'd be interested to know.

- Gareth

Dr. Gareth S. Bestor
IBM Linux Technology Center
M/S DES2-01
15300 SW Koll Parkway, Beaverton, OR 97006
503-578-3186, T/L 775-3186, Fax 503-578-3186

"Jim Fehlig" <jfehlig@xxxxxxxxxx>

"Jim Fehlig" <jfehlig@xxxxxxxxxx>
Sent by: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx

08/04/06 08:47 AM

To	<Lukasz.Szymanski@xxxxxxxxxx>
cc	xen-cim@xxxxxxxxxxxxxxxxxxx
Subject	[Xen-cim] Re: Wbemcli setup question

Luke,

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:

https://bugzilla.novell.com/show_bug.cgi?id=193866
https://bugzilla.novell.com/show_bug.cgi?id=194567
https://bugzilla.novell.com/show_bug.cgi?id=195189
https://bugzilla.novell.com/show_bug.cgi?id=195192

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
manipulate:

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
http://localhost:5988/root/cimv2/SomeObjectPath?

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

Jim

Jim Fehlig
Software Engineer
jfehlig@xxxxxxxxxx
801.861.5254

Novell, Inc.
Software for the Open Enterprise
http://www.novell.com/open

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

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 127.0.0.1:40021:
47955036746064:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http
request:s23_srvr.c:379:\

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.

Thanks,
Luke



_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim