Hey Will, I'm seeing the same issue in my Graylog2 instance. Did you find the root cause back when you posted this? Did your increase of RAM lead to the issue going away?
I'd appreciate any pointers. Thanks! On Thursday, 24 April 2014 06:29:48 UTC+5:30, [email protected] wrote: > > Hello, > > I have a a Graylog2 server (with ES on the same VM) when I look at the > system tab I see a large number of indexing errors: > *"There were 40,993 failed indexing attempts in the last 24 hours"* > > When I click the "Show errors" button I get an "Oh no, something went > wrong!" page with reason: > "Could not get indexer failures. We expected HTTP 200, but got a HTTP 500." > > This is what I see in the Graylog2 log: > > 2014-04-23 17:50:52,954 ERROR: > org.graylog2.plugin.rest.AnyExceptionClassMapper - Unhandled exception in > REST resource > com.mongodb.MongoException: Runner error: Overflow sort stage buffered > data usage of 33554455 bytes exceeds internal limit of 33554432 bytes > > It is part of a much larger message that I can post if necessary. Any > ideas why I can't see the indexer errors? > > OS: Red Hat Enterprise Linux Server release 6.5 (Santiago) > RAM: 4G (trying to get more) > CPU: 4x cores > Log partition: 2TB > Java: 1.7.0_55 > ES: "0.90.13 > MongoDB: v2.6.0 > Graylog: 0.20.1 > > Thanks!! > > --Will > > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
