core dumps not working on FreeBSD host
jpereira at freeradius.org
Wed Feb 5 19:20:49 CET 2020
If you could trigger it easily, maybe you could just start the process with GDB and after catching the crash just uses the command “bt full all threads” to show the entire stack trace and send it to us or create a ticket https://github.com/FreeRADIUS/freeradius-server/issues/new/choose <https://github.com/FreeRADIUS/freeradius-server/issues/new/choose>
It would be good if you could do that.
jpereira at networkradius.com
> On 5 Feb 2020, at 10:25, Marek Zarychta <zarychtam at plan-b.pwste.edu.pl> wrote:
> Dear list,
> since upgrade from 3.0.19 to 3.0.20 I am occasionally getting errors
> like this one:
> pid 23749 (radiusd), jid 1, uid 133: exited on signal 11
> This issue is somehow related to network / connectivity problems and
> looks like quite a new problem (I have not seen this in 3.0.19 and
> earlier releases). It can't be easily triggered, so I am searching for
> the culprit. To find it I have tried to enable core dumps on FreeBSD for
> radiusd but without success. I have set allow_core_dumps = yes in
> radiusd.conf file. Also these sysctls are set:
> There is no problem with getting core dumps for other daemons running on
> this host, also those running with suid/sgid enabled like bind or nsd,
> so the issue looks more like daemon related problem than OS problem.
> Any help would be greatly appreciated!
> Marek Zarychta
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users