Recently, I rebooted my vCenter after doing some customer configuration changes – and it never came back.
Kept troubleshooting and some of the symptoms were –
1. VPXD.EXE service runs but vmware service won’t start.
2. SSO server was fine. Inventory service was fine.
3. Database was fine
4. Killing the VPXD.EXE service would simply restart it but vcenter won’t come back up.
5. Configuration restore didn’t fix the issue.
6. The VPXD log stopped updating and event log reported VPXD.EXE was corrupted.
A snap of the VPXD log said –
2013-06-19T16:38:41.934-05:00 [00248 info ‘vpxdvpxdHostCnx’ opID=SWI-41cfcd8c] [VpxdHostCnx] Host connection reaper thread exiting
2013-06-19T16:38:41.934-05:00 [00248 warning ‘VpxProfiler’ opID=SWI-41cfcd8c] VpxUtil_InvokeWithOpId [TotalTime] took 3812269207 ms
2013-06-19T16:38:41.934-05:00 [00248 info ‘ThreadPool’] Thread delisted
2013-06-19T16:38:41.934-05:00 [02156 warning ‘VpxProfiler’ opID=SWI-91fdbb72] VpxUtil_InvokeWithOpId [TotalTime] took 3812269207 ms
2013-06-19T16:38:41.934-05:00 [02156 info ‘ThreadPool’] Thread delisted
A quick google and a bit of researching landed me at a vCenter known bug where the VPXD service starts before the SSO.
Now this is weird because my vCenter setup is not a standalone with all services in one box. However the fix for the bug was an upgrade to vCenter build 5.1.0-build 1123961. I was running vCenter build 5.1.0-build 947673. Below is a snippet of how to find the build number.
Here is the KB article about the issue. Needless to say – the issue was resolved after the upgrade!
Enjoy and comment if you like 🙂
Follow Us!