[one-users] ONE 1.4 error monitoring VMWare host

Xavier Sarda Perez xavier.sarda at atosresearch.eu
Wed Jun 9 03:06:11 PDT 2010


Hi Tino,

Thank you for answering my first post so quickly.

I guess that you forgot something after "Have you tried the" in first instruction. But, talking about second instruction, I had run "SimpleClient" from VI samples and I got the following information:

Started
Object Type : Folder
Reference Value : ha-folder-vm
   Property Name : name
   Property Value : vm
Object Type : HostSystem
Reference Value : ha-host
   Property Name : name
   Property Value : servername.domain.es
Object Type : ResourcePool
Reference Value : ha-root-pool
   Property Name : name
   Property Value : Resources
Object Type : Folder
Reference Value : ha-folder-host
   Property Name : name
   Property Value : host
Object Type : ComputeResource
Reference Value : ha-compute-res
   Property Name : name
   Property Value : servername.domain.es
Object Type : VirtualMachine
Reference Value : 16
   Property Name : name
   Property Value : ONE-Master2
Object Type : Datacenter
Reference Value : ha-datacenter
   Property Name : name
   Property Value : ha-datacenter
Object Type : Folder
Reference Value : ha-folder-root
   Property Name : name
   Property Value : ha-folder-root
Ended SimpleClient

I think it's a correct output from SimpleClient because it's so close to VMware sample.

In addition, I turned on VMware log and got the following information due to failed monitoring:

[09.06.2010 11:49:25] MONITOR FAILURE 0 Failed monitoring host 192.168.252.10.
[09.06.2010 11:49:25] Failed monitoring host 192.168.252.10.Reason: null
---- Debug stack trace ----
java.lang.NullPointerException
        at GetProperty.getProperties(GetProperty.java:74)
        at GetProperty.getObjectProperty(GetProperty.java:59)
        at OneImVmware.loop(OneImVmware.java:166)
        at OneImVmware.main(OneImVmware.java:59)
[09.06.2010 11:49:25] ---------------------------

Also, IM VMware driver startup was successful according to im_vmware.log

Thank you once again!

-----Original Message-----
From: tinova79 at gmail.com [mailto:tinova79 at gmail.com] On Behalf Of Tino Vazquez
Sent: miércoles, 09 de junio de 2010 11:31
To: Xavier Sarda Perez
Cc: users at lists.opennebula.org
Subject: Re: [one-users] ONE 1.4 error monitoring VMWare host

Hi Xavi,

Ok, let's try the usual suspects:

* Have you tried using the

* Can you access the VMware server using the VI Client?

Also, it would be nice to enable debug in the IM VMware driver
($ONE_LOCATION/etc/imm_vmware/imm_vmwarerc)

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 3:14 PM, Xavier Sarda Perez
<xavier.sarda at atosresearch.eu> wrote:
> Hi everybody!
>
>
>
> I’m working on a project where we want to run OpenNebula over VMWare servers
> (using VMWare Server 2 installed onto Debian Lenny). I’m using OpenNebula
> 1.4 downloaded directly from OpenNebula site.
>
>
>
> I had followed VMWare hosts installation instructions (VI SDK run test it’s
> ok on ONE front-end) but something isn’t working straight because ONE is
> unable to monitor the VMWare host. At this time, we only have one server and
> exactly the same configuration that’s described on OpenNebula webpage.
>
>
>
> I had thought that it could be a problem about SSH access but SSH
> passwordless access is working properly.  Telnet access from front-end to
> cluster node is also working.
>
>
>
> Please take a look at following oned.log fragment (it isn’t a lot of
> information but hope it helps).
>
>
>
> Tue Jun  8 12:13:52 2010 [ONE][I]: Init OpenNebula Log system
>
> Tue Jun  8 12:13:52 2010 [ONE][I]: Log Level: 3
> [0=ERROR,1=WARNING,2=INFO,3=DEBUG]
>
> Tue Jun  8 12:13:52 2010 [ONE][I]:
> ----------------------------------------------
>
> Tue Jun  8 12:13:52 2010 [ONE][I]:        OpenNebula Configuration File
>
> Tue Jun  8 12:13:52 2010 [ONE][I]:
> ----------------------------------------------
>
> Tue Jun  8 12:13:52 2010 [ONE][I]:
>
> --------------------------------------------
>
>         DEBUG_LEVEL=3
>
>         HM_MAD=EXECUTABLE=one_hm
>
>         HOST_MONITORING_INTERVAL=60
>
>         IM_MAD=ARGUMENTS=--username oneadmin --password
> password,EXECUTABLE=one_im_vmware,NAME=im_vmware
>
>         MAC_PREFIX=00:03
>
>         MANAGER_TIMER=30
>
>         NETWORK_SIZE=16
>
>         PORT=2633
>
>
> TM_MAD=ARGUMENTS=tm_vmware/tm_vmware.conf,EXECUTABLE=one_tm,NAME=tm_vmware
>
>         VM_DIR=/srv/cloud/one/var
>
>         VM_MAD=ARGUMENTS=-username oneadmin --password
> password,EXECUTABLE=one_vmm_vmware,NAME=vmm_vmware,TYPE=xml
>
>         VM_POLLING_INTERVAL=60
>
> --------------------------------------------
>
> Tue Jun  8 12:13:52 2010 [VMM][I]: Starting Virtual Machine Manager...
>
> Tue Jun  8 12:13:52 2010 [LCM][I]: Starting Life-cycle Manager...
>
> Tue Jun  8 12:13:52 2010 [InM][I]: Starting Information Manager...
>
> Tue Jun  8 12:13:52 2010 [TrM][I]: Starting Transfer Manager...
>
> Tue Jun  8 12:13:52 2010 [DiM][I]: Starting Dispatch Manager...
>
> Tue Jun  8 12:13:52 2010 [ReM][I]: Starting Request Manager...
>
> Tue Jun  8 12:13:52 2010 [ReM][I]: Starting XML-RPC server, port 2633 ...
>
> Tue Jun  8 12:13:52 2010 [HKM][I]: Starting Hook Manager...
>
> Tue Jun  8 12:13:52 2010 [LCM][I]: Life-cycle Manager started.
>
> Tue Jun  8 12:13:52 2010 [InM][I]: Information Manager started.
>
> Tue Jun  8 12:13:52 2010 [TrM][I]: Transfer Manager started.
>
> Tue Jun  8 12:13:52 2010 [VMM][I]: Virtual Machine Manager started.
>
> Tue Jun  8 12:13:52 2010 [DiM][I]: Dispatch Manager started.
>
> Tue Jun  8 12:13:52 2010 [ReM][I]: Request Manager started.
>
> Tue Jun  8 12:13:52 2010 [HKM][I]: Hook Manager started.
>
> Tue Jun  8 12:13:54 2010 [VMM][I]: Loading Virtual Machine Manager drivers.
>
> Tue Jun  8 12:13:54 2010 [VMM][I]:      Loading driver: vmm_vmware (XML)
>
> Tue Jun  8 12:13:54 2010 [MAD][E]: MAD did not answer INIT command
>
> Tue Jun  8 12:13:54 2010 [InM][I]: Loading Information Manager drivers.
>
> Tue Jun  8 12:13:54 2010 [InM][I]:      Loading driver: im_vmware
>
> Tue Jun  8 12:13:55 2010 [InM][I]:      Driver im_vmware loaded
>
> Tue Jun  8 12:13:55 2010 [TM][I]: Loading Transfer Manager drivers.
>
> Tue Jun  8 12:13:55 2010 [VMM][I]:      Loading driver: tm_vmware
>
> Tue Jun  8 12:13:55 2010 [TM][I]:       Driver tm_vmware loaded.
>
> Tue Jun  8 12:13:55 2010 [HKM][I]: Loading Hook Manager driver.
>
> Tue Jun  8 12:13:55 2010 [HKM][I]:      Hook Manager loaded
>
> Tue Jun  8 12:14:22 2010 [InM][I]: Monitoring host 192.168.252.10 (7)
>
> Tue Jun  8 12:14:28 2010 [InM][E]: Error monitoring host 7 : MONITOR FAILURE
> 7 Failed monitoring host 192.168.252.10.
>
>
>
> (I had highlighted what seemed interesting to me in the log... but I have no
> idea how to fix it)
>
>
>
> I had changed password parameters here but I had revised a thousand times on
> configuration files (and every time I did it they were the right ones).
>
>
>
> Any comments or help would be very appreciated!! Thanks in advance!!
>
>
>
>
>
>
>
> Xavi Sardà Pérez
>
> ATOS ORIGIN - Research and Innovation
>
>
>
> Avda. Diagonal 200
>
> 08018 Barcelona
>
> phone: (+34) 93 506 1420
>
>
>
>
> ------------------------------------------------------------------
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive
> this e-mail in error, please notify the sender immediately and destroy it.
> As its integrity cannot be secured on the Internet, the Atos Origin
> group liability cannot be triggered for the message content. Although
> the sender endeavours to maintain a computer virus-free network,
> the sender does not warrant that this transmission is virus-free and
> will not be liable for any damages resulting from any virus transmitted.
>
> Este mensaje y los ficheros adjuntos pueden contener informacion
> confidencial
> destinada solamente a la(s) persona(s) mencionadas anteriormente
> pueden estar protegidos por secreto profesional.
> Si usted recibe este correo electronico por error, gracias por informar
> inmediatamente al remitente y destruir el mensaje.
> Al no estar asegurada la integridad de este mensaje sobre la red, Atos
> Origin
> no se hace responsable por su contenido. Su contenido no constituye ningun
> compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas
> partes.
> Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
> no puede garantizar nada al respecto y no sera responsable de cualesquiera
> danos que puedan resultar de una transmision de virus.
> ------------------------------------------------------------------
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive 
this e-mail in error, please notify the sender immediately and destroy it. 
As its integrity cannot be secured on the Internet, the Atos Origin 
group liability cannot be triggered for the message content. Although 
the sender endeavours to maintain a computer virus-free network, 
the sender does not warrant that this transmission is virus-free and 
will not be liable for any damages resulting from any virus transmitted. 

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial 
destinada solamente a la(s) persona(s) mencionadas anteriormente 
pueden estar protegidos por secreto profesional. 
Si usted recibe este correo electronico por error, gracias por informar 
inmediatamente al remitente y destruir el mensaje. 
Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin 
no se hace responsable por su contenido. Su contenido no constituye ningun 
compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. 
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor 
no puede garantizar nada al respecto y no sera responsable de cualesquiera 
danos que puedan resultar de una transmision de virus. 
------------------------------------------------------------------


More information about the Users mailing list