[one-users] OpenNebula 4.4 Problem with VMWARE ESX The state of "onehost list" always is "RETRY"

2014-01-05 Thread ska...@system01.net
I am doing a Testdrive installing OpenNebula 4.4 and added the first VMWARE ESX Server. The state of onehost list is always "RETRY".

In oned.log VM's and Datastores are successfully scanned (VM's , Datastore ,etc) but there was one error message: Fri Jan  3 20:24:15 2014 [ONE][E]: Error parsing host information: syntax error, unexpected VARIABLE, expecting COMMA or CBRACKET at line 14, columns 338:339. Monitoring information:
�MODELNAME="Intel(R) Xeon(TM) CPU 3.20G�

..

 

How to troubleshoot this ??? I removed the Server , added it again, always the same problem. In Sunstone no Server, Network and Datastore showing up. 

Please help!

 

regards

 

Sven

 
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org


Re: [one-users] how to configure the vms High Availability?

2014-01-05 Thread hansz
Hi,
i use opennebula4.2 install on centos6.4 and has two esxi 
hypervisor.(10.24.101.72  and 10.24.101.73)
i have change my front-end's oned.conf like
HOST_HOOK = [
name  = "error",
on= "ERROR",
command   = "ft/host_error.rb",
arguments = "$ID -r",
remote= "no" ]


VM_HOOK = [
   name  = "on_failure_recreate",
   on= "UNKNOWN",
   command   = "/usr/bin/env onevm delete --recreate",
   arguments = "$ID" ]


then i create one vm  on 10.24.101.73 , after the vm running, i power off the 
10.24.101.73,but the vm dose not migrate to 10.24.101.72
i also create one cluser one the sunstone which include the two esxis.
the vm log 


Sun Jan 5 13:54:53 2014 [DiM][I]: New VM state is ACTIVE.
Sun Jan 5 13:54:53 2014 [LCM][I]: New VM state is PROLOG.
Sun Jan 5 13:55:05 2014 [LCM][I]: New VM state is BOOT
Sun Jan 5 13:55:05 2014 [VMM][I]: Generating deployment file: 
/var/lib/one/vms/9/deployment.0
Sun Jan 5 13:55:05 2014 [VMM][I]: Successfully execute network driver 
operation: pre.
Sun Jan 5 13:55:21 2014 [VMM][I]: Successfully execute virtualization driver 
operation: deploy.
Sun Jan 5 13:55:21 2014 [VMM][I]: Successfully execute network driver 
operation: post.
Sun Jan 5 13:55:21 2014 [LCM][I]: New VM state is RUNNING
Sun Jan 5 13:58:03 2014 [LCM][I]: New VM state is UNKNOWN
Sun Jan 5 13:58:03 2014 [LCM][I]: New VM state is CLEANUP.
Sun Jan 5 13:58:03 2014 [VMM][I]: Driver command for 9 cancelled
Sun Jan 5 13:58:03 2014 [DiM][I]: New VM state is PENDING
Sun Jan 5 13:58:03 2014 [HKM][I]: Success executing Hook: on_failure_recreate: 
. 
Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 Command execution fail: 
/var/lib/one/remotes/vmm/vmware/cancel 'one-9' '10.24.101.73' 9 10.24.101.73


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG E 9 cancel: Error executing: 
virsh -c 'esx://10.24.101.73/?no_verify=1&auto_answer=1' destroy one-9 err: 
ExitCode: 1


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 out:


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 error: internal error HTTP 
response code 503 for call to 'RetrieveServiceContent'


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 error: failed to connect to 
the hypervisor


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 ExitCode: 1


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 Failed to execute 
virtualization driver operation: cancel.


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 Successfully execute network 
driver operation: clean.


Sun Jan 5 13:58:06 2014 [VMM][W]: Ignored: LOG I 9 Successfully execute 
transfer manager driver operation: tm_delete.


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 Command execution fail: 
/var/lib/one/remotes/tm/vmfs/delete 10.24.101.73:/vmfs/volumes/100/9 9 100


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG E 9 delete: Command "rm -rf 
/vmfs/volumes/100/9" failed: rm: can't remove 
'/vmfs/volumes/100/9/disk.0/disk-flat.vmdk': Device or resource busy


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 rm: can't remove 
'/vmfs/volumes/100/9/disk.0/vmx-one-9-2219911413-1.vswp': Device or resource 
busy


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 rm: can't remove 
'/vmfs/volumes/100/9/disk.0/one-9.vmx.lck': Device or resource busy


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 rm: can't remove 
'/vmfs/volumes/100/9/disk.0/one-9-845128f5.vswp': Device or resource busy


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 rm: can't remove 
'/vmfs/volumes/100/9/disk.0': Directory not empty


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 rm: can't remove 
'/vmfs/volumes/100/9/disk.1': Device or resource busy


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 rm: can't remove 
'/vmfs/volumes/100/9': Directory not empty


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG E 9 Error deleting 
/vmfs/volumes/100/9


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 ExitCode: 1


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: LOG I 9 Failed to execute transfer 
manager driver operation: tm_delete.


Sun Jan 5 13:58:07 2014 [VMM][W]: Ignored: CLEANUP SUCCESS 9 












___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org