Acknowledge service problem fails
Posted: Thu Jun 25, 2015 9:21 am
Hello everyone,
Yesterday I noticed a problem when I attempted to acknowledge service alerts. During the commit, after entering a comment, i get an error; the commit could not take place and the permissions on /usr/local/nagios/var/rw/nagios.cmd may be incorrect:
[root@sms1 rw]# ll
total 0
prw-rw----. 1 nagios nagcmd 0 Jun 24 17:05 nagios.cmd
srw-rw----. 1 nagios nagcmd 0 Jun 24 17:05 nagios.qh
[root@sms1 rw]# pwd
/usr/local/nagios/var/rw
[root@sms1 rw]#
Nagios XI 2014R2.7
So I change the permissions on nagios.cmd using chmod a+w, the commit works. But then later the permissions on the nagios.cmd named pipe default back to 660 and the commits fail again with the same error.
Is there something re-setting the permissions on that named pipe? What else could be causing the commits to fail?
I was loged in as nagiosadmin when I did these commits. I have not tried as a normal user.
Yesterday I noticed a problem when I attempted to acknowledge service alerts. During the commit, after entering a comment, i get an error; the commit could not take place and the permissions on /usr/local/nagios/var/rw/nagios.cmd may be incorrect:
[root@sms1 rw]# ll
total 0
prw-rw----. 1 nagios nagcmd 0 Jun 24 17:05 nagios.cmd
srw-rw----. 1 nagios nagcmd 0 Jun 24 17:05 nagios.qh
[root@sms1 rw]# pwd
/usr/local/nagios/var/rw
[root@sms1 rw]#
Nagios XI 2014R2.7
So I change the permissions on nagios.cmd using chmod a+w, the commit works. But then later the permissions on the nagios.cmd named pipe default back to 660 and the commits fail again with the same error.
Is there something re-setting the permissions on that named pipe? What else could be causing the commits to fail?
I was loged in as nagiosadmin when I did these commits. I have not tried as a normal user.