Nagios Support Forum

Install Nagios core on a Centos 7 server and the client also Centos 7. On the client I can't seem to start the NRPE services
error message from journalctl -xe:
The result is failed.
Aug 12 08:40:39 localhost.localdomain systemd[1]: Unit nrpe.service entered failed state.
Aug 12 08:40:39 localhost.localdomain systemd[1]: nrpe.service failed.
Aug 12 08:40:39 localhost.localdomain dbus-daemon[700]: dbus[700]: [system] Activating service name='org.fedorap
Aug 12 08:40:39 localhost.localdomain dbus[700]: [system] Activating service name='org.fedoraproject.Setroublesh
Aug 12 08:40:40 localhost.localdomain dbus[700]: [system] Successfully activated service 'org.fedoraproject.Setr
Aug 12 08:40:40 localhost.localdomain dbus-daemon[700]: dbus[700]: [system] Successfully activated service 'org.
Aug 12 08:40:40 localhost.localdomain polkitd[15514]: Unregistered Authentication Agent for unix-process6
Aug 12 08:40:40 localhost.localdomain dbus-daemon[700]: 'list' object has no attribute 'split'
Aug 12 08:40:40 localhost.localdomain setroubleshoot[20852]: Plugin Exception restorecon_source
Aug 12 08:40:40 localhost.localdomain setroubleshoot[20852]: SELinux is preventing /usr/sbin/nrpe from open access on the file /etc/nagios/nrpe.cfg[/color]
Aug 12 08:40:40 localhost.localdomain python[20852]: SELinux is preventing /usr/sbin/nrpe from open access on th

***** Plugin restorecon (99.5 confidence) suggests *****

If you want to fix the label.
/etc/nagios/nrpe.cfg default label should be nrpe_etc_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /etc/nagios/nrpe.cfg

***** Plugin catchall (1.49 confidence) suggests *******

If you believe that nrpe should be allowed open access on t
Then you should report this as a bug.
You can generate a local policy module to allow this access
Do
allow this access for now by executing:
# grep nrpe /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

All help appreciated

Is disabling SELinux or at least putting it in "permissive" mode an option for you? The reason I am asking this is because this is going to be the easiest way to fix your issue. FYI, SELinux configuration is out of the scope of Nagios support. What is the output of the following command?

I had to flatten it in the end and start from scratch. And now I don't seem to get this error message no more

Are we good to mark this thread as resolved then?