Hi Jeremy, since I'm also out of ideas right now (something *is* wrong with the list of cluster nodes in Graylog2 but finding the culprit will probably take some time…) reinstalling the Graylog2 server might just be the easier way of resolving this. :(
Am Freitag, 7. November 2014 15:26:54 UTC+1 schrieb Jeremy Farr: > > I can install from the repos for ease of future release install and just > simply "attach" the new Graylog2 instance to my mongo db and my > elasticsearch cluster. > I'm afraid this wouldn't solve the problems. Graylog2 doesn't store data outside of MongoDB and Elasticsearch and I suspect some rogue document in MongoDB to cause these errors in your installation. > I'll have to use Graylog2 0.90.3 as my elasticsearch cluster is still > version 0.90.x. Is there a "best practice" to this? Does the node id on > the replacement install need to be the same as the legacy Graylog2 server > instance? > The node ID is used to determine which inputs have been started (or should be started) on a particular cluster node among other things. It doesn't have to be the same on the new Graylog2 node but you will have to re-create the inputs (and their extractors) if it's not the same. Cheers, Jochen -- 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.
