Just as the title says. Ran through all documents I could find via search. Let me know what to provide to help resolve. Thank you.
It's best to default to providing as much info as you can - logs, OS info, the steps you followed to upgrade.
Please also format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you 
I am very new trying to figure this out. Sorry for my ignorance. This is a Redhat 7.5 Enterprise. I followed the path on the site which was to shutdown the elastic service, install the new software via YUM. It detected that it was to upgrade and completed successfully. All the yml files seem to be correct. The only log file that seems to update when trying to start it is the gc.log. I noticed in the elasticsearch.log got a boot strap error, but I do have the cluster.initail_master_nodes in the yml file.
[1] bootstrap checks failed
[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured
The message is really indicating that this setting isn't there. Are you sure you've set it in the right file? Are you sure it's spelled correctly (there's a typo in your post).
If you introduce a bogus setting in this file, e.g. not.a.setting: "bogus" do you get this kind of error?
java.lang.IllegalArgumentException: unknown setting [not.a.setting] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:531) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:476) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:447) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:418) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:148) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.node.Node.<init>(Node.java:341) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.node.Node.<init>(Node.java:251) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:211) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:211) ~[elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:325) [elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) [elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) [elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) [elasticsearch-cli-7.0.0.jar:7.0.0]
at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-7.0.0.jar:7.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115) [elasticsearch-7.0.0.jar:7.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) [elasticsearch-7.0.0.jar:7.0.0]
If not, you're not editing the right file.
Searching the system I only have one log file at /var/log/elasticsearch/elasticsearch.log
and one yml file /etc/elasticsearch/elasticsearch.yml. There is only one service installed. Nothing shows up in the elastisearch.log any longer. gc.log is the only file that updates and that does not seem to provide anything. I have renamed the yml file and try to start the service and nothing happens.
Sorry, I'm not too knowledgeable about how things are installed with yum, nor how to find out what it's done or where it's put everything. If it's not logging anything then it sounds like it's not properly installed: Elasticsearch always logs something shortly after starting.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.