W dniu 05.02.2020 o 19:20, Jorge Pereira pisze:
Hi Marek,
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.
-- Jorge Pereira jpereira@networkradius.com
I have been using freeradius3-3.0.20 since Nov 26th 2019 on both systems, the issue has occurred only 3 or 4 times since then, so it can't be triggered easily. I believe that running the process in the debugger for weeks is not an acceptable scenario. I suspect that some network related problems triggered the issue but it's not easily reproducible. I must admit that so far all previous versions survived network outages easily. I am running FreeRADIUS on FreeBSD for 10+ years, never encountered strictly OS related issues since both FreeRADIUS and FreeBSD are great pieces of software. I am grateful and really appreciate your work guys as well as the ability to get your support here. With kind regards, -- Marek Zarychta