First of all, sorry if this is a stopid question
It's the second time I play with grsecurity, and I already have some issues before even playing with the ACLs ...
I'm trying to get Nagios (http://www.nagios.org) up n' running, but got some problems which I don't understand ... and I don't find much help from the logs, except that the grsec kernel extension kills the process.
/etc/rc.d/init.d/nagios start
Starting network monitor: nagios
No lock file found in /home/httpd/nagios/var/nagios.lock
From Nagios logs, everything seems fine - except a sigterm at the end :
[1043601212] Finished daemonizing... (New PID=11371)
[1043601212] Caught SIGSEGV, shutting down...
And it seems that this sigterm is sent by grsec for some reason :
Jan 26 12:13:32 nagios nagios: Finished daemonizing... (New PID=11371)
Jan 26 12:13:32 nagios kernel: grsec: From 172.16.16.13: signal 11 sent
to (nagios:11371) UID(0) EUID(0), parent (nagios:3278) UID(0) EUID(0)
Jan 26 12:13:32 nagios nagios: Caught SIGSEGV, shutting down...
Jan 26 12:13:32 nagios kernel: grsec: From 172.16.16.13: signal 11 sent
to (nagios:11371) UID(0) EUID(0), parent (nagios:3278) UID(0) EUID(0)
Any help appreciated here ...
I also tried to disable nagios with a kernel boot parametter but I couldn't find yet which parametter it is (I remember that there was something like that a while ago ...)
I'll try with an 'insecure' kernel then to be sure ...
Tia, Treuf
