Bug 782905

Summary:	Requests fails with "Internal sanity check failed" message
Product:	Red Hat Enterprise Linux 6	Reporter:	Norman Elton <normelton>
Component:	freeradius	Assignee:	John Dennis <jdennis>
Status:	CLOSED ERRATA	QA Contact:	Patrik Kis <pkis>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.1	CC:	dpal, ebenes, pkis, syeghiay
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 14:06:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Norman Elton 2012-01-18 20:18:07 UTC

Description of problem:

When FreeRADIUS receives a request, it can fail giving the following message:

"WARNING: Internal sanity check failed in event handler for request 6"

Unfortunately this is very hard to reproduce, we do not have a good test case yet. But our research indicates that Alan has patched the issue in newer versions of FreeRADIUS. Can we get a release of 2.1.12? We have not had any errors on this release.

Thanks

Comment 2 John Dennis 2012-01-18 23:11:43 UTC

We have a bug open to rebase FreeRADIUS in the next RHEL6 update cycle. The rebase would be freeradius 2.1.12 as you request. It is bug#736878.

Please note there is a limitation on which packages can go into any given RHEL update, unfortunately freeradius is not currently on that list but we are applying for inclusion. If this is important to you then you should have your RHEL representative escalate this, customer needs are listened to.

Comment 9 Patrik Kis 2012-05-03 08:46:35 UTC

Verified: SanityOnly

Comment 12 errata-xmlrpc 2012-06-20 14:06:09 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0881.html