Nagios Support Forum

I have a repository setup to hold our snapshots for long term storage. up to August they have been writing to the repository no problems. When I went to do our quarterly restore verification, I noticed that all the snapshots have been IN_PROGRESS and have not completed and I do not see any new indices listed in the repository. Nothing has changed in over a year on the repository. It is currently setup as an NFS share with root access to write to it.

My questions are

• Where in the logs can I see what is causing this on the nagioslog server?

• how can I clear these IN_PROGRESS snapshots? as the system has already removed the indicies as its setup to remove them after 14 days.

• how do I fix this from happening some more?

Thanks,
Joe H

In 2024R1.1 (released on July 16) there were Python changes surrounding the curator script (and others) to use venv's. Depending on when you upgraded to R1.1 this may be related to your problem.

A couple of things to try. First run the curator script and share the output from it:
Any logs related to the index snapshots will be in /var/www/html/nagioslogserver/application/logs/

You may have to turn the log level up to see them
in /var/www/html/nagioslogserver/application/config/config.php. The messages related to the snapshots will be tagged with BACKUP (all caps).

Let us know the results of this and we can look further into it.

when I run the curator script its seems to execute. I am not supplying any of the switches not sure which ones to apply but I does not fail with any errors just provides all the options you can apply to it. I have changed the logging level and let it run yesterday, I will collect the logs and attach what I can shortly.

Thank you for your response,
Joe H

Were there any logs relating to the snapshots after upping the logging level? If not you may have to contact phone support for a deeper investigation on this.

Hi,
Sorry this is so late. After digging in the logs. there was nothing specifically related to the SNAPSHOTS.

Thanks,
Joe H

Unfortunately then, I think you might have to open a support ticket on this.