Thanks for the quick reply! Yes, I forgot to set multicast.enabled back to false after my testing yesterday - I was trying anything I could to try and get it functional again. I made some modifications to our multicast randevous points (sup 720 6500-E cisco routers) in our network late yesterday to try and accommodate elasticsearch's multicast discovery, that setting is simply residual from that. I've set it back to false and I still get the same problem. Here's the debug output after I set it to false: http://pastebin.com/TGMVKzxt Give me a few moments to try the IPV4 preference and I'll report back my findings. I'm going to put it on both elasticsearch and graylog's java wrapper.
About the elasticsearch_ prefixed settings from graylog2.conf. If I specify a config file, should I comment out all of the prefixed ones in graylog2.conf and rely only on the elasticsearch_config_file's settings? It's not explicitly documented, I assume the prefixed lines will override the config file's lines. An interesting problem I've also seen is discovery.zen.ping.timeout: 5s seems to not have any effect on graylog's elasticsearch client when it attempts to connect/find a cluster. It's always 3 seconds. I wonder if my ES master is too slow to respond? (I doubt that.) -- 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/groups/opt_out.
