![]() After some trial and error, I found that the following commands fixed the issue: kill -9 `ps -Cuv | grep syslog | awk ''` esxcli system syslog config set -loghost="tcp://192.168.2.10" So it appears that the syslog process is stuck with a socket error. usr/lib/vmware/vmsyslog/bin/esxcfg-syslog -plugin=esxcli -loghost='tcp://192.168.2.10'Ĭheck the inner exception for more details. Additional info: Message: Got no data from process Unable to configure syslog server information for host 'esx01.matrix'. Set-VMHostSysLogServer : 9:59:28 AM Set-VMHostSysLogServer Here is what I saw: > Set-VMHostSyslogServer -VMHost esx01.matrix -SyslogServer "tcp://192.168.2.20" It all started when I attempted to configure syslog on some ESXi hosts using PowerCLI. ![]() What followed was an exercise on troubleshooting remote syslog on an ESXi host and I wanted to share some tips. I hit an interesting issue the other day when attempting to reconfigure remote syslog on some ESXi hosts.
0 Comments
Leave a Reply. |