On 27 Nov 2015, at 07:24, Stefan Winter <stefan.winter@restena.lu> wrote:
Hi,
I finally was able to catch thecrash which I see very intermittently with 3.0.10.
Today, it happened in a sequence every some 30 seconds; apparently a continued authentication attempt by one user always triggered the fatal code path.
After switching runtime perms to root/root, gdb actually worked and provided a backtrace.
I'm attaching the gdb session log. I see EAP sub-module failed, and EAP-pwd, so I think it's got to be in that area.
I also configured the system to dump a core. As soon as I find it on the filesystem, I can send it off-list to a developer who cares about it :-)
Went back in time and fixed it for you: https://github.com/FreeRADIUS/freeradius-server/issues/1320 -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2