He saw the following failed vCenter task in his vSphere Client.
The error message:
setting["Syslog.global.logHost"] is invalid or exceeds the maximum number of characters permitted
seemed very strange to me.
From ESXi logs collected by LogInsight was evident that ESXi advanced setting cannot be configured through API. However, the same or similar issue can be reproduced by esxcli command for setting the advanced parameter.
esxcli system settings advanced set -o /Syslog/global/logHost -s “udp://220.127.116.11:514”
Unable to find branch Syslog
The resolution of this problem was to configure syslog configuration (as described in my older blog post here) instead of setting advanced parameter /Syslog/global/logHost.
The command to configure remote syslog is
esxcli system syslog config set --loghost='tcp://18.104.22.168:514' help customer to resolve the issue.
I have never seen this issue in other vSphere environments so hope this helps to at least one other person from VMware community.