[SOLVED] VMFS Image datastore does not show capacity

Hi Guys,

I have added ESXi host to ONE and added 2 new datastore for VMFS, However the system datastore shows capacity but the image datastore does not ecause of which I am unable to import images or create a VM.

Version - 4.12
Esxi - 5.1

Host - IP - 10.10.9.3 (One and KVM hypervisor installed)
Esxi - IP - 10.10.9.1

Created nfs share on host 10.10.9.3 - location - /var/lib/one/datastores

:/var/lib/one/datastores$ ls -lh
total 34K
drwxr-xr-x 5 oneadmin oneadmin 4.0K Mar 25 07:25 0
drwxr-xr-x 4 oneadmin oneadmin 4.0K Mar 28 04:40 1
drwxrwxr-x 2 oneadmin oneadmin 2 Mar 28 09:35 107
drwxrwxr-x 2 oneadmin oneadmin 2 Mar 28 09:42 108
drwxrwxr-x 2 oneadmin oneadmin 2 Mar 9 10:17 2

NFS Share Details

/var/lib/one/datastores/107 *(rw,sync,no_subtree_check,root_squash,anonuid=1000,anongid=1000)
/var/lib/one/datastores/108 *(rw,sync,no_subtree_check,root_squash,anonuid=1000,anongid=1000)

Nfs share are mounted on Esxi Host with same Datastore Id

onedatastore list
ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM
0 system 738.1G 93% KVM Cluster 0 sys - shared
1 default 738.1G 91% KVM Cluster 11 img fs shared
2 files 279.8G 100% - 0 fil fs ssh
107 VMFS - System 279.8G 100% VMware ESXi 0 sys - vmfs
108 VMFS - Image 0M - VMware ESXi 0 img vmfs vmfs

oneadmin@storagenode01:/var/lib/one/datastores$ onehost list
ID NAME CLUSTER RVM ALLOCATED_CPU ALLOCATED_MEM STAT
2 storagenode01 KVM Clust 2 79 / 400 (19%) 4G / 11.7G (34%) on
4 10.10.9.1 VMware ES 0 0 / 400 (0%) 0K / 7.7G (0%) on

DATASTORE 108 INFORMATION

ID : 108
NAME : VMFS - Image
USER : oneadmin
GROUP : oneadmin
CLUSTER : VMware ESXi Cluster
TYPE : IMAGE
DS_MAD : vmfs
TM_MAD : vmfs
BASE PATH : /vmfs/volumes/108
DISK_TYPE : FILE

DATASTORE CAPACITY
TOTAL: : 0M
FREE: : 0M
USED: : 0M
LIMIT: : -

PERMISSIONS
OWNER : um-
GROUP : um-
OTHER : u–

DATASTORE TEMPLATE
BASE_PATH="/vmfs/volumes/"
BRIDGE_LIST=“10.10.9.1”
CLONE_TARGET=“SYSTEM”
DISK_TYPE=“FILE”
DS_MAD=“vmfs”
LN_TARGET=“NONE”
TM_MAD=“vmfs”
TYPE=“IMAGE_DS”

DATASTORE 107 INFORMATION

ID : 107
NAME : VMFS - System
USER : oneadmin
GROUP : oneadmin
CLUSTER : VMware ESXi Cluster
TYPE : SYSTEM
DS_MAD : -
TM_MAD : vmfs
BASE PATH : /vmfs/volumes/107
DISK_TYPE : FILE

DATASTORE CAPACITY
TOTAL: : 279.8G
FREE: : 279.8G
USED: : 1M
LIMIT: : -

PERMISSIONS
OWNER : um-
GROUP : u–
OTHER : —

DATASTORE TEMPLATE
BASE_PATH="/vmfs/volumes/"
SHARED=“YES”
TM_MAD=“vmfs”
TYPE=“SYSTEM_DS”

Regards
Kiran Ranjane

ONED.LOGS

Mon Mar 30 08:47:45 2015 [Z0][ReM][D]: Req:3760 UID:0 DatastorePoolInfo invoked
Mon Mar 30 08:47:45 2015 [Z0][ReM][D]: Req:3760 UID:0 DatastorePoolInfo result SUCCESS, "<DATASTORE_POOL><DAT…"
Mon Mar 30 08:47:46 2015 [Z0][AuM][D]: Message received: AUTHENTICATE SUCCESS 140 -

Mon Mar 30 08:47:46 2015 [Z0][ReM][D]: Req:7920 UID:0 DatastorePoolInfo invoked
Mon Mar 30 08:47:46 2015 [Z0][ReM][D]: Req:7920 UID:0 DatastorePoolInfo result SUCCESS, "<DATASTORE_POOL><DAT…"
Mon Mar 30 08:47:47 2015 [Z0][InM][I]: --Mark–
Mon Mar 30 08:47:56 2015 [Z0][InM][D]: Monitoring datastore default (1)
Mon Mar 30 08:47:56 2015 [Z0][InM][D]: Monitoring datastore files (2)
Mon Mar 30 08:47:56 2015 [Z0][InM][D]: Monitoring datastore VMFS - Image (108)
Mon Mar 30 08:47:57 2015 [Z0][ImM][D]: Datastore default (1) successfully monitored.
Mon Mar 30 08:47:57 2015 [Z0][ImM][D]: Datastore files (2) successfully monitored.
Mon Mar 30 08:47:59 2015 [Z0][ImM][D]: Datastore system (0) successfully monitored.
Mon Mar 30 08:47:59 2015 [Z0][ImM][D]: Datastore VMFS - System (107) successfully monitored.
Mon Mar 30 08:47:59 2015 [Z0][InM][D]: Host storagenode01 (2) successfully monitored.
Mon Mar 30 08:48:03 2015 [Z0][ImM][I]: Command execution fail: /var/lib/one/remotes/datastore/vmfs/monitor PERTX0RSSVZFUl9BQ1RJT05fREFUQT48REFUQVNUT1JFPjxJRD4xMDg8L0lEPjxVSUQ+MDwvVUlEPjxHSUQ+MDwvR0lEPjxVTkFNRT5vbmVhZG1pbjwvVU5BTUU+PEdOQU1FPm9uZWFkbWluPC9HTkFNRT48TkFNRT5WTUZTIC0gSW1hZ2U8L05BTUU+PFBFUk1JU1NJT05TPjxPV05FUl9VPjE8L09XTkVSX1U+PE9XTkVSX00+MTwvT1dORVJfTT48T1dORVJfQT4wPC9PV05FUl9BPjxHUk9VUF9VPjE8L0dST1VQX1U+PEdST1VQX00+MTwvR1JPVVBfTT48R1JPVVBfQT4wPC9HUk9VUF9BPjxPVEhFUl9VPjE8L09USEVSX1U+PE9USEVSX00+MDwvT1RIRVJfTT48T1RIRVJfQT4wPC9PVEhFUl9BPjwvUEVSTUlTU0lPTlM+PERTX01BRD48IVtDREFUQVt2bWZzXV0+PC9EU19NQUQ+PFRNX01BRD48IVtDREFUQVt2bWZzXV0+PC9UTV9NQUQ+PEJBU0VfUEFUSD48IVtDREFUQVsvdm1mcy92b2x1bWVzLzEwOF1dPjwvQkFTRV9QQVRIPjxUWVBFPjA8L1RZUEU+PERJU0tfVFlQRT4wPC9ESVNLX1RZUEU+PFNUQVRFPjA8L1NUQVRFPjxDTFVTVEVSX0lEPjEwMDwvQ0xVU1RFUl9JRD48Q0xVU1RFUj5WTXdhcmUgRVNYaSBDbHVzdGVyPC9DTFVTVEVSPjxUT1RBTF9NQj4wPC9UT1RBTF9NQj48RlJFRV9NQj4wPC9GUkVFX01CPjxVU0VEX01CPjA8L1VTRURfTUI+PElNQUdFUz48L0lNQUdFUz48VEVNUExBVEU+PEJBU0VfUEFUSD48IVtDREFUQVsvdm1mcy92b2x1bWVzL11dPjwvQkFTRV9QQVRIPjxCUklER0VfTElTVD48IVtDREFUQVsxMC4xMC45LjFdXT48L0JSSURHRV9MSVNUPjxDTE9ORV9UQVJHRVQ+PCFbQ0RBVEFbU1lTVEVNXV0+PC9DTE9ORV9UQVJHRVQ+PERJU0tfVFlQRT48IVtDREFUQVtGSUxFXV0+PC9ESVNLX1RZUEU+PERTX01BRD48IVtDREFUQVt2bWZzXV0+PC9EU19NQUQ+PExOX1RBUkdFVD48IVtDREFUQVtOT05FXV0+PC9MTl9UQVJHRVQ+PFRNX01BRD48IVtDREFUQVt2bWZzXV0+PC9UTV9NQUQ+PFRZUEU+PCFbQ0RBVEFbSU1BR0VfRFNdXT48L1RZUEU+PC9URU1QTEFURT48L0RBVEFTVE9SRT48L0RTX0RSSVZFUl9BQ1RJT05fREFUQT4= 108
Mon Mar 30 08:48:03 2015 [Z0][ImM][I]: ExitCode: 255
Mon Mar 30 08:48:03 2015 [Z0][ImM][E]: Error monitoring datastore 108: -
Mon Mar 30 08:48:07 2015 [Z0][ReM][D]: Req:8928 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Mar 30 08:48:07 2015 [Z0][ReM][D]: Req:8928 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL>119…"
Mon Mar 30 08:48:08 2015 [Z0][ReM][D]: Req:5984 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Mar 30 08:48:08 2015 [Z0][ReM][D]: Req:5984 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL>119…"
Mon Mar 30 08:48:19 2015 [Z0][ImM][D]: Datastore system (0) successfully monitored.

Regards
Kiran Ranjane

Hi,

First of all, please note that support for ESX 5.1 has been dropped in OpenNebula 4.12

Having said that, monitoring has not changed in 4.12 so it should work the same way. Could you send through the output of executing the following in the OpenNebula front-end as oneadmin?

bash -xv /var/lib/one/remotes/datastore/vmfs/monitor PERTX0RSSVZFUl9BQ1RJT05fREFUQT48REFUQVNUT1JFPjxJRD4xMDg8L0lEPjxVSUQ+MDwvVUlEPjxHSUQ+MDwvR0lEPjxVTkFNRT5vbmVhZG1pbjwvVU5BTUU+PEdOQU1FPm9uZWFkbWluPC9HTkFNRT48TkFNRT5WTUZTIC0gSW1hZ2U8L05BTUU+PFBFUk1JU1NJT05TPjxPV05FUl9VPjE8L09XTkVSX1U+PE9XTkVSX00+MTwvT1dORVJfTT48T1dORVJfQT4wPC9PV05FUl9BPjxHUk9VUF9VPjE8L0dST1VQX1U+PEdST1VQX00+MTwvR1JPVVBfTT48R1JPVVBfQT4wPC9HUk9VUF9BPjxPVEhFUl9VPjE8L09USEVSX1U+PE9USEVSX00+MDwvT1RIRVJfTT48T1RIRVJfQT4wPC9PVEhFUl9BPjwvUEVSTUlTU0lPTlM+PERTX01BRD48IVtDREFUQVt2bWZzXV0+PC9EU19NQUQ+PFRNX01BRD48IVtDREFUQVt2bWZzXV0+PC9UTV9NQUQ+PEJBU0VfUEFUSD48IVtDREFUQVsvdm1mcy92b2x1bWVzLzEwOF1dPjwvQkFTRV9QQVRIPjxUWVBFPjA8L1RZUEU+PERJU0tfVFlQRT4wPC9ESVNLX1RZUEU+PFNUQVRFPjA8L1NUQVRFPjxDTFVTVEVSX0lEPjEwMDwvQ0xVU1RFUl9JRD48Q0xVU1RFUj5WTXdhcmUgRVNYaSBDbHVzdGVyPC9DTFVTVEVSPjxUT1RBTF9NQj4wPC9UT1RBTF9NQj48RlJFRV9NQj4wPC9GUkVFX01CPjxVU0VEX01CPjA8L1VTRURfTUI+PElNQUdFUz48L0lNQUdFUz48VEVNUExBVEU+PEJBU0VfUEFUSD48IVtDREFUQVsvdm1mcy92b2x1bWVzL11dPjwvQkFTRV9QQVRIPjxCUklER0VfTElTVD48IVtDREFUQVsxMC4xMC45LjFdXT48L0JSSURHRV9MSVNUPjxDTE9ORV9UQVJHRVQ+PCFbQ0RBVEFbU1lTVEVNXV0+PC9DTE9ORV9UQVJHRVQ+PERJU0tfVFlQRT48IVtDREFUQVtGSUxFXV0+PC9ESVNLX1RZUEU+PERTX01BRD48IVtDREFUQVt2bWZzXV0+PC9EU19NQUQ+PExOX1RBUkdFVD48IVtDREFUQVtOT05FXV0+PC9MTl9UQVJHRVQ+PFRNX01BRD48IVtDREFUQVt2bWZzXV0+PC9UTV9NQUQ+PFRZUEU+PCFbQ0RBVEFbSU1BR0VfRFNdXT48L1RZUEU+PC9URU1QTEFURT48L0RBVEFTVE9SRT48L0RTX0RSSVZFUl9BQ1RJT05fREFUQT4= 108

Hi Tino,

Issue seems to be fixed, passwordless ssh was causing the issue as it was not persistent on esxi after reboot.

Now the monitoring works fine.

Regards
Kiran Ranjane

Excellent, please take into account the instructions to make ssh configuration persistent across ESXi reboots.

Hello! I have the same problem, OpenNebula 4.12.1 and ESXi 5.5, system datastore is fine bat images datastore doesn`t show space and does not allow to create any file.

ssh persistence access is working (I had to modify /etc/rc.local.d/local.sh instead /etc/rc.local).

Can you help me?

Thank you

Hello! I have the same problem, OpenNebula 4.12.1
and ESXi 5.5, system datastore is fine bat images datastore doesn`t
show space and does not allow to create any file.

ssh persistence access is working (I had to modify /etc/rc.local.d/local.sh instead /etc/rc.local).

Can you help me?

Thank you

I have the exact same probelem using ene4.10 and esxi 5.0. Any solution?
Best regards.

I suspect that may be some problem with the VMFS DS driver.
I’m trying to access a NFS shared datastore trough the ESXi Host. These Datastore are accessible by the Host, but the ONE front end can’t monitor the IMAGE_DS datastore. The Bridge_list is correct. The persistent passwordless SSH connection either.
Basically I follow this installation guide.

When I change the DS_TYPE to SYSTEM_DS the ONE front-end monitor the datastore normally.

Can anybody help me?

Thank you.

=====================================
Datastore information:

[oneadmin@localhost ~]$ onedatastore list
ID NAME                SIZE AVAIL     CLUSTER      IMAGES TYPE DS       TM
0 system                8.5G 80%      -                 0 sys  -        vmfs
1 default                 0M -        -                 0 img  vmfs     vmfs
2 files                 8.5G 79%      -                 0 fil  fs       ssh
103 imagens             8.5G 79%      -                 1 img  fs       ssh

DATASTORE 1 INFORMATION

ID : 1
NAME : default
USER : oneadmin
GROUP : oneadmin
CLUSTER : -
TYPE : IMAGE
DS_MAD : vmfs
TM_MAD : vmfs
BASE PATH : /vmfs/volumes/1
DISK_TYPE : FILE

DATASTORE CAPACITY
TOTAL: : 0M
FREE: : 0M
USED: : 0M
LIMIT: : -

PERMISSIONS
OWNER : um-
GROUP : u–
OTHER : u–

DATASTORE TEMPLATE
BASE_PATH="/vmfs/volumes/"
BRIDGE_LIST="10.235.2.225"
CLONE_TARGET="SYSTEM"
DISK_TYPE="FILE"
DS_MAD="vmfs"
LN_TARGET="NONE"
TM_MAD="vmfs"
TYPE=“IMAGE_DS”

DATASTORE 0 INFORMATION

ID : 0
NAME : system
USER : oneadmin
GROUP : oneadmin
CLUSTER : -
TYPE : SYSTEM
DS_MAD : -
TM_MAD : vmfs
BASE PATH : /vmfs/volumes/0
DISK_TYPE : FILE

DATASTORE CAPACITY
TOTAL: : 8.5G
FREE: : 6.8G
USED: : 1.7G
LIMIT: : -

PERMISSIONS
OWNER : um-
GROUP : u–
OTHER : —

DATASTORE TEMPLATE
BASE_PATH="/vmfs/volumes/"
SHARED="YES"
TM_MAD="vmfs"
TYPE=“SYSTEM_DS”

DATASTORE 103 INFORMATION

ID : 103
NAME : imagens
USER : oneadmin
GROUP : oneadmin
CLUSTER : -
TYPE : IMAGE
DS_MAD : fs
TM_MAD : ssh
BASE PATH : /var/lib/one/datastores/103/103
DISK_TYPE : FILE

DATASTORE CAPACITY
TOTAL: : 8.5G
FREE: : 6.7G
USED: : 103M
LIMIT: : -

PERMISSIONS
OWNER : um-
GROUP : u–
OTHER : u–

DATASTORE TEMPLATE
BASE_PATH="/var/lib/one/datastores/103/"
BRIDGE_LIST="10.235.2.227"
CLONE_TARGET="SYSTEM"
DISK_TYPE="FILE"
DS_MAD="fs"
LN_TARGET="SYSTEM"
TM_MAD="ssh"
TYPE=“IMAGE_DS”

ONED.LOG

Tue Oct 18 23:20:01 2016 [Z0][ONE][I]: Starting OpenNebula 4.10.2

 OpenNebula Configuration File      

AUTH_MAD=AUTHN=ssh,x509,ldap,server_cipher,server_x509,EXECUTABLE=one_auth_mad
DATASTORE_BASE_PATH=/vmfs/volumes
DATASTORE_CAPACITY_CHECK=yes
DATASTORE_LOCATION=/vmfs/volumes
DATASTORE_MAD=ARGUMENTS=-t 15 -d dummy,fs,vmfs,lvm,ceph,dev,EXECUTABLE=one_datastore
DB=BACKEND=sqlite
DEFAULT_CDROM_DEVICE_PREFIX=sd
DEFAULT_DEVICE_PREFIX=sd
DEFAULT_IMAGE_TYPE=OS
DEFAULT_UMASK=177
ENABLE_OTHER_PERMISSIONS=YES
FEDERATION=MASTER_ONED=,MODE=STANDALONE,ZONE_ID=0
HM_MAD=EXECUTABLE=one_hm
HOST_MONITORING_EXPIRATION_TIME=43200
HOST_PER_INTERVAL=15
IMAGE_RESTRICTED_ATTR=SOURCE
IM_MAD=ARGUMENTS=-p 4124 -f 5 -t 50 -i 20,EXECUTABLE=collectd,NAME=collectd
IM_MAD=ARGUMENTS=-r 3 -t 15 kvm,EXECUTABLE=one_im_ssh,NAME=kvm
IM_MAD=ARGUMENTS=-r 3 -t 15 xen4,EXECUTABLE=one_im_ssh,NAME=xen
IM_MAD=ARGUMENTS=-c -t 15 -r 0 vmware,EXECUTABLE=one_im_sh,NAME=vmware
INHERIT_DATASTORE_ATTR=CEPH_HOST
INHERIT_DATASTORE_ATTR=CEPH_SECRET
INHERIT_DATASTORE_ATTR=CEPH_USER
INHERIT_DATASTORE_ATTR=GLUSTER_HOST
INHERIT_DATASTORE_ATTR=GLUSTER_VOLUME
INHERIT_VNET_ATTR=VLAN_TAGGED_ID
INHERIT_VNET_ATTR=BRIDGE_OVS
KEEPALIVE_MAX_CONN=30
KEEPALIVE_TIMEOUT=15
LOG=DEBUG_LEVEL=3,SYSTEM=file
LOG_CALL_FORMAT=Req:%i UID:%u %m invoked %l
MAC_PREFIX=02:00
MANAGER_TIMER=15
MAX_CONN=15
MAX_CONN_BACKLOG=15
MESSAGE_SIZE=1073741824
MONITORING_INTERVAL=60
MONITORING_THREADS=50
NETWORK_SIZE=254
PORT=2633
RPC_LOG=NO
SCRIPTS_REMOTE_DIR=/var/tmp/one
SESSION_EXPIRATION_TIME=900
TIMEOUT=15
TM_MAD=ARGUMENTS=-t 15 -d dummy,lvm,shared,fs_lvm,qcow2,ssh,vmfs,ceph,dev,EXECUTABLE=one_tm
TM_MAD_CONF=CLONE_TARGET=SYSTEM,LN_TARGET=NONE,NAME=dummy,SHARED=yes
TM_MAD_CONF=CLONE_TARGET=SELF,LN_TARGET=NONE,NAME=lvm,SHARED=yes
TM_MAD_CONF=CLONE_TARGET=SYSTEM,LN_TARGET=NONE,NAME=shared,SHARED=yes
TM_MAD_CONF=CLONE_TARGET=SYSTEM,LN_TARGET=SYSTEM,NAME=fs_lvm,SHARED=yes
TM_MAD_CONF=CLONE_TARGET=SYSTEM,LN_TARGET=NONE,NAME=qcow2,SHARED=yes
TM_MAD_CONF=CLONE_TARGET=SYSTEM,LN_TARGET=SYSTEM,NAME=ssh,SHARED=no
TM_MAD_CONF=CLONE_TARGET=SYSTEM,LN_TARGET=NONE,NAME=vmfs,SHARED=yes
TM_MAD_CONF=CLONE_TARGET=SELF,LN_TARGET=NONE,NAME=ceph,SHARED=yes
TM_MAD_CONF=CLONE_TARGET=NONE,LN_TARGET=NONE,NAME=dev,SHARED=yes
VM_INDIVIDUAL_MONITORING=no
VM_MAD=ARGUMENTS=-t 15 -r 0 kvm,DEFAULT=vmm_exec/vmm_exec_kvm.conf,EXECUTABLE=one_vmm_exec,NAME=kvm,TYPE=kvm
VM_MAD=ARGUMENTS=-t 15 -r 0 xen4,DEFAULT=vmm_exec/vmm_exec_xen4.conf,EXECUTABLE=one_vmm_exec,NAME=xen,TYPE=xen
VM_MAD=ARGUMENTS=-t 15 -r 0 vmware -s sh,DEFAULT=vmm_exec/vmm_exec_vmware.conf,EXECUTABLE=one_vmm_sh,NAME=vmware,TYPE=vmware
VM_MONITORING_EXPIRATION_TIME=14400
VM_PER_INTERVAL=5
VM_RESTRICTED_ATTR=CONTEXT/FILES
VM_RESTRICTED_ATTR=NIC/MAC
VM_RESTRICTED_ATTR=NIC/VLAN_ID
VM_RESTRICTED_ATTR=NIC/BRIDGE
VM_RESTRICTED_ATTR=NIC_DEFAULT/MAC
VM_RESTRICTED_ATTR=NIC_DEFAULT/VLAN_ID
VM_RESTRICTED_ATTR=NIC_DEFAULT/BRIDGE
VM_RESTRICTED_ATTR=DISK/TOTAL_BYTES_SEC
VM_RESTRICTED_ATTR=DISK/READ_BYTES_SEC
VM_RESTRICTED_ATTR=DISK/WRITE_BYTES_SEC
VM_RESTRICTED_ATTR=DISK/TOTAL_IOPS_SEC
VM_RESTRICTED_ATTR=DISK/READ_IOPS_SEC
VM_RESTRICTED_ATTR=DISK/WRITE_IOPS_SEC
VM_SUBMIT_ON_HOLD=NO
VNC_BASE_PORT=5900
VNET_RESTRICTED_ATTR=PHYDEV
VNET_RESTRICTED_ATTR=VLAN_ID
VNET_RESTRICTED_ATTR=VLAN
VNET_RESTRICTED_ATTR=BRIDGE
VNET_RESTRICTED_ATTR=AR/PHYDEV
VNET_RESTRICTED_ATTR=AR/VLAN_ID
VNET_RESTRICTED_ATTR=AR/VLAN
VNET_RESTRICTED_ATTR=AR/BRIDGE

Tue Oct 18 23:20:01 2016 [Z0][ONE][I]: Log level:3 [0=ERROR,1=WARNING,2=INFO,3=DEBUG]
Tue Oct 18 23:20:01 2016 [Z0][ONE][I]: Support for xmlrpc-c > 1.31: yes
Tue Oct 18 23:20:01 2016 [Z0][ONE][I]: Checking database version.
Tue Oct 18 23:20:01 2016 [Z0][ONE][I]: oned is using version 4.9.80 for local_db_versioning
Tue Oct 18 23:20:01 2016 [Z0][ONE][I]: oned is using version 4.6.0 for db_versioning
Tue Oct 18 23:20:01 2016 [Z0][ACL][I]: Starting ACL Manager…
Tue Oct 18 23:20:01 2016 [Z0][ACL][I]: ACL Manager started.
Tue Oct 18 23:20:01 2016 [Z0][VMM][I]: Starting Virtual Machine Manager…
Tue Oct 18 23:20:01 2016 [Z0][LCM][I]: Starting Life-cycle Manager…
Tue Oct 18 23:20:01 2016 [Z0][InM][I]: Starting Information Manager…
Tue Oct 18 23:20:01 2016 [Z0][TrM][I]: Starting Transfer Manager…
Tue Oct 18 23:20:01 2016 [Z0][DiM][I]: Starting Dispatch Manager…
Tue Oct 18 23:20:01 2016 [Z0][HKM][I]: Starting Hook Manager…
Tue Oct 18 23:20:01 2016 [Z0][AuM][I]: Starting Auth Manager…
Tue Oct 18 23:20:01 2016 [Z0][ImM][I]: Starting Image Manager…
Tue Oct 18 23:20:02 2016 [Z0][AuM][I]: Authorization Manager started.
Tue Oct 18 23:20:02 2016 [Z0][ImM][I]: Image Manager started.
Tue Oct 18 23:20:02 2016 [Z0][InM][I]: Information Manager started.
Tue Oct 18 23:20:02 2016 [Z0][VMM][I]: Virtual Machine Manager started.
Tue Oct 18 23:20:02 2016 [Z0][TrM][I]: Transfer Manager started.
Tue Oct 18 23:20:02 2016 [Z0][DiM][I]: Dispatch Manager started.
Tue Oct 18 23:20:02 2016 [Z0][LCM][I]: Life-cycle Manager started.
Tue Oct 18 23:20:02 2016 [Z0][HKM][I]: Hook Manager started.
Tue Oct 18 23:20:02 2016 [Z0][VMM][I]: Loading Virtual Machine Manager drivers.
Tue Oct 18 23:20:02 2016 [Z0][VMM][I]: Loading driver: kvm (KVM)
Tue Oct 18 23:20:03 2016 [Z0][VMM][I]: Driver kvm loaded.
Tue Oct 18 23:20:03 2016 [Z0][VMM][I]: Loading driver: xen (XEN)
Tue Oct 18 23:20:03 2016 [Z0][VMM][I]: Driver xen loaded.
Tue Oct 18 23:20:03 2016 [Z0][VMM][I]: Loading driver: vmware (VMWARE)
Tue Oct 18 23:20:03 2016 [Z0][VMM][I]: Driver vmware loaded.
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Loading Information Manager drivers.
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Loading driver: collectd
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Driver collectd loaded
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Loading driver: kvm
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Driver kvm loaded
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Loading driver: xen
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Driver xen loaded
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Loading driver: vmware
Tue Oct 18 23:20:03 2016 [Z0][InM][I]: Driver vmware loaded
Tue Oct 18 23:20:03 2016 [Z0][TM][I]: Loading Transfer Manager driver.
Tue Oct 18 23:20:03 2016 [Z0][TM][I]: Transfer manager driver loaded
Tue Oct 18 23:20:03 2016 [Z0][HKM][I]: Loading Hook Manager driver.
Tue Oct 18 23:20:04 2016 [Z0][HKM][I]: Hook Manager loaded
Tue Oct 18 23:20:04 2016 [Z0][ImM][I]: Loading Image Manager driver.
Tue Oct 18 23:20:04 2016 [Z0][ImM][I]: Image Manager loaded
Tue Oct 18 23:20:04 2016 [Z0][AuM][I]: Loading Auth. Manager driver.
Tue Oct 18 23:20:04 2016 [Z0][AuM][I]: Auth Manager loaded
Tue Oct 18 23:20:04 2016 [Z0][ReM][I]: Starting Request Manager…
Tue Oct 18 23:20:04 2016 [Z0][ReM][I]: Starting XML-RPC server, port 2633 …
Tue Oct 18 23:20:04 2016 [Z0][ReM][I]: Request Manager started.
Tue Oct 18 23:20:06 2016 [Z0][ReM][D]: Req:4032 UID:0 SystemConfig invoked
Tue Oct 18 23:20:06 2016 [Z0][ReM][D]: Req:4032 UID:0 SystemConfig result SUCCESS, "<AUTH_MAD>…"
Tue Oct 18 23:20:16 2016 [Z0][InM][D]: Monitoring datastore default (1)
Tue Oct 18 23:20:17 2016 [Z0][InM][D]: Monitoring datastore files (2)
Tue Oct 18 23:20:17 2016 [Z0][InM][D]: Monitoring datastore imagens (103)
Tue Oct 18 23:20:17 2016 [Z0][ImM][D]: Datastore imagens (103) successfully monitored.
Tue Oct 18 23:20:17 2016 [Z0][ImM][D]: Datastore files (2) successfully monitored.
Tue Oct 18 23:20:17 2016 [Z0][ImM][D]: Datastore default (1) successfully monitored.
Tue Oct 18 23:20:32 2016 [Z0][InM][D]: Monitoring host 10.235.2.225 (0)
Tue Oct 18 23:20:34 2016 [Z0][ImM][D]: Datastore system (0) successfully monitored.
Tue Oct 18 23:20:34 2016 [Z0][InM][D]: Host 10.235.2.225 (0) successfully monitored.
Tue Oct 18 23:20:35 2016 [Z0][ReM][D]: Req:9136 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Tue Oct 18 23:20:35 2016 [Z0][ReM][D]: Req:9136 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL></VM_POOL>"
Tue Oct 18 23:20:36 2016 [Z0][ReM][D]: Req:1152 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Tue Oct 18 23:20:36 2016 [Z0][ReM][D]: Req:1152 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL></VM_POOL>"
Tue Oct 18 23:21:06 2016 [Z0][ReM][D]: Req:5040 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Tue Oct 18 23:21:06 2016 [Z0][ReM][D]: Req:5040 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL></VM_POOL>"
Tue Oct 18 23:21:06 2016 [Z0][ReM][D]: Req:3168 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Tue Oct 18 23:21:06 2016 [Z0][ReM][D]: Req:3168 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL></VM_POOL>"
Tue Oct 18 23:21:13 2016 [Z0][InM][D]: Monitoring datastore default (1)
Tue Oct 18 23:21:13 2016 [Z0][InM][D]: Monitoring datastore files (2)
Tue Oct 18 23:21:13 2016 [Z0][InM][D]: Monitoring datastore imagens (103)
Tue Oct 18 23:21:14 2016 [Z0][ImM][D]: Datastore files (2) successfully monitored.
Tue Oct 18 23:21:14 2016 [Z0][ImM][D]: Datastore imagens (103) successfully monitored.
Tue Oct 18 23:21:14 2016 [Z0][ImM][D]: Datastore default (1) successfully monitored.
Tue Oct 18 23:21:36 2016 [Z0][ReM][D]: Req:8960 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Tue Oct 18 23:21:36 2016 [Z0][ReM][D]: Req:8960 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL></VM_POOL>"
Tue Oct 18 23:21:36 2016 [Z0][ReM][D]: Req:1136 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Tue Oct 18 23:21:36 2016 [Z0][ReM][D]: Req:1136 UID:0 VirtualMachinePoolInfo result SUCCESS, “<VM_POOL></VM_POOL>”

Solved. The problem was with the outdated ESXi 5.0- Build 474610. Somehow every time I log in with the oneadmin user via SSH the ESXI don’t grant me the root privilege, even with the user oneadmin being in the root group and with administrator role activated. Thus the df command could not be executed and the monitor.py script couldn’t determine the datastore space.

After the update to ESXi 5.0 build 3982828 Release 2016-06-14 this problem was solved. But 'til that a lot of headache.