Let's say you are unable to start the Nagios Network Monitoring service after reboot.

First of all, check your var/log/messages log file.

$ sudo cat var/log/messages

$ less installed-rpms | grep nagios

$ sudo cat /etc/nagios/nagios.cfg
lock_file=/var/run/nagios/nagios.pid

This is the lockfile that Nagios will use to store its PID number in when it is running in daemon mode.

 

If the lock_file parameter was set to “/var/run/nagios/nagios.pid“ in “/etc/nagios/nagios.cfg“, edit the file and set the “lock_file” parameter to point to a directory where data is persistent across reboot.

Change the lock_file parameter from “/var/run/nagios/nagios.pid” to “/nagios/nagios.pid”.

Try restarting the service again.

sudo systemctl restart nagios.service
Je li Vam ovaj odgovor pomogao? 0 Korisnici koji smatraju članak korisnim (0 Glasovi)

Najpopularnije

How To Access cPanel/WHM Via Command Line As The Root User

It is true that cPanel & WHM automates many of the server administration tasks that you may...
How To Resolve Empty cPanel CPU/Concurrent Usage Snapshot

When a CloudLinux user hits LVE limits, appropriate faults are generated and lvestats package...
How To Implement cPanel Firewalls On AWS & Google Cloud

If you are using a public cloud such as AWS, Google Cloud Platform, Microsoft Azure, Alibabacloud...
How To Check Your cPanel & WHM Server Ports As An Admin

For a Linux instance, follow these steps to verify the security group rule: Connect to a Linux...
How To Check cPanel Log Files With Location and Description

First of all, some of these locations do change as cPanel release new versions. If you are...