[YYYY-MM-DDTHH:MM:SS] INFO [ad16b29fc9944373] [services/initUtils.js, init, logStartupArguments:408] Starting sddcManagerServer: /usr/bin/node /opt/vmware/vcf/sddc-manager-ui-app/server/src/servers/sddcManagerServer/index[YYYY-MM-DDTHH:MM:SS] VERBOSE [ad16b29fc9944373] [servers/sddcManagerServer/init.js, init, init:29] Begin Init().[YYYY-MM-DDTHH:MM:SS] INFO [ad16b29fc9944373] [servers/sddcManagerServer/www.js, init, null:123] --- server initializing ---[YYYY-MM-DDTHH:MM:SS] INFO [ad16b29fc9944373] [servers/sddcManagerServer/www.js, init, null:139] Server listening on 127.0.0.1:7500[YYYY-MM-DDTHH:MM:SS] INFO [ad16b29fc9944373] [servers/sddcManagerServer/www.js, init, onListening:39] listening on port 7500[YYYY-MM-DDTHH:MM:SS] ERROR [ad16b29fc9944373] [services/ws1bAuthentication/ws1bAuthenticationService.js, init, getWs1bClientId:93] error during getWs1bClientId 404 - "{\"errorCode\":\"SDDCMANAGER_GET_OIDC_INFO_FAILED\",\"arguments\":[\"Failed to get the SDDC Manager OIDC Client information ntpq -pn on the SDDC Manager and vCenter shows a large time offset. Refer to KB Troubleshooting NTP on ESX and ESXi 6.x / 7.x / 8.xVCF 5.1.1
This is caused by time offset between the management vCenter and the SDDC Manager.
Typically, NTP is set and configured to a NTP Server. Refer to Configuring vCenter Server to use a Network Time Protocol (NTP) server for additional information. Change the mode to host for the vCenter to get the correct time from the hosts instead.
Run the date command on vCenter and SDDC Manager at the same time. Then use the following command to set the SDDC Manager to the correct time from the management vCenter. This is a workaround to help the UI load, it will not persist after reboots unlike changing the ntp mode above.
Exampledate -s “2 June 2023 14:05:00”