Nagios Support Forum

We had some issues with running out of disk space in the past so I configured maintenance settings to close indexes older than 30 days and delete indexes older than 35 days. I may be misunderstanding how this works, but indexes don't seem to be closing or deleting. Today is May 15 and I still have all indexes open dating back to April 05 (first day of log collection since we experienced issues and started over). No indexes have been closed or deleted.

I also configured a snapshot repository. Both instances have access to the repository via NFS and have the share mounted to the exact same path. The nagios user has the same UIDs and GIDs across all instances and our NFS server. Snapshots are configured to be captured once daily but none have shown up. When I run the job manually from command subsystem menu, nothing happens. I'm been tailing /usr/local/nagioslogserver/var/jobs.log when running the job and only see lines like this:

tail: /usr/local/nagioslogserver/var/jobs.log: file truncated
Running command do_maintenance with args ' ' for job id: snapshots_maintenance

Any suggestions appreciated it. Thank you.

Can you send a screenshot of the command subsystem menu ?

Attached. The last and next run times are way off given the frequency setting, and when I run manually, nothing seems to happen.

Ok, it appears these jobs may all be stuck from something happening on or about 2/19 as they all think they are currently in a running state and have not updated since February.

Lets click the "Reset All Jobs" button at the top of the table.

then you are going to want to give it some time to finish. Some may take quite some time as they haven't ran for months.

That took care of it. Thanks for the help.

NSchoenbaechler wrote:That took care of it. Thanks for the help.

Glad to hear it is resolved.

Locking