radiusd doesn't dump a core after SIGSEGV?

[Alan DeKok]

On Oct 22, 2024, at 1:51 PM, Coy Hile (BLOOMBERG/ 919 3RD A) <chile1 at bloomberg.net> wrote:
> 
> We've found that radiusd has died a couple times recently (using RedHat's packages on RHEL 8.8) without leaving a core file or even a stack trace that we can use to investigate the issue. Is that expected? I see the panic_action in `radiusd.conf`, but I don't want to run `gdb` on the core; I just want a core left behind so I can investigate the cause of the crash.
> 
> Any idea what I'm missing?

  See radiusd.conf.  "allow_core_dumps"

  The problem is that the OS often has additional settings which limit core dumps for background daemons.

  And which version are you running?

  But also... if you're using RedHat and paying for support, they should really be helping you.  We often find that RH distributions ship very old / out of date packages.

  Alan DeKok.