Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001377PacketFenceupstreampublic2012-02-07 11:032012-02-28 14:31
Assigned Toobilodeau 
PlatformOSOS Version
Product Version 
Target Version3.2.0Fixed in Version3.2.0 
Summary0001377: freeradius segfaults
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb54f4b90 (LWP 27887)]
0x00bc5726 in Perl_sv_setsv_flags () from /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/

We're seeing this since a little while, so far we haven't got too deep into identifying root cause as we were thinking it was a freeradius problem... Now, I am getting tired of it...

Affects large environments

- Unable to reliably reproduce
- Tried freeradius 2.1.10-12 packaged and from source

Candidate solutions to move things forward:
- [^]
- recompile freeradius and perl together with a stable perl release (> 5.10)
- try to make the stacktrace better by compiling freeradius AND perl with debug/symbols enabled
- try other rlm_perl debug options as outlined on the freeradius-users list ( [^])


Use watchdog script in addons/.
Steps To Reproduce1. Have a large wireless deployment
2. See radiusd segfault at least once a week
TagsNo tags attached.
fixed in git revision
fixed in mtn revision8219835d3324599dc23038758d2ef3324c25ae5b
Attached Files

- Relationships

-  Notes
obilodeau (reporter)
2012-02-21 14:09

We were able to reliably reproduce in a specific environment with a lot of load. With gdb we still tracked down the issue to rlm_perl / Discussing the problem to people outside of it, we got suggestions to track all native modules used by our perl module.

We found out about Sys::Syslog which uses the native syslog library by default. We decided to port our logging to the native facilities offered by radius' rlm_perl and configure radius to log to the syslog by default.
obilodeau (reporter)
2012-02-21 20:54

This is tentatively marked as fixed. We think we nailed it in at least one obvious crashing case but we won't know for sure until we've deployed the fix more widely.

If you still get radiusd segfaults please let us know and re-open.
obilodeau (reporter)
2012-02-28 14:31

Fixed in recently released 3.2.0.

- Issue History
Date Modified Username Field Change
2012-02-07 11:03 obilodeau New Issue
2012-02-07 11:09 obilodeau Description Updated
2012-02-21 14:05 obilodeau Status new => assigned
2012-02-21 14:05 obilodeau Assigned To => obilodeau
2012-02-21 14:09 obilodeau Note Added: 0002574
2012-02-21 14:10 obilodeau Description Updated
2012-02-21 20:54 obilodeau mtn revision => 8219835d3324599dc23038758d2ef3324c25ae5b
2012-02-21 20:54 obilodeau Note Added: 0002575
2012-02-21 20:54 obilodeau Status assigned => resolved
2012-02-21 20:54 obilodeau Fixed in Version => trunk
2012-02-21 20:54 obilodeau Resolution open => fixed
2012-02-28 14:22 obilodeau Target Version => 3.2.0
2012-02-28 14:22 obilodeau Fixed in Version trunk => 3.2.0
2012-02-28 14:31 obilodeau Note Added: 0002583
2012-02-28 14:31 obilodeau Status resolved => closed

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker