RSS for all categories
FS#1938 — FS#5939 — Alertes 'Host connection and power state' .
Attached to Project— Dedicated Cloud
| Incident | |
| Backend / Core | |
| CLOSED | |
 |
We have just seen several false alarms on some hosts.
An example: on some host an alarm dated at 12 h 56 h has been appeared at 14h49.
Other hosts have created an alert at 14 h 49 when there is no break.
The investigation on what could cause such problem is ongoing.
Date: Saturday, 15 October 2011, 13:53PMAn example: on some host an alarm dated at 12 h 56 h has been appeared at 14h49.
Other hosts have created an alert at 14 h 49 when there is no break.
The investigation on what could cause such problem is ongoing.
Reason for closing: Done
We have made a reboot of the vcenters.
A ticket is in progress with VMware.
VMware Support is checking the problem with our team.
Apparently the event and task tables of SQL supporting vCenter are too large. (!!!)
We're cleaning them and we will apply it for all vCenter:
60 days for events and 120 days for tasks.
No best-practice of VMware did previously defined ...
Following this false fixing of this problem, VMware support found the original problem:
http://kb.vmware.com/kb/2001504
The entity on which an alarm has been put is gone. It prevents starting the entire vCenter!
After checking each alarm manually,it seems there is one.
The service is up.
Still, there is an error 503 on the service. We will check it.
The service is up.