Alan DeKok-2 wrote:
Uh... packets are not signals. Use "ktrace" to monitor signals sent to a process.
Well, I've now monitored an "Exiting normally" event using ktrace: /var/log/radius.log: Sat Dec 18 02:43:43 2010 : Info: Exiting normally. /var/log/messages: Dec 18 02:43:43 radius kernel: pid 655 (radiusd), uid 133: exited on signal 11 $ kdump | tail -20 655 radiusd CALL fstat(0xa,0xbf8fb280) 655 radiusd STRU struct stat {dev=83, ino=2378852, mode=-rw------- , nlink=1, uid=133, gid=133, rdev=0, atime=1292640223, stime=1292640223, ctime=1292640223, birthtime=1292640223, size=0, blksize=16384, blocks=0, flags=0x0 } 655 radiusd RET fstat 0 655 radiusd CALL lseek(0xa,0,SEEK_SET,0x2) 655 radiusd RET lseek 0 655 radiusd CALL write(0xa,0x28752000,0x54) 655 radiusd GIO fd 10 wrote 84 bytes "Sat Dec 18 02:43:43 2010 Timestamp = 1292640223 Request-Authenticator = Verified " 655 radiusd RET write 84/0x54 655 radiusd CALL close(0xa) 655 radiusd RET close 0 655 radiusd PSIG SIGSEGV SIG_DFL 655 radiusd RET _umtx_op -1 errno 4 Interrupted system call 655 radiusd RET _umtx_op -1 errno 4 Interrupted system call 655 radiusd RET _umtx_op -1 errno 4 Interrupted system call 655 radiusd RET _umtx_op -1 errno 4 Interrupted system call It seems I can semi-reliably replicate this scenario. When I force this radius server to become the primary, it exits after a few hours. / Danial -- View this message in context: http://freeradius.1045715.n5.nabble.com/FreeRADIUS-exiting-with-Signal-11-on... Sent from the FreeRadius - User mailing list archive at Nabble.com.