[one-users] Problem with VMWare Server 2.0 as hypervisor

Wed Jun 9 02:58:37 PDT 2010

Hi Manish,

Good news!! I'm sure this feedback would be useful to other OpenNebula users.

So, what is the issue with the 443 port then?

Regards,

-Tino

--
Constantino Vázquez, Grid & Virtualization Technology
Engineer/Researcher: http://www.dsa-research.org/tinova
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org

On Wed, Jun 9, 2010 at 11:34 AM, Manish Sapariya <manish at gslab.com> wrote:
> Hi Tino,
> I was finally tracked down the problem.
>
> My tools were compiled using Sun JDK, however
> my PATH was pointing to Icedtea java. When I
> corrected the PATH to use Sun Java, opennebula started
> Monitoring to ESXi server.
>
> I still have issues with VMWare Server configured
> to run on 443 though.
>
> Thanks for all the help though.
> Manish
>
> On 6/8/2010 6:29 PM, Manish Sapariya wrote:
>>
>> I suspected it to be so, and hence I tried to run OneImVmware
>> from the command line. It fails with exception indicating that it
>> is not able to find my keystore or not able to access it.
>>
>> However when I use same keystore to run connect samples from VI-SDK it
>> works all right. So I am not sure what's wrong.
>>
>> Anyways, thanks for the pointer, I will go through it to check if I
>> have something wrong in my setup.
>>
>> Thanks and Regards,
>> Manish
>>
>>
>>
>> On 6/8/2010 6:13 PM, Tino Vazquez wrote:
>>>
>>> Sorry, I forgot the link
>>>
>>> [1] http://jcalcote.wordpress.com/2009/06/19/java-https-key-setup/
>>>
>>> --
>>> Constantino Vázquez, Grid& Virtualization Technology
>>> Engineer/Researcher: http://www.dsa-research.org/tinova
>>> DSA Research Group: http://dsa-research.org
>>> Globus GridWay Metascheduler: http://www.GridWay.org
>>> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>>>
>>>
>>>
>>> On Tue, Jun 8, 2010 at 2:43 PM, Tino Vazquez<tinova at fdi.ucm.es> wrote:
>>>>
>>>> Hi,
>>>>
>>>> It looks like you are having problems with your keystore, maybe the
>>>> certification file associated to the host is not its certificate?
>>>>
>>>> Take a look at this [1] for more insight. I suggest rebuilding the
>>>> keystore entry for that host.
>>>>
>>>> Regards,
>>>>
>>>> -Tino
>>>>
>>>> --
>>>> Constantino Vázquez, Grid& Virtualization Technology
>>>> Engineer/Researcher: http://www.dsa-research.org/tinova
>>>> DSA Research Group: http://dsa-research.org
>>>> Globus GridWay Metascheduler: http://www.GridWay.org
>>>> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>>>>
>>>>
>>>>
>>>> On Tue, Jun 8, 2010 at 1:22 PM, Manish Sapariya<manish at gslab.com> wrote:
>>>>>
>>>>> Hi Tino,
>>>>> Thanks for the reply.
>>>>>
>>>>> I am using FQDN of the host, it is resolvable.
>>>>> Port 443 is accessible using telnet and the browser as well.
>>>>> I tried changing the port to 8333 and recompiling the sources
>>>>> but it did not help.
>>>>>
>>>>> I just now tried with ESXi server as well
>>>>> and I am seeing same problem. When I printed
>>>>> the stack trace after modifying some code,
>>>>> I see following exception.
>>>>>
>>>>>
>>>>> ===========================================================================================
>>>>>
>>>>> [08.06.2010 16:48:19] Failed monitoring host
>>>>> leopard2.gslab.com.Reason: ;
>>>>> nested exception is:
>>>>> java.net.SocketException: java.security.NoSuchAlgorithmException:
>>>>> Error constructing implementation (algorithm: Default, provider:
>>>>> SunJSSE,
>>>>> class: sun.security.ssl.DefaultSSLContextImpl)
>>>>> ---- Debug stack trace ----
>>>>> AxisFault
>>>>> faultCode:
>>>>> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>>>>> faultSubcode:
>>>>> faultString: java.net.SocketException:
>>>>> java.security.NoSuchAlgorithmException: Error constructing
>>>>> implementation
>>>>> (algorithm: Default, provider: SunJSSE, class:
>>>>> sun.security.ssl.DefaultSSLContextImpl)
>>>>> faultActor:
>>>>> faultNode:
>>>>> faultDetail:
>>>>>
>>>>> {http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
>>>>> java.security.NoSuchAlgorithmException: Error constructing
>>>>> implementation
>>>>> (algorithm: Default, provider: SunJSSE, class:
>>>>> sun.security.ssl.DefaultSSLContextImpl)
>>>>> at
>>>>>
>>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(SSLSocketFactory.java:197)
>>>>>
>>>>>
>>>>> ============================================================================================
>>>>>
>>>>>
>>>>> When I tried to compile the samples in SDK and invoke the connect
>>>>> sample it
>>>>> connects alright without giving the exception. In fact
>>>>> it was also failing when I was using Icedtea java 1.7. But when
>>>>> I switched to Sun Java 1.5, the connect sample in SDK started working
>>>>> fine, but not opennebula. I have made sure that the JAVAHOME points
>>>>> to sun java.
>>>>>
>>>>> I am clueless as far as this error is concerned and have tried out
>>>>> all the possible things that I can think of.
>>>>>
>>>>> I would really appreciate any help getting this to work.
>>>>>
>>>>> Do you think I shall give a try using opennebula controller on Ubuntu?
>>>>>
>>>>> Thanks and Regards,
>>>>> Manish
>>>>>
>>>>> Office Phone : 46711053
>>>>> Extension : #1053
>>>>>
>>>>> On 6/8/2010 3:40 PM, Tino Vazquez wrote:
>>>>>>
>>>>>> Hi Manish,
>>>>>>
>>>>>> Let's try to avoid common problems:
>>>>>>
>>>>>> * Try a telnet connection between OpenNebula front-end and the remote
>>>>>> vmware server host to port 443, (note that vmware server needs to be
>>>>>> listening in port 443). This is to avoid firewall issues.
>>>>>>
>>>>>> * Are you using the FQDN of the host?
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> -Tino
>>>>>>
>>>>>> --
>>>>>> Constantino Vázquez, Grid& Virtualization Technology
>>>>>> Engineer/Researcher: http://www.dsa-research.org/tinova
>>>>>> DSA Research Group: http://dsa-research.org
>>>>>> Globus GridWay Metascheduler: http://www.GridWay.org
>>>>>> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jun 7, 2010 at 2:55 PM, Manish Sapariya<manish at gslab.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>> I am not able to get my setup of OpenNebula with
>>>>>>> VMWare Server 2.0 running.
>>>>>>>
>>>>>>> The im_vmware.log show 'Connection refused'.
>>>>>>>
>>>>>>> I have tried following but did not help.
>>>>>>> - Change the port of VMWare server to 443.
>>>>>>> - Change the java code to talk to 8333.
>>>>>>>
>>>>>>> Here is my configuration:
>>>>>>>
>>>>>>> - OS Fedora (Both for controller and the VMWare server)
>>>>>>> - one 1.4
>>>>>>>
>>>>>>> Is there any way where in I can tell if my setup is
>>>>>>> correct or not, some unit tests or alike?
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>> Manish
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users at lists.opennebula.org
>>>>>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>