I recently updated Log Insight to version 3.3.2 in my lab. After selecting the appropriate PAK file, the UI displayed a warning containing the following text:<\/p>\n
Note that certain builds of ESXi need to have \ntheir syslog configuration reloaded after restart, \notherwise log data will stop forwarding. \nConfiguration can be reloaded from the vSphere \nIntegration page<\/a>. See the Online Help<\/a> for \nmore information.\n<\/pre>\nI waited a couple hours after the upgrade to check back on the system and noticed that I was no longer collecting syslog data. I visited the vSphere Integration page and reviewed my hosts, but they were already configured as expected. I picked just one host and updated the configuration anyway, and that host started logging data again. For another host, I manually cleared the syslog.global.logHost value from the web client and then re-entered the logHost text. This also caused the host to start sending syslog data again. Interested in the minimum effort to ‘reload’ syslog configuration (without needing to update\/reset logHost values) I found the following KB article: https:\/\/kb.vmware.com\/kb\/2003322<\/a>. It appears that esxcli has an option to simply reload the configuration (using esxcli system syslog reload<\/span>). To run this on all hosts remaining in my inventory, I executed the following code:<\/p>\n\n\n
Get-VMHost | Sort-Object Name | %{\n write-host -nonewline \"$($_.Name) reloading syslog:\"\n (Get-EsxCli -VMHost $($_.Name) -v2).system.syslog.reload.invoke()\n}<\/code><\/pre>\n\n\n\nNote: this requires the latest version (6.3 release 1) of PowerCLI. I hope someone finds this information helpful.<\/p>\n","protected":false},"excerpt":{"rendered":"
I recently updated Log Insight to version 3.3.2 in my lab. After selecting the appropriate PAK file, the UI displayed a warning containing the following text: Note that certain builds of ESXi need to have their syslog configuration reloaded after … Continue reading