Bug 782905 - Requests fails with "Internal sanity check failed" message
Summary: Requests fails with "Internal sanity check failed" message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: freeradius
Version: 6.1
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: John Dennis
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-18 20:18 UTC by Norman Elton
Modified: 2012-06-20 14:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 14:06:09 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0881 0 normal SHIPPED_LIVE freeradius bug fix and enhancement update 2012-06-19 20:47:36 UTC

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


Note You need to log in before you can comment on or make changes to this bug.