Summary: SELinux is preventing /usr/sbin/nagios "write" access on nagios.pid. Detailed Description: SELinux denied access requested by nagios. It is not expected that this access is required by nagios and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:nagios_t:s0 Target Context system_u:object_r:initrc_var_run_t:s0 Target Objects nagios.pid [ file ] Source nagios Source Path /usr/sbin/nagios Port <Unknown> Host (removed) Source RPM Packages nagios-3.2.0-2.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-89.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.12-174.2.22.fc12.i686 #1 SMP Fri Feb 19 19:26:06 UTC 2010 i686 i686 Alert Count 1 First Seen Mon 22 Feb 2010 02:38:29 PM CET Last Seen Mon 22 Feb 2010 02:38:29 PM CET Local ID 9d52c50a-1b84-4b17-90c8-8f0a7694f041 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1266845909.108:32677): avc: denied { write } for pid=2347 comm="nagios" name="nagios.pid" dev=dm-0 ino=5117 scontext=system_u:system_r:nagios_t:s0 tcontext=system_u:object_r:initrc_var_run_t:s0 tclass=file node=(removed) type=SYSCALL msg=audit(1266845909.108:32677): arch=40000003 syscall=5 success=no exit=-13 a0=8a8a0c8 a1=8042 a2=1a4 a3=0 items=0 ppid=2338 pid=2347 auid=4294967295 uid=490 gid=475 euid=490 suid=490 fsuid=490 egid=475 sgid=475 fsgid=475 tty=pts2 ses=4294967295 comm="nagios" exe="/usr/sbin/nagios" subj=system_u:system_r:nagios_t:s0 key=(null) Hash String generated from catchall,nagios,nagios_t,initrc_var_run_t,file,write audit2allow suggests: #============= nagios_t ============== allow nagios_t initrc_var_run_t:file write;
*** This bug has been marked as a duplicate of bug 539963 ***