Nagios Support Forum

When I try to run a delete it says: {"error":"ConcurrentSnapshotExecutionException[[FreeNAS:curator-20190601180154] another snapshot is currently running cannot delete]","status":503}[

Should I keep trying to utilize this Repo or create another one?

I have added a Snapshot Repository via CIFS. Both systems in the clusters can see it and write to it. However in my Snapshot status I get the following: logstash-2020.11.17 IN_PROGRESS 2020-11-18 15:57:58 - 1969-12-31 18:00:00 1.7.6 It doesn't appear the system is processing snapshots correctly can ...

Since my upgrade the 2.1.5 the java processes have been running high and consuming a lot of memory. Also, no logs are being collected. I've checked the iptables firewall and it's config has not changed. I can logon to the web interface of Nagios Log Server but that is it. Nothing I can find in /var/...

Thanks, my fault, should have checked that first. Found a few of the ports wouldn't open properly. Fixed that and it's working.

The Logstash Collector keeps stopping and will not start after I restart it.

The Logstash service is stopping on the server. I can restart it but it will fail again in less than 5 minutes. Looked in the /var/logs/logstash.log and I see this entry: {:timestamp=>"2015-08-18T15:39:17.899000-0500", :message=>"retrying failed action with response code: 503", :...

It's a single node in the cluster.

Ok, thanks. Let's see where we get and we'll go from there. Index page attached.

Ok removed the index. Waited a few hours and the cluster status is still yellow. Plus it will grab events for a short period and then stop. Screen shots are attached. Should I just cut my losses at this point, backup my dashboards, input filters, queries, etc and start over?

It looks like it might be the latest index 3-30-15. Am I reading this correctly? curl -XGET 'http://localhost:9200/_cluster/health/*?level=shards' {"cluster_name":"3c75d8ce-06b4-409c-b5b7-1f834a9db496","status":"red","timed_out":false,"number_of...