VirtualCenter restarts every five minutes

[dkleeman]

We have VitualCenter 2.5.0 build 119598 and it the VirtualCenter service is stopping after five minutes. It can be restarted and when running it appears to be fine.

The log ends with the following three lines which are the first errors in the log:

2009-11-04 10:42:02.045 'App' 3112 error Win32 exception: Stack overflow (0xc00000fd) 2009-11-04 10:42:02.045 'App' 3112 error eip: 0x7c343241 esp: 0x4ef3000 ebp: 0x4ef3020 2009-11-04 10:42:02.045 'App' 3112 error eax: 0x000001 ebx: 0x000001 ecx: 0x000001 edx: 0x61f55e0 edi: 00000000 esi: 0x61f55dc

We thought that the problem started when we changed our normal service user password, but this might be a red herring. We have gone through the procedure to update the password entered during installation, and we have carried out an installation repair (without resetting the database).

Any help on this problem would be much appreciated. We will be upgrading to vCenter 4.0 in due course, but this is not convenient just now.

[mlubinski]

isn't this an issue with lack of disk space on system/db partition?

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

[dkleeman]

The DB is on the C: drive which has 1.45 GB free at present.

[mlubinski]

and after this service stops, you are able to start it again, and after ~5mins it stops again with this error?

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

[dkleeman]

Yes. I now also note that in the application log I can see the VIM database restarting every ten minutes via a SQL event ID 17137.

[Dave_Mishchenko]

Do you have auto close enabled on the VC database?




Dave

VMware Communities User Moderator

New book in town - vSphere Quick Start Guide -http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/.

Do you have a system or PCI card working with VMDirectPath? Submit your specs to the Unofficial VMDirectPath HCL - http://www.vm-help.com/forum/viewforum.php?f=21.

[mlubinski]

check this out sql error

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

[dkleeman]

Yes, we have Auto Close enabled. Is there a preferred setting for this option?

[ElGogy]

Hi.

Did you sove this problem?

How?

Thanks.

[jason_farrow]

I am seeing the same thing on vSphere vCenter 4.0 update 1:

Win32 exception: Stack overflow (0xc00000fd)

eip: 0x7c4211f5 esp: 0x4943000 ebp: 0x4943008

eax: 0x494305c ebx: 0x4943058 ecx: 0x00000f edx: 00000000 edi: 0x5fcb558 esi: 0x000002

This is happening out of the blue in a very new installation. All hosts are esxi at 4.0 update 1 with all VUM applied patches.

The OS supporting vCenter is Win2003 SP1.

The crash has been occuring since this morning. Nothing indicates that changes have occured to the base platform. kb article http://kb.vmware.com/kb/1016281 is similar but is clearly not the cause here. The vCenter (running in a VM) does not have snapshots. Nor has the .vmx been modified in any way. None of the VMs managed by this vCenter have snapshots.

[jason_farrow]

Drmdump written: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs/drmdump/cluster7/12913220252693-proposeActions.dump

host-on LogHostDemand: host esx0.ad.xbas.nhs.uk cpu 264 mem 558, host esx1.ad.xbas.nhs.uk cpu 24 mem 645, host esx2.ad.xbas.nhs.uk cpu 96 mem 737, host esx3.ad.xbas.nhs.uk cpu 48 mem 660,

host-off LogHostDemand: host esx0.ad.xbas.nhs.uk cpu 246 mem 717, host esx1.ad.xbas.nhs.uk cpu 210 mem 980, host esx2.ad.xbas.nhs.uk cpu 120 mem 1053, host esx3.ad.xbas.nhs.uk cpu 48 mem 910,

LogActiveCapacity: cpu 66240 mem 173621

Power prop: stars 4, host-rec, powerOffHost esx3.ad.xbas.nhs.uk

Power prop: stars 4, host-rec, powerOffHost esx1.ad.xbas.nhs.uk

ASSERT d:/build/ob/bora-208111/bora/vpx/drm/vpxDrmAction.cpp:1158

ASSERT d:/build/ob/bora-208111/bora/vpx/drm/vpxDrmAction.cpp:1158

Exit DRS_PROFILE CallingProposeActions (32 ms)

Win32 exception: Stack overflow (0xc00000fd)

eip: 0x7c4211f5 esp: 0x49a3000 ebp: 0x49a3008

eax: 0x49a305c ebx: 0x49a3058 ecx: 0x00000f edx: 00000000 edi: 0x66fcec0 esi: 0x000003

More of the same. The time interval between crashes is not consistent. I thought that VSS, which keeps being called by vCenter, was causing the issue. When I disabled the VSS service on the vCenter VM W2k3 OS the crash appeared to have stopped. Alas, no. Just took an hour to crash.

Really puzzled by this. There are no KB or other support articles that match this.

[4men]

Hello,

we have the same problem. We have a ESX 4 U1 Cluster environment with vSphereCenter U1(Build 208111)

The error message comes since few days, and the service restart all few minutes. We only change the guest memory and cpu settings (from 2 to 4 cpus) and also more memory. The vCenter Service is running on a Windows 2008 (not R2). The Guest is running the newest VM Tools and we upgrade it since the problemexists from HW Level 4 to 7, in hope the error is because we are not in "native ESX 4 Modus (HW L 7)". We upgrade the Environment from version 3.5 U4 to ESX 4 U1, for few week's.

The Database is running local. We dosn't have any quota or other limit on the disk - so the service did not died, behavior the diskpace is on a limit.

For testing reasons we removed also the new CPU's, but not the expanded Memory.

2010-04-06 11:51:47.831 03512 info 'App' Drm Drmdump written: C:\ProgramData\VMware\VMware VirtualCenter\Logs/drmdump/cluster17/12915021107800-proposeActions.dump

2010-04-06 11:51:47.841 03512 info 'App' Drm host-on LogHostDemand: host hostnameX.domain.tpl cpu 1523 mem 2727, host hostnameX.domain.tpl cpu 1432 mem 1902, host hostnameX.domain.tpl cpu 1489 mem 4667, host hostnameX.domain.tpl cpu 923 mem 2596, host hostnameX.domain.tpl cpu 836 mem 1678,

2010-04-06 11:51:47.841 03512 info 'App' Drm host-off LogHostDemand: host hostnameX.domain.tpl cpu 2211 mem 3423, host hostname1.domain.tpl cpu 4694 mem 2353, host hostnameX.domain.tpl cpu 1699 mem 5589, host hostnameX.domain.tpl cpu 1373 mem 3047, host hostnameX.domain.tpl cpu 836 mem 2075,

2010-04-06 11:51:47.841 03512 info 'App' Drm LogActiveCapacity: cpu 116285 mem 145620

2010-04-06 11:51:47.845 03512 info 'App' Drm Power prop: stars 4, host-rec, powerOffHost hostnameX.domain.tpl

2010-04-06 11:51:47.848 03512 info 'App' Drm Power prop: stars 4, host-rec, powerOffHost hostnameX.domain.tpl

2010-04-06 11:51:47.859 03512 info 'App' Drm Power prop: stars 3, host-rec, powerOffHost hostnameX.domain.tpl

2010-04-06 11:51:47.863 03512 warning 'Libs' ASSERT d:/build/ob/bora-208111/bora/vpx/drm/vpxDrmAction.cpp:1158

2010-04-06 11:51:47.875 03512 info 'StackTracer' 3512 Exit DRS_PROFILE CallingProposeActions (77 ms)

2010-04-06 11:51:47.878 03512 error 'App' Win32 exception: Stack overflow (0xc00000fd)

2010-04-06 11:51:47.878 03512 error 'App' eip: 0x744238cf esp: 0x5b73000 ebp: 0x5b73074

2010-04-06 11:51:47.878 03512 error 'App' eax: 00000000 ebx: 0x74fe8a94 ecx: 0x5b73028 edx: 0x000035 edi: 0x5b8f5f4 esi: 0x5b73028

Any hint or solution for the problem?

At the moment we upgrade the w2k8 to w2k8 R2.

[jason_farrow]

This problem is intermittent. It can not appear for a week and then crash consistenly throughout a day. I can also kill backups with Data Recovery and this has led to at least one VM corruption.

I have a problem record open with VMware (#1506564441). There are no matching records and no obvious indicators as to cause. The support guy (Rob Moran?) has turned on extra tracing and DB debug and we wait for more crashing.

One other issue is that I am not due to be on-site at the customer for a while and have no way to check whether we have had more crashes. The customer is new to VMware and no-one else has any real experience to check the environment.

As I sit here the vCenter could be a total road-kill...