I previously removed the leading whitespaces, it didn't make any difference.
I installed ES from the steps listed in the Graylog documentation for CentOS. It was install via RPM. Per the init script, it's pulling the /etc/elasticsearch/ folder for the configuration location. Which is where the elasticsearch.yml file I'm editing is located. That is also the only elasticsearch.yml on the system, and other settings I've edited there previously did take effect. At this point, it's tempting to just blow away the VM and rebuild it from scratch. But it's really frustrating. If I run into weird problems like this, is it something I want to deal with in a production setting? Nathan On Wednesday, August 3, 2016 at 10:18:15 AM UTC-4, Jochen Schalanda wrote: > > Hi Nathan, > > On Wednesday, 3 August 2016 16:10:55 UTC+2, Nathan Mace wrote: >> >> I'm editing /etc/elasticsearch/elasticsearch.yml. That has to be the >> correct file, right? I mean, node 2 doesn't have anything installed >> besides ElasticSearch, so what other config file would there be to edit? >> > > This totally depends on how you've installed Elasticsearch and how you're > starting it. The command line used to start ES might give some hints (check > `ps -ef | grep java` for the Elasticsearch processes). > > If you haven't removed the leading whitespace in your Elasticsearch > configuration files yet, this would be a good chance. Just to make sure… > > Cheers, > Jochen > -- 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/722df39d-ad69-4611-a7d2-f488e7b811c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
