Hello,
I have updated my vCenter 4.0 to 4.1.
With this task I migrated to a new W2k8R2 VM and from a SQL2005 to a SQL2008 DB.
We use the vCenter for our production servers and for our View environment, so it is very critical.
The upgrade workes fine with no error messages, but now the vCenter service crash frequently with this error message in the vpxd.log:
Panic: Win32 exception: Access Violation (0xc0000005)
Read (0) at address ffffffffffffffff rip: 00000001800cf974 rsp: 000000001063f130 rbp: 0000000180070490
rax: 000000001063f1f0 rbx: 0000000000000005 rcx: 000000001063f178
rdx: 50000000074b7e80 rdi: 0000000000000012 rsi: 0000000015686f10
r8: 0000000000000000 r9: 0000000000000004 r10: 726573750a0d312e
r11: 000000001063f1f8 r12: 000000000c293c00 r13: 0000000000000001
r14: 00000000000000f5 r15: 0000000000000000
Backtrace:
backtrace[00] rip 000000018010a1aa Vmacore::System::Stacktrace::CaptureWork
backtrace[01] rip 00000001800e8018 Vmacore::System::SystemFactoryImpl::CreateFileWriter
backtrace[02] rip 00000001800e850e Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace
backtrace[03] rip 0000000180129205 Vmacore::PanicExit
backtrace[04] rip 0000000180129377 Vmacore::PanicExit
backtrace[05] rip 000000018011b746 Vmacore::System::IsEnlisted
backtrace[06] rip 0000000074c64e25 _CxxFrameHandler3
backtrace[07] rip 0000000074c63fd2 _CxxExceptionFilter
backtrace[08] rip 0000000074c646da _CxxExceptionFilter
backtrace[09] rip 0000000074c64919 _CxxExceptionFilter
backtrace[10] rip 0000000074c64d27 _CxxFrameHandler3
backtrace[11] rip 00000000774a52cd RtlCompareUnicodeString
backtrace[12] rip 0000000077485c9c RtlTimeToSecondsSince1970
backtrace[13] rip 00000000774bfcb8 KiUserExceptionDispatcher
backtrace[14] rip 00000001800cf974 Vmacore::Http::CreateReverseHttpProxy
backtrace[15] rip 00000001800d07ee Vmacore::Http::CreateReverseHttpProxy
backtrace[16] rip 00000001801d330c VmdbPipe_AllocOnStreams
backtrace[17] rip 00000001800fac41 Vmacore::Ssl::CreateSSLContext
backtrace[18] rip 00000001801d330c VmdbPipe_AllocOnStreams
backtrace[19] rip 000000018012c1cf ExternalCoreDumpRunSlave
backtrace[20] rip 000000018011f728 Vmacore::System::IsEnlisted
backtrace[21] rip 000000018011f8f8 Vmacore::System::IsEnlisted
backtrace[22] rip 000000018012062b Vmacore::System::IsEnlisted
backtrace[23] rip 0000000180119915 Vmacore::System::GetThreadId
backtrace[24] rip 0000000074c22fdf endthreadex
backtrace[25] rip 0000000074c23080 endthreadex
backtrace[26] rip 000000007726f56d BaseThreadInitThunk
backtrace[27] rip 00000000774a3021 RtlUserThreadStart
Win32 exception: Access Violation (0xc0000005)
Read (0) at address ffffffffffffffff
rip: 00000001800cf974 rsp: 000000001063f130 rbp: 0000000180070490
rax: 000000001063f1f0 rbx: 0000000000000005 rcx: 000000001063f178
rdx: 50000000074b7e80 rdi: 0000000000000012 rsi: 0000000015686f10
r8: 0000000000000000 r9: 0000000000000004 r10: 726573750a0d312e
r11: 000000001063f1f8 r12: 000000000c293c00 r13: 0000000000000001
r14: 00000000000000f5 r15: 0000000000000000
Anyone get the same error and resolved it?
Ideas?
Thanks
Stefan
Hi,
I got that error too. I tried that solution :
For me, I found that no virtual machine was the problem. I had to put theDatabase in «Simple» Mode :
Or maybe you could try this one :
Hope this could help!
The KB articles above describes other error messages. For my issue this are no solutions.
But I have opend a SR and got a workaround now: This is a VMware Bug! The IP address that I use is longer than 40Bit : 192.168.192.232
The workaround is to use an IP address that is smaller than 40Bit like: 192.168.192.1--99
At the Moment I have not changed the IP but I hope and pray that this workaround helps...
Stefan