In a previous post I installed and configured the Synology Syslog server to allow me to stop me getting the below message on my hosts.
The reason for the message is that I run my 3 ESXi hosts using SanDisk Cruzer Fit USB keys and as such there is no persistent storage for logs. In this post I am going to show you how to configure some VMware infrastructure to point to our newly configured Syslog server.
In this post we are going to configure the Synology Syslog server so that we can get rid of the message below that occurs because my servers use the SanDisk Cruzer Fit USB drives
After a recent upgrade to our vCenter 5.1 infrastructure we discovered that we were getting the following error when trying to use the log browser component of the web client.
Having tried a number fixes from the usual sources (Derek Seamans excellent blog) none of them seemed to resolve the issue, a reboot of the infrastructure, a re-install of the Web Client all resulted in the same error cropping up. In the end it took the eyes of a VMware BCS Engineer to have a look at our ca_certificates.crt file and discover some white space present.
The strange thing here is that there wasn’t any date change on the file since the initial deployment back last year and we had no issues with the log browser working before the upgrade.
If you experience any issues with the log browser it may be worth checking the C:\ProgramData\VMware\SSL\ca_certificates(_2).crt file to make sure that there isn’t any white space present in the file first.