Hi Javier,
Even though I updated to 4.4 after the problem appeared, it looks like
'onehost sync' has solved the issue.
Thank you,
Javier
On 20/01/14 12:25, Javier Fontan wrote:
Have you upgraded to 4.4 from an older version? In previous versions
system datastores are not monitored and old p
Have you upgraded to 4.4 from an older version? In previous versions
system datastores are not monitored and old probes do not get that
information. In this case execute:
$ onehost sync
It should copy the new ones to the hosts.
On Mon, Jan 20, 2014 at 12:09 PM, Javier wrote:
> Hi Ruben,
>
> Tha
Hi Ruben,
Thank you for your reply. Here it is what I found out:
1- I had a cluster defined but I deleted it, so right now I don't have any.
2- The only host I have at the moment is correctly monitored. And the
output of monitor_ds.sh is correctly showing info about the datastore (I
cannot ru
Hi Javier,
A couple of ideas:
1.- System DS needs to be associated to a cluster. Sometimes this may cause
problems if a host is in a cluster but the cluster hasn't got any system
DS. (This seems not to be your problem, but just double checking)
2.- System DS information is gathered through the m
Hello,
After a reboot my VMs started getting stuck in PENDING state. Watching
at the log files I noticed that the problem was that the system
datastore was not being correctly monitored:
onedatastore list
ID NAMESIZE AVAIL CLUSTER IMAGES TYPE DS TM
0 system
