Final resolution: I gave Graylog considerably more resources, including both memory and CPU cores. I cycled Elasticsearch and waited until it came green (looking at the curl output via the Elasticsearch API). Combined with pruning the number of indexes and forcing Graylog to recompute its ranges, this appears to have resolved the issue and Graylog has been stable for the past three days, with the only outage being caused by PG&E (Pray Gamble and Explode) managing to cut the power to our building for an hour without warning.
On Friday, March 25, 2016 at 2:32:08 PM UTC-7, Eric Green wrote: > > 2016-03-25T20:47:35.346Z WARN [IndexHelper] Couldn't find latest > deflector target index > org.graylog2.database.NotFoundException: Index range for index > <graylog2_185> not found. > > I cannot reach the 'indices' page for further information, so I attempted > to manually cycle via an API call. At which point I get: > > 2016-03-25T20:47:37.985Z ERROR [IndexRotationThread] Couldn't point > deflector to a new index > org.elasticsearch.ElasticsearchTimeoutException: Timeout waiting for task. > > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/bc8a6c8d-24b0-476c-b569-a8a6ad7c5797%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
