I have 6 hosts all configured with the same syslog configuration:
Local Log Output: /scratch/log
Local Logging Default Rotation Size: 1024
Local Logging Default Rotations: 8
Log To Unique Subdirectory: false
Remote Host: tcp://server.domain.com:514
Two of the 6 hosts no longer write to the vmkernel and vmkwarning logs locally for some reason. They do write to other logs like syslog, vobd, vpxa, etc. They are writing to the syslog server configured in Remote Host. I've already tried reloading syslog via Powershell and from the console to no avail. I've torn out the syslog server config and restarted and still doesn't log. Are these vmk* logs separate from syslog? Any ideas?
EDIT: I should also add that it is not a disk space issue as other logs are being written to appropriately.
Hi
Welcome to the communities.
I don't thinks both log are different .
Hello ,
syslog.log is different from syslog server. your syslog server is a repository for all the logs.
if vmkernel is not doing the logging .. seems that the logging deamon service may not be responding correctly. A restart of the management agents should fix the problem.
Thanks,
Avinash
