/var/lib/rabbitmq/ rabbitmq:rabbitmq
/var/lib/rabbitmq/data root:root 027 umask: rwxr-x---
so the
/usr/local/lib/nagios/plugins/check_rabbitmq_queues.py -c \* \* 100 200 /var/lib/rabbitmq/data/juju*_queue_stats.dat
check fails (/etc/nagios/nrpe.d/check_rabbitmq_queue.cfg)
1.) why data is owned by root:root, when rabbitmq's home folder (/var/lib/rabbitmq) is owned by rabbitmq:rabbitmq?
2.) when running CIS, that sets the umask to 027. This breaks the ability to read the stats by others.
The /var/lib/rabbitmq/data folder + stats should not be owned by root (along with possibly the /var/lib/rabbitmq/logs folder), but by the rabbitmq user. But that still would not allow nagios to read the stats file, maybe by adding nagios to the rabbitmq group.
/var/lib/rabbitmq/ rabbitmq:rabbitmq rabbitmq/ data root:root 027 umask: rwxr-x--- lib/nagios/ plugins/ check_rabbitmq_ queues. py -c \* \* 100 200 /var/lib/ rabbitmq/ data/juju* _queue_ stats.dat nrpe.d/ check_rabbitmq_ queue.cfg)
/var/lib/
so the
/usr/local/
check fails (/etc/nagios/
1.) why data is owned by root:root, when rabbitmq's home folder (/var/lib/rabbitmq) is owned by rabbitmq:rabbitmq?
2.) when running CIS, that sets the umask to 027. This breaks the ability to read the stats by others. rabbitmq/ data folder + stats should not be owned by root (along with possibly the /var/lib/ rabbitmq/ logs folder), but by the rabbitmq user. But that still would not allow nagios to read the stats file, maybe by adding nagios to the rabbitmq group.
The /var/lib/