topic Re: System Management Software 1 SEL Fullness 0: Log Full - Assert in ESXi Discussions

System Management Software 1 SEL Fullness 0: Log Full - Assert

xblain — Sun, 27 Mar 2016 08:05:33 GMT

Hi all,

We have an old VmWare ESXi 4 in our organization, No vCenter installed.
I have two warning messages regarding to log capacity , print screen is attached.
I have access via SSH to Tech Support mode ,also I can access folders on the server and locate the log file.

Tried to clear the log as suggested here: VMware KB: The Host IPMI System Event Log Status alarm is triggered repeatedly in VMware vCenter Server 4.x and 5.x
But when I run the "localcli hardware ipmi sel clear" command in SSH connection I get an error: -ash: localcli: not found.

Please help me to clear the logs,

Can I just remove the log file from the server?

Re: System Management Software 1 SEL Fullness 0: Log Full - Assert

Techie01 — Sun, 27 Mar 2016 14:37:35 GMT

AFAIK, localcli did not exist in esx 4.x . It was introduced in 5.0 onwards.

From the KB , localcli hardware ipmi sel clear command is introduced specifically in a releaseof 5.1 and 5.5 only. For 4.x following steps should solve the issue.

To clear the IPMI System Event.log file and reset the sensors:

Open vCenter Server using vSphere Client.
In the vCenter Server Inventory, select the ESXi/ESX host.
Click the Hardware Status tab.
Click System Event log under View.
Click Reset Event Log. The red alert is removed from the System Event log.
Click Reset Sensors to reset the host sensors.

Re: System Management Software 1 SEL Fullness 0: Log Full - Assert

xblain — Tue, 29 Mar 2016 13:52:50 GMT

Hi ,

As I mentioned before we donwt have vCenter installed.
Furthermore I think there is no option to connect ESXi 4 (free edition) to the vCenter. May be I am wrong...
I have no access to download the vCenter 4 in official VMWare download page.

So is there any other option? May be I can get download link from somewhere and try to install vCenter?

Thanks in advance,

Re: System Management Software 1 SEL Fullness 0: Log Full - Assert

xblain — Mon, 04 Apr 2016 06:19:37 GMT

So. I figured out how to do this.
First we need to understand that it could be Server Host BIOS logs or in another case the partition containing logs can be out of storage.

In my case the problem was in IBM server BIOS logs. I just cleared BIOS logs from the host server (restart required).
Other way to overcome this problem , if it was a partition that run out of space is to point logs to another , larger partition.
This could be done under Configuration>>Software>>Advanced Settings -> ScratchConfig.

Hope that will help to anyone.... I don't sure that ESXi4 exist somewhere except my company