group ownership of nagios.cmd

[jssingh]

We have 2 instances of nagios with the same setup. On both of them nagios.cmd is owned by the nagios user and the group is the group with the nrdp user and the nagios user.

On one system (the production system), when I restart nagios it changes the group to the default group for the nagios user, but on the other system it keeps the group the same. So obviously there is something different between the two systems, but I can't figure out what it is. Does anyone know what settings would cause this behavior?

[rkennedy]

I believe this is from when you first configured Core, and appended the --with-command-group=<user>. On the Core system I'm running for example, I used the 'nagcmd' user, and that's what it defaults to after a restart as well.

Code: Select all

[root@localhost rw]# ls -l nagios.cmd
prw-rw---- 1 nagios nagcmd 0 May  6 15:12 nagios.cmd
[root@localhost rw]# chown nagios:nagios nagios.cmd
[root@localhost rw]# ls -l
total 0
prw-rw---- 1 nagios nagios 0 May  6 15:12 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 May  6 15:12 nagios.qh
[root@localhost rw]# service nagios restart
Restarting nagios (via systemctl):                         [  OK  ]
[root@localhost rw]# ls -l
total 0
prw-rw---- 1 nagios nagcmd 0 May 26 16:31 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 May 26 16:31 nagios.qh

[eloyd]

What he said. And I forget, ALL THE TIME, to use that argument when I'm building Core. Makes me scratch my head a lot until I remember, go reconfigure, recompile, and reinstall just so I can write stuff to nagios.cmd.

[jssingh]

Yeah, apparently I remembered to do it for one server and not the other!

[rkennedy]

No problem! Were you able to get this resolved then @jssingh?

[jssingh]

yes. thank you.