On Thu, Oct 22, 2015 at 4:19 PM, d tbsky <tbskyd@gmail.com> wrote:
2015-10-22 16:27 GMT+08:00 <A.L.M.Buxey@lboro.ac.uk>:
Hi,
does the bug fixed in 3.0.10 or I need to log more radiusd info to track the issue?
3.0.10 was released because lofs of bugs were fixed. the first thing to do is try the latest version to see if that bug has been already squashed. if not, THEN do the debugging/tracing etc
alan -
ok I will try 3.0.10. any suggestion about radiusd debug setting so I can get useful info if the situation happen again? the server crashed after online about a month, so I think it is not easy to trigger in my environment.
thanks for the hint.
Assuming you compile your own binary, OR your package comes with debug packages, see "panic_action" on radiusd.conf -- Fajar