vCenter Server service does not shutdown when database connectivity is lost

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• vCenter Server service does not shutdown when database connectivity is lost
• You see these errors in the vCenter Server logs:
• Vdb::Connection::TestConnection SQLExecute failed: 08S01:233
• [Vdb::GetConnection] Failed to obtain connection: 08001:2
• [Vdb] Failed to obtain database connection. Retrying..

Environment

VMware vCenter Server 5.1.x
VMware vCenter Server 5.5.x
VMware vCenter Server 5.0.x
VMware vCenter Server 4.1.x

Cause

As of vCenter Server 4.1, when connectivity is lost, the service tries to reconnect to the database (rather than shutting down)until the maximum database downtime is exceeded.

Resolution

The maximum database downtime is a configurable parameter that defaults to 1800 seconds (30 minutes). Modifying the parameter to a shorter value (such as 10 seconds) forces vCenter Server service to shut down sooner when it loses database connectivity.

To modify the database downtime parameter to 10 seconds:

1. Log in to vCenter Server as an administrative user.
2. Open the vCenter Server configuration file (vpxd.cfg) in a text editor.
3. Add this parameter:
   
   <config>
   ...
   <vpxd>
   <odbc>
   <maxDatabaseDowntime>10</maxDatabaseDowntime>
   </odbc>
   ...
   </vpxd>
   </config>
   
   
   Notes:
   • Specify the value in seconds. You can choose any value.
   • If you want vCenter Server to shut down immediately when it loses database connectivity, set the database downtime parameter to 0. For example, <maxDatabaseDowntime>0</maxDatabaseDowntime>
     
     
4. Save and close the file.
5. Restart the VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Additional Information

How to stop, start, or restart vCenter Server services
vCenter Server サービスが、データベース接続を失った場合に、シャットダウンしない