Aaron A. Glenn <[email protected]> wrote:
> > > Sep 18 19:06:10 nairobi bgpd[99160]: session engine ready
...
> > > Sep 18 19:06:12 nairobi bgpd[92056]: session engine terminated; signal 11
> > > Sep 18 19:06:12 nairobi bgpd[92056]: route decision engine terminated;
> > > signal 11
> > > Sep 18 19:06:12 nairobi bgpd[92056]: terminating
...
> Since it doesn't (seem to) coredump, I was unable to coax anything into
> /var/crash/bgpd
The session engine has performed an incorrect memory access and received
SIGSEGV. It is trying to dump core, but has no place to do so since it
is chrooted.
That is where the sysctl advice comes from:
To place core dumps from issetugid(2) programs (in this example bgpd(8))
into a safe place for debugging purposes:
# mkdir -m 700 /var/crash/bgpd
# sysctl kern.nosuidcoredump=3
The kernel is taught there is a safe place to dump such core files.
Repeat the test please.
