Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 782905 - Requests fails with "Internal sanity check failed" message
Requests fails with "Internal sanity check failed" message
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: freeradius (Show other bugs)
6.1
x86_64 Linux
low Severity medium
: rc
: ---
Assigned To: John Dennis
Patrik Kis
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-18 15:18 EST by Norman Elton
Modified: 2012-06-20 10:06 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 10:06:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0881 normal SHIPPED_LIVE freeradius bug fix and enhancement update 2012-06-19 16:47:36 EDT

  None (edit)
Description Norman Elton 2012-01-18 15:18:07 EST
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 18:11:43 EST
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 04:46:35 EDT
Verified: SanityOnly
Comment 12 errata-xmlrpc 2012-06-20 10:06:09 EDT
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.