Error: "no healthy upstream" when accessing the vCenter Server UI due to stsd service pre-start failure
search cancel

Error: "no healthy upstream" when accessing the vCenter Server UI due to stsd service pre-start failure

book

Article ID: 419617

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • The vCenter Server UI displays the following error: no healthy upstream

  • The stsd service is in a stopped state, which is verifiable using the command: service-control --status --all

  • Manual attempts to start the stsd service fails with the error message: An error occurred while starting service '%(0)s'

  • The STS service pre-start failure is observed in /var/log/vmware/vmon/vmon.log:

YYYY-MM-DDTHH:MM:SSZ Wa(03) host-#### <sts> Service pre-start command's stderr:     raise CalledProcessError(retcode, process.args,
YYYY-MM-DDTHH:MM:SSZ Wa(03)+ host-#### subprocess.CalledProcessError: Command '['/opt/likewise/bin/lwregshell', 'list_values', '[HKEY_THIS_MACHINE\\Services\\vmdir]']' returned non-zero exit status 252.
YYYY-MM-DDTHH:MM:SSZ Er(02) host-#### <sts> Service pre-start command failed with exit code 1
  • The following error occurs when attempting to read the lwregshell registry using the command: /opt/likewise/bin/lwregshell ls "[HKEY_THIS_MACHINE\Services\vmdir]"

lwregshell (error = 40700 - LWREG_ERROR_NO_SUCH_KEY_OR_VALUE)
No such key or valueCause Justification

Environment

VMware vCenter Server 8.x

Cause

The stsd service fails to start due to residual stale likewise processes.

Resolution

  • To resolve the issue, reboot the vCenter Sever which will clear the stale likewise processes and start the sts service.

Additional Information

"LWREG_ERROR_NO_SUCH_KEY_OR_VALUE", vCenter update fails with error Internal error occurs during execution of update process