So, I recently reinstalled FC5 on my desktop computer, and all seemed to be working well. I had saved all my config scripts for just about everything, including nagios. I reinstalled nagios, as I have several times before, and setup everything as it should and then stopped using this computer directly, hence the reason why I didn't run into this problem until today. Nagios is *working*, in as much that it will email me when something goes down or comes back up, but it will not page me, no matter what, and so I started investigating. I got an error that I hadn't seen before, and its repeated several times inside the system log. Even worse, it clogs up all normal TTY's on the system; fortunately (or unfortunately) I'd been using SSH [long story] so I hadn't noticed until today when I got a new kvm switch.
here's an excerpt of /var/log/messages:
Code:
Mar 5 14:21:00 SystemName kernel: audit (1173133279.246:4): avc: denied (read) for pid=2241 comm="ping" name="nagios.cmd" dev=dm-0 ino=4163262 scontext=system_u:system_r:ping_t:s0 tcontect\system:u:object_r:usr_t:s0 tclass=fifo_file
Mar 5 14:22:15 SystemName kernel: audit (1173133335.306:5): avc: denied (read) for pid=2262 comm="ping" name="nagios.cmd" dev=dm-0 ino=4163262 scontext=system_u:system_r:ping_t:s0 tcontect\system:u:object_r:usr_t:s0 tclass=fifo_file
and this keeps going on and on and on... [so far about 4mb of this in text format] Is this some sort of a firewall setting inside the kernel no allowing the pings to go out? Did nagios just get borked up and need to be reinstalled?
