Well, the thread is no longer new, but still seems current, even with vSphere 8.
When the SEL is full, the error message also appears and the vSphere Client appears to hang.
In this cases and if you don't want to wait, use this PowerShell snippet:
$VIServer = "your-vcenter"
Connect-viserver $VIServer
$VMHostToEdit = "Host-SEL to clear"
function Clear-VMHostSEL {
Param(
[parameter(Mandatory=$true, ValueFromPipeline=$true)]$VMHosts
)
process {
foreach($VMHost in $VMHosts){
$VMhostView = Get-View $VMHost
$VMhostHealthView = Get-View -Id $VMhostView.ConfigManager.HealthStatusSystem
$VMhostHealthView.ClearSystemEventLog()
}
}
}
Write-Host "DisConnect-VMHost $VMHostToEdit"
Set-VMHost $VMHostToEdit -State "Disconnected"
Write-Host "Connect-VMHost $VMHostToEdit"
Start-Sleep -s 10
$VMHost = Get-VMhost $VMHostToEdit
$connectSpec = New-Object VMware.Vim.HostConnectSpec
$connectSpec.force = $true
$connectSpec.hostName = $VMHost.name
$VMHost.extensionData.ReconnectHost_Task( $connectSpec,$null )
Write-Host "Clearing SEL of: $VMHostToEdit"
Start-Sleep -s 10
Get-VMhost $VMHostToEdit | Clear-VMHostSEL
Disconnect-VIServer * -Confirm:$false
exit