vCenter on Windows keeps crashing

sergeNZ · ‎11-30-2011

Hi,

We're running vCenter 4.1.0 and are experiencing issues when the vCenter daemon (vpxd) crashes with a "Win32 invalid_parameter error" and I can't seem to figure out why. From the vpxd.log we can see the following output when vCenter crashes:

[2011-12-01 14:53:51.819 06804 warning 'App' opID=85a8b277] Resource config mirror for VM VMTEST-win64 is NULL
[2011-12-01 14:53:51.822 06804 info 'App' opID=85a8b277] [Drm] Drmdump written: C:\ProgramData\VMware\VMware VirtualCenter\Logs/drmdump/cluster74039/12967178031821-mapVm.dump
[2011-12-01 14:53:51.851 06804 warning 'Libs' opID=85a8b277] ASSERT d:/build/ob/bora-345043/bora/vpx/vpxd/vpxdMoSnapshot.cpp:312
[2011-12-01 14:53:51.851 06804 error 'App' opID=85a8b277] Win32 invalid_parameter: expression=(null), function=(null), file=(null), line=0
[2011-12-01 14:54:53.001 06804 info 'App' opID=85a8b277] CoreDump: Writing minidump
[2011-12-01 14:55:32.515 06804 panic 'App' opID=85a8b277]

Panic: Win32 invalid_parameter error
Backtrace:
backtrace[00] rip 000000018010a8aa Vmacore::System::Stacktrace::CaptureWork
backtrace[01] rip 00000001800e8008 Vmacore::System::SystemFactoryImpl::CreateFileWriter
backtrace[02] rip 00000001800e84fe Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace
backtrace[03] rip 0000000180129ba5 Vmacore::PanicExit
backtrace[04] rip 0000000180129cb1 Vmacore::PanicExit
backtrace[05] rip 000000018011ab14 Vmacore::System::GetThisThread
backtrace[06] rip 00000000728b52ad invalid_parameter
backtrace[07] rip 00000000728b5309 invalid_parameter_noinfo
backtrace[08] rip 00000001400aa9b1 (no symbol)
backtrace[09] rip 00000001400ac567 (no symbol)
backtrace[10] rip 00000001400aca35 (no symbol)
backtrace[11] rip 0000000000a103c3 Vim::Vm::ScsiPassthroughInfo::_GetDataType
backtrace[12] rip 00000000003b8dc0 Vmomi::RuntimeFault::_GetDataType
backtrace[13] rip 000000014094cf6f (no symbol)
backtrace[14] rip 000000014092a672 (no symbol)
backtrace[15] rip 0000000140930a08 (no symbol)
backtrace[16] rip 000000018011f68d Vmacore::System::IsEnlisted
backtrace[17] rip 0000000180120a6f Vmacore::System::IsEnlisted
backtrace[18] rip 0000000180119df5 Vmacore::System::ThisThreadExists
backtrace[19] rip 0000000072862fdf endthreadex
backtrace[20] rip 0000000072863080 endthreadex
backtrace[21] rip 00000000771bf56d BaseThreadInitThunk
backtrace[22] rip 00000000772f2cc1 RtlUserThreadStart

[2011-12-01 14:55:32.517 06804 panic 'App' opID=85a8b277] Win32 invalid_parameter error
------ In-memory logs start --------

and then 5 minutes later it crashes again:

[2011-12-01 14:53:51.819 06804 verbose 'App' opID=85a8b277] [VpxdMoVm::GetMemoryOverheadInt] Use runtime overhead (188) from host vim.HostSystem:host-74339

[2011-12-01 14:53:51.819 06804 verbose 'App' opID=85a8b277] [VpxdDrmInterface::VpxDrmRetrieveVmInfo] Set overheadMB to 188 for VM VMTEST-win64

[2011-12-01 14:53:51.821 06804 verbose 'VpxProfiler' opID=85a8b277] [3-] DRS_PROFILE RetrieveInitialPlacement (took 445 ms)

[2011-12-01 14:53:51.821 06804 verbose 'VpxProfiler' opID=85a8b277] [3+] DRS_PROFILE GetPlaceForVm

[2011-12-01 14:53:51.821 06804 verbose 'VpxProfiler' opID=85a8b277] [4+] DRS_PROFILE CallingMapVm

[2011-12-01 14:53:51.822 06804 info 'App' opID=85a8b277] [Drm] Drmdump written: C:\ProgramData\VMware\VMware VirtualCenter\Logs/drmdump/cluster74039/12967178031821-mapVm.dump

[2011-12-01 14:53:51.835 02472 verbose 'SoapAdapter.HTTPService'] User agent is 'Jakarta Commons-HttpClient/3.1'

[2011-12-01 14:53:51.835 02472 verbose 'SoapAdapter.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)

[2011-12-01 14:53:51.836 02472 verbose 'App'] [VpxVmomi] Invoking [waitForUpdatesEx] on [vmodl.query.PropertyCollector:propertyCollector] session [E98828D0-2CCD-4ABE-AEE1-3C30310B5D4D(40595C26-9206-4D68-9E9C-16D120BED994)]

[2011-12-01 14:53:51.847 06804 verbose 'VpxProfiler' opID=85a8b277] [4-] DRS_PROFILE CallingMapVm (took 26 ms)

[2011-12-01 14:53:51.847 06804 verbose 'VpxProfiler' opID=85a8b277] [3-] DRS_PROFILE GetPlaceForVm (took 26 ms)

[2011-12-01 14:53:51.851 06804 verbose 'VpxProfiler' opID=85a8b277] [2-] DRS_PROFILE GetInitialPlacementRecommendations (took 475 ms)

[2011-12-01 14:53:51.851 06804 verbose 'App' opID=85a8b277] [VpxdDrmInterface::GetInitialPlacementHosts] The host vm1.comp.internal picked by DRS for VM OHW9-win64 is not compatible any more.

[2011-12-01 14:53:51.851 06804 verbose 'App' opID=85a8b277] [VpxdDrmInterface::GetInitialPlacementHosts] The host vm6.comp.internal picked by DRS for VM OHW9-win64 is not compatible any more.

[2011-12-01 14:53:51.851 06804 verbose 'App' opID=85a8b277] [VpxdDrmInterface::GetInitialPlacementHosts] The host vm3.comp.internal picked by DRS for VM OHW9-win64 is not compatible any more.

[2011-12-01 14:53:51.851 06804 verbose 'App' opID=85a8b277] [VpxdDrmInterface::GetInitialPlacementHosts] The host vm7.comp.internal picked by DRS for VM OHW9-win64 is not compatible any more.

[2011-12-01 14:53:51.851 06804 verbose 'VpxProfiler' opID=85a8b277] [1-] DRS_PROFILE GetInitialPlacementHosts (took 475 ms)

[2011-12-01 14:53:51.851 06804 warning 'Libs' opID=85a8b277] ASSERT d:/build/ob/bora-345043/bora/vpx/vpxd/vpxdMoSnapshot.cpp:312

[2011-12-01 14:53:51.851 06804 error 'App' opID=85a8b277] Win32 invalid_parameter: expression=(null), function=(null), file=(null), line=0

[2011-12-01 14:54:53.001 06804 info 'App' opID=85a8b277] CoreDump: Writing minidump

[2011-12-01 14:55:32.515 06804 panic 'App' opID=85a8b277]

Panic: Win32 invalid_parameter error

Backtrace:

backtrace[00] rip 000000018010a8aa Vmacore::System::Stacktrace::CaptureWork

backtrace[01] rip 00000001800e8008 Vmacore::System::SystemFactoryImpl::CreateFileWriter

backtrace[02] rip 00000001800e84fe Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace

backtrace[03] rip 0000000180129ba5 Vmacore::PanicExit

backtrace[04] rip 0000000180129cb1 Vmacore::PanicExit

backtrace[05] rip 000000018011ab14 Vmacore::System::GetThisThread

backtrace[06] rip 00000000728b52ad invalid_parameter

backtrace[07] rip 00000000728b5309 invalid_parameter_noinfo

backtrace[08] rip 00000001400aa9b1 (no symbol)

backtrace[09] rip 00000001400ac567 (no symbol)

backtrace[10] rip 00000001400aca35 (no symbol)

backtrace[11] rip 0000000000a103c3 Vim::Vm::ScsiPassthroughInfo::_GetDataType

backtrace[12] rip 00000000003b8dc0 Vmomi::RuntimeFault::_GetDataType

backtrace[13] rip 000000014094cf6f (no symbol)

backtrace[14] rip 000000014092a672 (no symbol)

backtrace[15] rip 0000000140930a08 (no symbol)

backtrace[16] rip 000000018011f68d Vmacore::System::IsEnlisted

backtrace[17] rip 0000000180120a6f Vmacore::System::IsEnlisted

backtrace[18] rip 0000000180119df5 Vmacore::System::ThisThreadExists

backtrace[19] rip 0000000072862fdf endthreadex

backtrace[20] rip 0000000072863080 endthreadex

backtrace[21] rip 00000000771bf56d BaseThreadInitThunk

backtrace[22] rip 00000000772f2cc1 RtlUserThreadStart

[2011-12-01 14:55:32.517 06804 panic 'App' opID=85a8b277] Win32 invalid_parameter error

------ In-memory logs end --------

Has anyone seen this problem before? I found some stuff relating to Win32 Access Violation errors, but this doesn't seem applicable to this error, especially since most of those errors had been fixed prior to the 4.1.0 version.

Thanks

nalfonso14 · ‎12-01-2011

Hi SergeNZ,

The problem you describe, refers to the version 4.0 of the vCenter .. and was fixed in "Update 2".

Upgraded from 4.0.0 to 4.1.0 or migrated the vCenter DB with clean install?

http://kb.vmware.com/kb/1020114

Nicolas Alfonso Sr Virtualization Architect ***Consider awarding points for "helpful" and/or "correct" answers.***

RParker · ‎12-01-2011

In addition to what Nicolas said, make sure your DB is not full as well.. sometimes vCenter will crash if it can't write data.

sergeNZ · ‎12-01-2011

@nalfonso14

We've upgraded from 4.0 to 4.1. I've seen the KB article previously, but thought that it didn't apply due to the fact that we were on version 4.1.

All

vCenter on Windows keeps crashing