vCenter Server Appliance 6.7 Deployment Fails During Firstboot - VMware Identity Management Service Firstboot Failed - "Failure setting accounting for vmware-sts-idmd" - "Illegal given domain name: [vCenter Hostname]​"
search cancel

vCenter Server Appliance 6.7 Deployment Fails During Firstboot - VMware Identity Management Service Firstboot Failed - "Failure setting accounting for vmware-sts-idmd" - "Illegal given domain name: [vCenter Hostname]​"

book

Article ID: 338256

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
To learn more about firstboot issues see: Understanding and Troubleshooting vCenter Server and vCenter Server Appliance 6.7 Firstboot Install/Deployment, Upgrade, or Migration Failures​.
To collect a log bundle or review log files for a vCenter Server Appliance install, upgrade, or migration issues reference Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure.  The relevant logs will be on the newly deployed appliance.  

firstbootStatus.json contains the following:
 
"failedSteps": "vmidentity-firstboot"

vmidentity-firstboot.py_####_stderr.log contains the following:
 
Failure setting accounting for vmware-sts-idmd.

Note: 
  • vCenter Server Appliance - Firstboot logs are located in the /var/log/firstboot directory.

vmware-sts-idmd.log contains the following:

Illegal given domain name: [vCenter Hostname]​

Note:
  • vCenter Server Appliance - Each service will have it's own folder in the /var/log/vmware/ directory.  The vmware-sts-idmd logs are located in the /var/log/vmware/sso folder.


Environment

VMware vCenter Server Appliance 6.7.x

Cause

vCenter Server Appliance utilizes a version of java that requires domain names to not contain non-LDH ASCII characters.

Resolution

Ensure that the vCenter Server Appliance domain name does not contain non-LDH ASCII characters.  One of the most common characters of this type is the underscore ("_"). For more information about non-LDH characters, see the IETF RFC.