欢迎来到之路教程(on itroad-com)
解决方案
在文件“/etc/nagios/nagios.cfg”中,lock_file 参数设置为“/var/run/nagios/nagios.pid”。
在 CentOS/RHEL 中,不建议写入 /var/run,因为 /var/run 通常挂载为 tmpfs,它是映射到 内存 的分区。
显然 内存 在重新启动时会被清除,所有 tmpfs 文件系统也是如此。
因此,找不到文件“/var/run/nagios/nagios.pid”。
# cat /etc/nagios/nagios.cfg lock_file=/var/run/nagios/nagios.pid
在 /etc/nagios/nagios.cfg 中,“lock_file”参数应该指向一个目录,在该目录中数据在重启后是持久的。
这是 Nagios 在守护进程模式下运行时用来存储其 PID 号的锁文件。
将 lock_file 参数从“/var/run/nagios/nagios.pid”更改为“/nagios/nagios.pid”。
保存更改并重新启动“nagios”服务。
问题
CentOS/RHEL系统重新启动后无法启动 Nagios 网络监控服务。
-- var/log/messages --- Jan 6 09:14:28 [hostname] nagios: Checking global event handlers... Jan 6 09:14:28 [hostname] nagios: Checking obsessive compulsive processor commands... Jan 6 09:14:28 [hostname] nagios: Checking misc settings... Jan 6 09:14:28 [hostname] nagios: Total Warnings: 0 Jan 6 09:14:28 [hostname] nagios: Total Errors: 0 Jan 6 09:14:28 [hostname] nagios: Things look okay - No serious problems were detected during the pre-flight check Jan 6 09:14:28 [hostname] nagios: Failed to obtain lock on file /var/run/nagios/nagios.pid: No such file or directory Jan 6 09:14:28 [hostname] nagios: Bailing out due to errors encountered while attempting to daemonize... (PID=9029) Jan 6 09:14:28 [hostname] systemd: nagios.service: control process exited, code=exited status=254 Jan 6 09:14:28 [hostname] systemd: Failed to start Nagios Network Monitoring. Jan 6 09:14:28 [hostname] systemd: Unit nagios.service entered failed state. Jan 6 09:14:28 [hostname] systemd: nagios.service failed.
$ less installed-rpms | grep nagios nagios-4.3.4-3.el7.x86_64 Mon Nov 18 14:30:00 2019 nagios-common-4.3.4-3.el7.x86_64 Mon Nov 18 14:29:59 2019
日期:2020-09-17 00:16:44 来源:oir作者:oir