systemctl start nagios.service
Job for nagios.service failed because a configured resource limit was exceeded. See "systemctl status nagios.service" and "journalctl -xe" for details.
[root@splab-nagios tmp]# systemctl status nagios.service
● nagios.service - Nagios Network Monitoring
Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
Active: failed (Result: resources) since Tue 2016-11-15 14:45:52 EST; 14s ago
Docs:
https://www.nagios.org/documentation/
Process: 27588 ExecStart=/usr/sbin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 27586 ExecStartPre=/usr/sbin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Nov 15 14:45:52 splab-nagios systemd[1]: Starting Nagios Network Monitoring...
Nov 15 14:45:52 splab-nagios systemd[1]: PID file /var/run/nagios/nagios.pid not readable (yet?) after start.
Nov 15 14:45:52 splab-nagios systemd[1]: nagios.service never wrote its PID file. Failing.
Nov 15 14:45:52 splab-nagios systemd[1]: Failed to start Nagios Network Monitoring.
Nov 15 14:45:52 splab-nagios systemd[1]: Unit nagios.service entered failed state.
Nov 15 14:45:52 splab-nagios systemd[1]: nagios.service failed.
This is what happened after I downloaded and recompiled nagios 4.2.2