vCenter not accessible due to VPXD service unexpected crashing after upgrade to version 8.0.2.x
search cancel

vCenter not accessible due to VPXD service unexpected crashing after upgrade to version 8.0.2.x

book

Article ID: 377948

calendar_today

Updated On:

Products

VMware vCenter Server 8.0

Issue/Introduction

Symptoms:

 

  • vSphere Client not accessible with error  "no healthy upstream"

  • VPXD service keeps crashing creating core.vpxd-worker.xxxx dumps

  • vmon logs contains errors similar to the excerpt below:

    /var/log/vmware/vmon/vmon.log
    YYYY-MM-DDTHH:MM:SS In(05) host-2646 <vpxd> Service is dumping core. Coredump count 10. CurrReq: 0
    YYYY-MM-DDTHH:MM:SS In(05) host-2646 <event-pub> Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonEventPublisher.py --eventdata vpxd,UNHEALTHY,HEALTHY,1 
    YYYY-MM-DDTHH:MM:SS Wa(03) host-2646 <vpxd> Service exited. Exit code 1
    YYYY-MM-DDTHH:MM:SS Wa(03) host-2646 <vpxd> Service exited unexpectedly. Crash count 10. Taking configured recovery action.

Environment

VMware vCenter Server 8.0.2.x

Cause

The issue is caused by a race condition affecting the Token Refresh function in vCenter.

Resolution

A fix has been provided to address the issue in vCenter version 8.0.3 or later.