VMware Cloud Community
usa_kwilliamson
Enthusiast
Enthusiast
‎09-10-2013 01:18 PM

VirtCenter 5.1 Shutdown on its own.

I have vCenter service stop running on my vCenter Server that is running view 5.1, and it has happened twice while recomposing a pool.  I don't think the two events are related.  I'm running vCenter Server 5.1 Build 880146.  The error messages I'm seeing are.

2013-09-07T23:18:32.152-05:00 [05384 error 'Default'
opID=task-internal-1-aa971c79-ab] [VdbStatement::Fetch] SQLError was thrown:
"ODBC error: (40001) - [Microsoft][SQL Server Native Client 10.0][SQL
Server]Transaction (Process ID 65) was deadlocked on lock resources with
another process and has been chosen as the deadlock victim. Rerun the
transaction." is returned when executing SQL statement "SELECT
HOST_ID            FROM VPX_VM,
VPX_VDEVICE_FILE_BACKING            WHERE
VPX_VM.ID = VPX_VDEVICE_FILE_BACKING.VM_ID            AND
VPX_VDEVICE_FILE_BACKING.HARD_DEVICE_BACKING_FILE_NAME = ?"

2013-09-07T23:18:32.152-05:00 [08160 warning 'Default']
[VdbStatement] SQL execution took too long: delete from VPX_VIRTUAL_DEVICE with
(rowlock) where ID = 3801 and DEVICE_KEY = 2000

2013-09-07T23:18:32.152-05:00 [08160 warning 'Default']
[VdbStatement] Execution elapsed time: 4165 ms

2013-09-07T23:18:32.152-05:00 [08160 warning 'Default']
[VdbStatement] Bind parameters:

 

2013-09-07T23:18:32.168-05:00 [05384 warning 'VmCheck'
opID=task-internal-1-aa971c79-ab] ComputeCompatibility [VmState constructor
which takes an existing vm] took 4181 ms

 

2013-09-07T23:18:32.168-05:00 [05384 warning 'VmCheck'
opID=task-internal-1-aa971c79-ab] ComputeCompatibility [ConstructVmStates] took
4181 ms

 

2013-09-07T23:18:32.168-05:00 [05384 warning 'VmCheck'
opID=task-internal-1-aa971c79-ab] ComputeCompatibility
[MoVmCompatChecker::CheckPowerOnInt] took 4181 ms

2013-09-07T23:18:32.168-05:00 [05384 warning 'VpxProfiler'
opID=task-internal-1-aa971c79-ab] Time taken for cluster region
[CheckClusterCompatibilityInt] took 4181 ms

2013-09-07T23:18:32.168-05:00 [05384 warning 'VpxProfiler'
opID=task-internal-1-aa971c79-ab] Time taken for cluster region
[ComputeCompatibilitySetInt] took 4181 ms

2013-09-07T23:18:32.168-05:00 [05384 warning 'VpxProfiler'
opID=task-internal-1-aa971c79-ab] Time taken for cluster region
[ClusterComputeCompatibilitySet] took 4399 ms

 

2013-09-07T23:18:32.168-05:00 [05384 warning
'VpxProfiler' opID=task-internal-1-aa971c79-ab] Time taken for DRS region
[AskAndRefreshDrmRecommendations] took 4399 ms

I'm not seeing any warnings on the MS SQL 2008 R2 server, unless I'm looking at the wrong place.

Any suggestions on what the issue is or better logs to help find the issue?

Tags (1)
Reply
0 Kudos
1 Reply
usa_kwilliamson
Enthusiast
Enthusiast
‎09-11-2013 06:43 AM

I found this link http://blog.mmars.org/2013/02/vcenter-service-dies-sql-to-blame.html.

It was recommending to change several database properties.

ALTER DATABASE <VCDB> SET ALLOW_SNAPSHOT_ISOLATION ON;

GO

ALTER DATABASE <VCDB> SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
ALTER DATABASE <VCDB> SET READ_COMMITTED_SNAPSHOT ON;
ALTER DATABASE <VCDB> SET MULTI_USER;

Would I need to restart the vcenter service or reboot virtcenter or something else for this to take into effect?

Reply
0 Kudos