Not starting Elasticsearch for some reason I can't undestand

Elastic Stack Elasticsearch
1

Hi,

I'm new with this software and I had installed 6.5.0 version months ago, but, when I tried to update I had problems, so I reset the CentOS 7 machine and try it again with this 7.0.0 version. I could make everything work except for Logstash and elasticsearch for some reasons I don't understand. I search for a solution on the internet but can't find a solution for this so, I finally came here for you.

Here you have what the machine say about this.....

systemctl status elasticsearch logstash:

● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since mar 2019-04-16 13:39:55 CEST; 56min ago
     Docs: http://www.elastic.co
  Process: 18614 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=78)
 Main PID: 18614 (code=exited, status=78)

abr 16 13:39:30 srvelesticsearch.Hikari.local systemd[1]: Started Elasticsearch.
abr 16 13:39:30 srvelesticsearch.Hikari.local elasticsearch[18614]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed ...e release.
abr 16 13:39:55 srvelesticsearch.Hikari.local systemd[1]: elasticsearch.service: main process exited, code=exited, status=78/n/a
abr 16 13:39:55 srvelesticsearch.Hikari.local systemd[1]: Unit elasticsearch.service entered failed state.
abr 16 13:39:55 srvelesticsearch.Hikari.local systemd[1]: elasticsearch.service failed.

● logstash.service - logstash
   Loaded: loaded (/etc/systemd/system/logstash.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since mar 2019-04-16 13:39:32 CEST; 57min ago
  Process: 18737 ExecStart=/usr/share/logstash/bin/logstash --path.settings /etc/logstash (code=exited, status=1/FAILURE)
 Main PID: 18737 (code=exited, status=1/FAILURE)

abr 16 13:39:31 srvelesticsearch.Hikari.local systemd[1]: logstash.service: main process exited, code=exited, status=1/FAILURE
abr 16 13:39:31 srvelesticsearch.Hikari.local systemd[1]: Unit logstash.service entered failed state.
abr 16 13:39:31 srvelesticsearch.Hikari.local systemd[1]: logstash.service failed.
abr 16 13:39:32 srvelesticsearch.Hikari.local systemd[1]: logstash.service holdoff time over, scheduling restart.
abr 16 13:39:32 srvelesticsearch.Hikari.local systemd[1]: Stopped logstash.
abr 16 13:39:32 srvelesticsearch.Hikari.local systemd[1]: start request repeated too quickly for logstash.service
abr 16 13:39:32 srvelesticsearch.Hikari.local systemd[1]: Failed to start logstash.
abr 16 13:39:32 srvelesticsearch.Hikari.local systemd[1]: Unit logstash.service entered failed state.
abr 16 13:39:32 srvelesticsearch.Hikari.local systemd[1]: logstash.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

view /var/log/elasticsearch/elasticsearch.log

[2019-04-16T13:39:54,965][INFO ][o.e.n.Node               ] [srvelesticsearch.Hikari.local] initialized
[2019-04-16T13:39:54,966][INFO ][o.e.n.Node               ] [srvelesticsearch.Hikari.local] starting ...

[2019-04-16T13:39:55,297][INFO ][o.e.t.TransportService   ] [srvelesticsearch.Hikari.local] publish_address {10.254.214.145:9300}, bound_addresses {10.254.214.145:9300}
[2019-04-16T13:39:55,312][INFO ][o.e.b.BootstrapChecks    ] [srvelesticsearch.Hikari.local] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2019-04-16T13:39:55,315][ERROR][o.e.b.Bootstrap          ] [srvelesticsearch.Hikari.local] node validation exception
[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
[2019-04-16T13:39:55,394][INFO ][o.e.n.Node               ] [srvelesticsearch.Hikari.local] stopping ...
[2019-04-16T13:39:55,512][INFO ][o.e.n.Node               ] [srvelesticsearch.Hikari.local] stopped
[2019-04-16T13:39:55,513][INFO ][o.e.n.Node               ] [srvelesticsearch.Hikari.local] closing ...
[2019-04-16T13:39:55,616][INFO ][o.e.n.Node               ] [srvelesticsearch.Hikari.local] closed

And I think that's all, I know it can be very newbie question or whatever, but I really don't understand this issue, I have even tried to update java, but nothing seems to be solved....

2

You are binding to 10.254.214.145 which is not localhost, so you are in production mode:

However, your node configuration is not suitable for production use:

If this is a production deployment, you should set one of these settings. If this is a test deployment only then you can either bind to localhost or else use single-node discovery to avoid the bootstrap checks.

3

Okay, thank you so much! I'll search about production mode and this, I had no idea this exists...

4

Here's the blog post about the introduction of bootstrap checks, explaining the rationale:

The page I linked above also has some more details.

1 Like
5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.