Bug 1031215

Summary:	no events logged after SEL buffer overflow
Product:	Red Hat Enterprise Linux 6	Reporter:	Konstantin Olchanski <olchansk>
Component:	ipmitool	Assignee:	Josef Ridky <jridky>
Status:	CLOSED WONTFIX	QA Contact:	Rachel Sibley <rasibley>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-25 08:11:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Konstantin Olchanski 2013-11-15 22:32:11 UTC

ipmi event buffer monitoring by ipmievd is useless. Eventually the IPMI SEL buffer is filled to 100% and all subsequent events are lost. I think ipmievd should clear the IPMI SEL buffer automatically to prevent complete loss of event monitoring after the SEL buffer is 100% full.

Right now, ipmievd does this: (grep /var/log/messages)

Nov 15 14:07:22 positron ipmievd: SEL buffer used at 100%, please consider clearing the SEL buffer
Nov 15 14:07:22 positron ipmievd: SEL buffer overflow, no SEL message can be logged until the SEL buffer is cleared

This is not useful nor helpful because nobody looks these messages unless there is a problem, by which time SEL is 100% full and all messages related to the problem have been lost.

ipmitool already can clear this buffer manually (ipmitool sel clear), ipmievd should do this automatically, at least as an option.

[root@positron ~]# rpm -qf `which ipmievd`
ipmitool-1.8.11-14.el6_3.x86_64

K.O.

Comment 2 Ales Ledvinka 2013-11-18 08:21:46 UTC

Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to  guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain  it receives the proper attention and prioritization to assure a timely resolution. 

For information on how to contact the Red Hat production support team, please visit:

https://www.redhat.com/support/process/production/#howto

Comment 4 Josef Ridky 2017-09-25 08:11:44 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the
Production 3 Phase, Critical impact Security Advisories (RHSAs) and
selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as
they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase
and will be marked as CLOSED/WONTFIX. If this remains a critical
requirement, please contact Red Hat Customer Support to request
a re-evaluation of the issue, citing a clear business justification. Note
that a strong business justification will be required for re-evaluation.
Red Hat Customer Support can be contacted via the Red Hat Customer Portal
at the following URL:

https://access.redhat.com/