Your request was not processed in a timely manner....

[emislivec]

third: ll /usr/local/nagios/var/rw/
total 4
-rw-r--r-- 1 apache nagcmd 29 Jun 19 16:52 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 Jun 17 14:42 nagios.qh

Ran these again today to make sure it was on the right host as I had most of our nagios instance open. Looks like I might have ran them on either our prod instance.

The type and ownership of nagios.cmd is wrong. That should be a pipe owned by nagios:

Code: Select all

prw-rw----. 1 nagios nagcmd 0 Jun 20 10:28 nagios.cmd

Delete that file and restart Core:

Code: Select all

rm /usr/local/nagios/var/rw/nagios.cmd
service nagios restart

[[email protected]]

third: ll /usr/local/nagios/var/rw/
total 4
-rw-r--r-- 1 apache nagcmd 29 Jun 19 16:52 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 Jun 17 14:42 nagios.qh

Ran these again today to make sure it was on the right host as I had most of our nagios instance open. Looks like I might have ran them on either our prod instance.

The type and ownership of nagios.cmd is wrong. That should be a pipe owned by nagios:

Code: Select all

prw-rw----. 1 nagios nagcmd 0 Jun 20 10:28 nagios.cmd

Delete that file and restart Core:

Code: Select all

rm /usr/local/nagios/var/rw/nagios.cmd
service nagios restart

Deleted file, and restarted nagios. Ran this again: ll /usr/local/nagios/var/rw/

Code: Select all

ll /usr/local/nagios/var/rw/
total 0
prw-rw---- 1 nagios nagcmd 0 Jun 23 11:29 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 Jun 23 11:29 nagios.qh

so still looks similar( except not owned by apache). Are you saying I need to change ownership from nagcmd to nagios on nagios.cmd or does that look correct?

Still having the same problem after deleting proposed file and restarting.

[sreinhardt]

Your permissions are fine now, being nagios:nagios or nagios:nagcmd is just fine. The big difference is the p or command pipe at the very start of the permissions. It seems that something in XI is attempting to write to the command file while it doesn't exist, and instead is creating a new one as text and not a pipe. Just to be sure we are 100% on the same page. If you:

Code: Select all

restart nagios core
list the command file and make sure it has the p flag
force an immidiate check

Does this work? If so, does applying config change the nagios.cmd file back to non-pipe?

[[email protected]]

Your permissions are fine now, being nagios:nagios or nagios:nagcmd is just fine. The big difference is the p or command pipe at the very start of the permissions. It seems that something in XI is attempting to write to the command file while it doesn't exist, and instead is creating a new one as text and not a pipe. Just to be sure we are 100% on the same page. If you:

Code: Select all

restart nagios core
list the command file and make sure it has the p flag
force an immidiate check

Does this work? If so, does applying config change the nagios.cmd file back to non-pipe?

No, that does not work. Restarting doesn't change the file and still can't do an immediate check after.

[lmiltchev]

I am locking this thread as you have a ticket open in our ticketing system, and it would be easier to follow it in one place. We will continue communication via emails.