read write error in checkresults

[Gilbert Samson]

Hello Nagios :)

I have finished my first instaltion two days back and I thought every thing is normal . In the morning I checked the message log and found ton of read/wright permision errors like this and this was only for ping check commands. 

Jul 21 22:03:08 nagios kernel: audit(1216702988.048:263963): avc:  denied  { read write } for  pid=13027 comm="ping" path="/usr/local/nagios/var/spool/checkresults/checkehZYV1" dev=hda3 ino=5201483 scontext=root:system_r:ping_t:s0 tcontext=root:object_r:usr_t:s0 tclass=file

Jul 21 22:03:32 nagios kernel: audit(1216703012.212:263964): avc:  denied  { read write } for  pid=13031 comm="ping" path="/usr/local/nagios/var/spool/checkresults/checkaJbTU8" dev=hda3 ino=5201483 scontext=root:system_r:ping_t:s0 tcontext=root:object_r:usr_t:s0 tclass=file

Folder permission
drwxr-xr-x 2 nagios nagios 20480 Jul 21 22:13 checkresults

My ping Check command:
$USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5

Aruguments 

check_ping!1000.0,40%!3000.0,80%


Forgive me if it is some basic error/stuff  and thank you very much for your help.

Kind Regards
Gilbert Samson



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080722/9b1469d2/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null