Nagios Support Forum

Logserver-01 refused connections on port 3515 around 5am GMT+8.

Not sure if it's still a RAM issue causing this.

Could we turn this into an official ticket with Support?

I've now turned off optimization on all my clusters and they are all running at 32GB fo RAM.

Will keep an eye and see if i have further issues.

Thanks!

I'm not sure if they're turned off on that particular cluster. Let me re-check as this cluster has been relatively fuss-free.

One of my US log servers port 3515 refused connections this morning.

Looks like it's another memory issue again but confirmation would be great.

Will do.

Thanks!

I think I might have made a bit of a mess with the logs.I turned on optimization again just to see what would happen last week and it went kaput. This log-server is a bit different to the rest of my other clusters as it is also logging for another site nearby. Perhaps this site requires 32GB RAM ins...

Output as below: repo.png root@hs3-log-01 ~]# curator --loglevel warn show snapshots --repository SharedBackupRepo --newer-than 25 --time-unit hours 2017-06-29 11:20:16,516 ERROR No snapshots found in Elasticsearch. No snapshots found in Elasticsearch. [root@hs3-log-01 ~]# [root@hs3-log-01 ~]# curl ...

Two weeks before it started dying again. I'm hitting 70% RAM usage before it decides to quit and roll-over.

Perhaps I should reduce indices to 20 days? Or less?

Hi Support, Am not quite sure where to post this but it looks like my Nagios XI is showing some backup snapshot alerts for my Log Server cluster. Strange this is that I'm looking at Nagios Log Server and the backup snapshot was run successfully. This is occurring across two datacentres. Where do I s...

I set indices to close after 30 days, will monitor for now.