Nagios Support Forum

We still get random stuff showing as down when we add the 10th instance back in This is a known issue with 1.4.2 that has been corrected for the next release. As rkennedy indicated, the issues you were experiencing were probably a lack of memory available for memory tasks. Good to hear that it's be...

I suspect it all has to do with the total amount of ram. Now that things are closing sooner this frees up quite a bit of it. How much data worth of logs do you have for the past 11 days now? Currently 1.9 Billion docs with a primary size of 1.1TB, and a total of 2TB We are still sitting at 9 instan...

Took a slightly different approach to this. Rather than just throw RAM at it, we decided to change our maint settings. Original was: Close indexes older than 16 days Delete indexes older than 17 days New settings: Close indexes older than 11 days Delete indexes older than 17 days Things seem to be w...

That should be fine especially if (at the transport layer) the events are being distributed among Logstash instances. Logstash doesn't require a particularly large heap. Usually, the first place Logstash runs into issues is related to the LS_OPEN_FILES directive. There's a different set of Java exc...

In my logstash config, I have the following custom setting: # Arguments to pass to java LS_HEAP_SIZE="2048m" LS_JAVA_OPTS="-Djava.io.tmpdir=$APP_DIR/tmp" I don't recall exactly what the default setting is, but the 2048m is NOT default - any issue there that you can see? *Edit: de...

I agree with rkennedy that running out of memory is probably the issue. Keep in mind that for each machine provisioned 32GB of memory, only half of that is being allocated to the regular storage tasks of elasticsearch. The other half is reserved for elasticsearch maintenance (and regular system) ta...

Each instance has 32GB allocated.

Interestingly, our Friday logs are gone (from about 10pm night before to about 6pm Friday Sept 16), but now the maint job seems to be working as expected since Monday night.
No changes, no reboots.

See attached GZ log file - i believe this should be what you were looking for

Attached txt files with sequential names matching each of the 3 commands