Nagios log file is not rotating in daily basis

[breddydu]

Hello,

Thank you for your reply.

We have killed all the process yesterday and today we have observed that after restarting the Nagios old process are not getting cleared and new process are creating ever time after restarting Nagios .

Once we restart the Nagios service log file is getting updated and it is having the past data as well , actually it has to be archived and fresh data should be created .

Size of the file is getting increased day by day .

[lmiltchev]

We have killed all the process yesterday and today we have observed that after restarting the Nagios old process are not getting cleared and new process are creating ever time after restarting Nagios .

You are running a very old version of Nagios Core (4.1.1). There was in issue in this version of Core, where nagios sometimes gets started with different process ID. The issue was fixed in 4.2.0.

Fixed init script to wait up to 90 seconds then kill the nagios process (John Frickson)

https://github.com/NagiosEnterprises/na ... /Changelog

I would recommend that you upgrade to the latest version of Nagios Core (4.4.5) in order to fix the issue.

[breddydu]

Hello ,

We have cleared all the process and started the Nagios , After that everday once we restr the nagios service to start the log file rotation manually (as it is not automatically rotating ), we can see a new process is starting again.

As we are using on all the managed servers we cannot stop the check_mk , as if it stops there will be no monitoring.

Please let us know if we can resolve this in any other way .

[benjaminsmith]

Hello @breddydu,

You would have to upgrade to a later version of Core for the patch. Do you have a test server setup? We always recommend making changes in a test environment before rolling out to the production server.

[breddydu]

Hello Team,

We are not in position to upgrade the core version, is there any possibility in helping us in resolving the issue.

Due to this we are not able to get the availability report .

In the archives and in the var drives we can see that the data is not rotating and appending in to single file .


drwxr-xr-x 3 root root 4.0K May 2 2016 spool
lrwxrwxrwx 1 root root 24 Jul 18 2016 archives -> /var/log/nagios/archives
-rw-r--r-- 1 nagios nagios 3.0M Jan 8 08:47 objects.precache
-rw-r--r-- 1 nagios nagios 2.7K Jan 8 08:47 nagios.configtest
-rw------- 1 nagios nagios 4.7M Jan 8 08:47 retention.dat
-rw-r--r-- 1 nagios nagios 6 Jan 8 08:47 nagios.lock
-rw-r--r-- 1 nagios nagios 3.0M Jan 8 08:47 objects.cache
drwxrwsr-x 2 nagios nagcmd 4.0K Jan 8 08:47 rw
-rw-r--r-- 1 nagios nagios 21G Jan 8 08:50 nagios.log
-rw-rw-r-- 1 nagios nagios 4.7M Jan 8 08:50 status.dat
-rw-r--r-- 1 nagios nagios 11G Jan 8 08:50 service-perfdata.out
-rw-r--r-- 1 nagios nagios 28G Jan 8 08:50 host-perfdata.out

---------------------------------------------------------------------------------------------------------------------------
-rw-r--r-- 1 nagios nagios 1.2G Dec 1 00:00 nagios-12-01-2019-00.log
-rw-r--r-- 1 nagios nagios 1.2G Dec 2 00:00 nagios-12-02-2019-00.log
-rw-r--r-- 1 nagios nagios 1.2G Dec 3 00:00 nagios-12-03-2019-00.log
-rw-r--r-- 1 nagios nagios 1.2G Dec 4 00:00 nagios-12-04-2019-00.log
-rw-r--r-- 1 nagios nagios 1.6G Dec 5 00:00 nagios-12-05-2019-00.log
-rw-r--r-- 1 nagios nagios 0 Dec 5 23:59 nagios-12-06-2019-00.log
-rw-r--r-- 1 nagios nagios 0 Dec 6 23:59 nagios-12-07-2019-00.log
-rw-r--r-- 1 nagios nagios 0 Dec 7 23:59 nagios-12-08-2019-00.log
-rw-r--r-- 1 nagios nagios 0 Dec 9 00:00 nagios-12-09-2019-00.log
-rw-r--r-- 1 nagios nagios 3.5G Dec 12 08:13 nagios-12-12-2019-00.log
-rw-r--r-- 1 nagios nagios 3.5G Dec 12 08:13 nagios-12-10-2019-00.log
-rw-r--r-- 1 nagios nagios 8.2G Dec 18 08:06 nagios-12-15-2019-00.log
-rw-r--r-- 1 nagios nagios 8.2G Dec 18 08:06 nagios-12-13-2019-00.log
-rw-r--r-- 1 nagios nagios 8.2G Dec 18 08:06 nagios-12-14-2019-00.log
-rw-r--r-- 1 nagios nagios 8.2G Dec 18 08:06 nagios-12-17-2019-00.log
-rw-r--r-- 1 nagios nagios 8.2G Dec 18 08:07 nagios-12-18-2019-00.log
-rw-r--r-- 1 nagios nagios 9.0G Dec 19 08:26 nagios-12-19-2019-00.log
-rw-r--r-- 1 nagios nagios 12G Dec 23 10:35 nagios-12-21-2019-00.log
-rw-r--r-- 1 nagios nagios 12G Dec 23 10:35 nagios-12-20-2019-00.log
-rw-r--r-- 1 nagios nagios 12G Dec 23 10:35 nagios-12-23-2019-00.log
-rw-r--r-- 1 nagios nagios 14G Dec 27 09:33 nagios-12-24-2019-00.log
-rw-r--r-- 1 nagios nagios 14G Dec 27 09:34 nagios-12-25-2019-00.log
-rw-r--r-- 1 nagios nagios 15G Dec 30 08:13 nagios-12-28-2019-00.log
-rw-r--r-- 1 nagios nagios 16G Dec 31 11:35 nagios-12-31-2019-00.log
-rw-r--r-- 1 nagios nagios 17G Jan 2 08:35 nagios-01-01-2020-00.log
-rw-r--r-- 1 nagios nagios 17G Jan 3 08:11 nagios-01-03-2020-00.log
-rw-r--r-- 1 nagios nagios 19G Jan 6 08:30 nagios-01-04-2020-00.log
-rw-r--r-- 1 nagios nagios 20G Jan 7 08:32 nagios-01-07-2020-00.log
-rw-r--r-- 1 nagios nagios 21G Jan 8 08:19 nagios-01-08-2020-00.log

From the each date data is appending in to archive files . Is there any other way we can get the availability report through web console .
Please let me know if we can have a web ex session in resolving this issue .

[benjaminsmith]

Hello,

We are not in a position to upgrade the core version, is there any possibility in helping us in resolving the issue.

If we've patched a bug in a later version, you'll have to upgrade to resolve. If you are not able to upgrade the production server, I would suggest setting up a new system and then migrate.