jpereira at freeradius.org
Tue Sep 7 16:01:15 CEST 2021
Have you heard about the “dmesg” command? Try “dmesg | grep radius” just to see if the crash is really in the FreRADIUS or is related to some other linked library.
Other than that, take a look at the option “panic_action” in radiusd.conf e.g: https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/radiusd.conf.in#L151
Which version are you using? Which is your system?
jpereira at freeradius.org
> On 7 Sep 2021, at 10:17, Franro Paxton <franro at ionlinesp.co.za> wrote:
> Hi Alan,
> There's not really much to it.
> Yesterday our monitoring systems reported that most of our radius
> servers restarted after I did some investigation this is the error code
> I got that killed the radius processes
> - freeradius.service: Main process exited, code=killed, status=11/SEGV
> #Signal 11 (SIGSEGV, also known as segmentation violation) means that
> the program accessed a memory location that was not assigned to it.
> That's usually a #bug in a program.
> - freeradius.service: Failed with result 'signal'.
> - Started FreeRADIUS multi-protocol policy server.
> After I did some googling all I could find is what the error means but
> no clear explanation as to why it happened.
> Franro Paxton
> Junior Systems Engineer
> iONLINE ISP (PTY) LTD - RSA
> P: 0861466546 M:
> W: www.ionlinesp.com E: franro at ionlinesp.co.za
> 14 Stanford Office Park, 12 Bauhinia St, Highveld, Centurion, Gauteng,
> 0157, South Africa
> png] 
> This email and its content are subjected to iONLINE's disclaimer.
> -----Original Message-----
> From: Freeradius-Users
> <freeradius-users-bounces+franro=ionlinesp.co.za at lists.freeradius.org>
> On Behalf Of Alan DeKok
> Sent: Tuesday, 07 September 2021 14:55
> To: FreeRadius users mailing list
> <freeradius-users at lists.freeradius.org>
> Subject: Re: segmentation violation
> On Sep 7, 2021, at 8:50 AM, Franro Paxton <franro at ionlinesp.co.za>
>> I need help with the below error
>> freeradius.service: Main process exited, code=killed, status=11/SEGV
>> Yesterday we got alerts that most of our radius servers restarted
> after some investigation this is what I got, from here I am unable to
> determine what exactly could have caused this.
>> Any help will be appreciated greatly.
> You have given precisely zero information about this issue. There is
> absolutely nothing we can do to help.
> On the other hand, if you follow the documentation and give useful
> information, we may be able to help.
> You can open an issue on GitHub at
> When you open an issue, PLEASE follow the documentation. If you
> don't, the issue will be closed.
> Alan DeKok.
> List info/subscribe/unsubscribe? See
> Visible links
> 1. http://www.ionlinesp.com/
> 2. https://www.facebook.com/ionlinesp
> 3. https://twitter.com/ionlinesp
> 4. https://www.linkedin.com/company/ionline
> 5. https://www.ionlinesp.com/email-disclaimer/
> 6. https://github.com/FreeRADIUS/freeradius-server/issues
> 7. http://www.freeradius.org/list/users.html
> Hidden links:
> 9. https://www.twitter.com/user_name_here
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users