Defining alarms on datastore folders can cause vCenter Server 4.x to becomes unresponsive

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Defining alarms (for example, to monitor storage space or overallocation) on datastore folders can cause vCenter Server to become unresponsive
• Defining alarms causes a deadlock issue, which causes vCenter Server to become unresponsive

vcenter-alarms vcenter-unresponsive restart-services vcenter-server-service-fails

Environment

VMware vCenter Server 4.1.x
VMware vCenter Server 4.0.x

Resolution

VMware is aware of this issue and is working to resolve it in a future release of VMware vCenter Server.

Restarting the VirtualCenter Server service temporarily resolves this issue. For more information, see Stopping, starting, or restarting vCenter services (1003895).

To avoid this issue, do not define alarms on datastore folders. Only define alarms on Datacenter or datacenter folders.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box