# Unable to start Elasticsearch 7.5 on RHEL 7
**URL:** https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244
**Category:** Elasticsearch
**Created:** [January 8, 2020, 2:24pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244 "2020-01-08T14:24:26Z")
**Posts on this page:** 17
**Page:** 1
### Author:  [@stressedsalmon](https://discuss.elastic.co/u/stressedsalmon)
#### Post date: [January 8, 2020, 2:24pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/1 "2020-01-08T14:24:26Z")
Hello,
I am having an issue running the elasticsearch service after installation. I have seen another article [here](https://discuss.elastic.co/t/unable-to-start-elasticsearch-cluster-on-centos7/207453) which was not answered. I am running into the same issue as the other user. Here are some log files:
Pastebin of elasticsearch log:
[https://pastebin.com/VhvdJmWE](https://pastebin.com/VhvdJmWE)
Pastebin of (default) /etc/elasticsearch/elasticsearch.yml:
[https://pastebin.com/X4zcRrzf](https://pastebin.com/X4zcRrzf)
Please let me know if this is an issue related to Java which it seems via the log file. I have tried many things and none of them seem to be working.
Regards
---
### Author:  [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [January 8, 2020, 5:34pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/2 "2020-01-08T17:34:22Z")
I think this is the breaking error:
> 2020-01-07T19:53:52,623][WARN][o.e.b.BootstrapChecks] [MachineName] 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
I think if you set node.name to a value, then use that value for discovery.seed\_hosts it should start.
---
### Author:  [@stressedsalmon](https://discuss.elastic.co/u/stressedsalmon)
#### Post date: [January 8, 2020, 6:41pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/3 "2020-01-08T18:41:09Z")
Hi Len,
Thank you for your response! I tried what you have mentioned but am still running into issues:
I updated the elasticsearch.yml file to define node.name as well as the discovery.seed\_hosts. for node.name I tried both the default "node-1" statement as well as the same entry I used for discovery.seed\_hosts (127.0.0.1) like so:
as well as:
The discovery.seed\_hosts is by default set to 127.0.0.1 which what I want but I defined it anyways as follows:
both failed with the output in the log as follows:
very strange that the service cannot start still...
Furthermore I tried installing this directly from the internet on another sandbox machine and it worked and started! The thing is for me to use this in a production environment it cannot be connected to the internet so my issue remains unresolved. I am thinking it might be installing some unmentioned dependencies when installing from the internet?? I am trying to install this locally from an .rpm file on a machine not connected to the internet so maybe its not installing those dependencies... not sure
Let me know if there is anything else I could try
Thanks!
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 8, 2020, 7:01pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/4 "2020-01-08T19:01:57Z")
FWIW for a one-node production cluster you can set `discovery.seed_hosts: []`. As long as you've set it to _something_ Elasticsearch will be happy.
The log message `stopping...` indicates that Elasticsearch was instructed to shut down cleanly by something external. On Linux that means it got something like a SIGTERM; I'm not sure exactly what the Windows equivalent is.
---
### Author:  [@elasticforme](https://discuss.elastic.co/u/elasticforme)
#### Post date: [January 8, 2020, 7:17pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/5 "2020-01-08T19:17:30Z")
> [@rugenl](#):
>
> cluster.initial\_master\_nodes
you have to define this first time.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 8, 2020, 7:17pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/6 "2020-01-08T19:17:53Z")
Oh wait we _are_ on Linux here. So yes, something outside Elasticsearch itself sent it a `SIGTERM`.
It is perhaps no coincidence that there's almost exactly 30 seconds between the first log message and the `stopping...`:
```auto
[2020-01-07T19:52:39,361][INFO][o.e.e.NodeEnvironment] [MachineName] using [1] data paths, mounts [[/var (/dev/mapper/rhel-var)]], net usable_space [31.8gb], net total_space [31.9gb], types [xfs]
...
[2020-01-07T19:53:09,640][INFO][o.e.n.Node] [MachineName] stopping ...
```
Maybe whatever is starting Elasticsearch up is waiting for some indication that the process is healthy and giving up after 30 seconds?
---
### Author:  [@stressedsalmon](https://discuss.elastic.co/u/stressedsalmon)
#### Post date: [January 8, 2020, 7:23pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/7 "2020-01-08T19:23:30Z")
Thank you for your responses guys! I have tried what you have mentioned and commented out the node.name field and set`discovery.seed_hosts: []` as below:
Tried to start the service and the same thing showed in the log:
I am confused why a SIGTERM is being sent as I am using systemctl to start the service and nothing external should be stopping it. I have it running smooth on an identical machine just connected to the internet so I am confident that no external program will be trying to shut it down..
very strange. I will try to define the `cluster.initial_master_nodes` next to see if anything changes but it seems to be something else.
Regards
---
### Author:  [@elasticforme](https://discuss.elastic.co/u/elasticforme)
#### Post date: [January 8, 2020, 7:27pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/8 "2020-01-08T19:27:48Z")
did you try to restart your linux system? may be some process has ran away.
---
### Author:  [@stressedsalmon](https://discuss.elastic.co/u/stressedsalmon)
#### Post date: [January 8, 2020, 7:32pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/9 "2020-01-08T19:32:19Z")
yes sir! also tried defining `cluster.initial_master_nodes` to no avail. Maybe I hit some sort of bug?
---
### Author:  [@elasticforme](https://discuss.elastic.co/u/elasticforme)
#### Post date: [January 8, 2020, 7:35pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/10 "2020-01-08T19:35:34Z")
by the cluster.initial\_master\_node is just one node entry
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 8, 2020, 7:49pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/11 "2020-01-08T19:49:03Z")
> [@stressedsalmon](#):
>
> I am confused why a SIGTERM is being sent as I am using systemctl to start the service and nothing external should be stopping it.
I think `systemd` does have a startup timeout. See if that's set to 30 seconds for this service and, if so, increase it to something more lenient.
---
### Author:  [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [January 8, 2020, 7:52pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/12 "2020-01-08T19:52:29Z")
You might check /var/log/messages or equivalent, maybe oom killer is getting it.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 8, 2020, 7:58pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/13 "2020-01-08T19:58:50Z")
> [@rugenl](#):
>
> maybe oom killer is getting it.
That wouldn't result in the process shutting down cleanly, as it is doing.
> [@elasticforme](#):
>
> > cluster.initial\_master\_nodes
>
> you have to define this first time.
This setting is not (yet) relevant. Let's focus on keeping the process alive first. We can worry about config like that later.
---
### Author:  [@elasticforme](https://discuss.elastic.co/u/elasticforme)
#### Post date: [January 8, 2020, 8:45pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/14 "2020-01-08T20:45:52Z")
david I still believe it is to do with setup. because I don't see anything is startup script about timeout
/usr/lib/systemd/system/elasticsearch.service
Stressesdsalmon, please post more log entry if you have it. since it started till it end.
---
### Author:  [@Ryne\_Keel](https://discuss.elastic.co/u/Ryne_Keel)
#### Post date: [January 9, 2020, 2:46pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/15 "2020-01-09T14:46:59Z")
Have you tried disabling SElinux? As David was mentioning tail journalctl -xe or /var/log/messages when you restart elasticsearch service to see if there is additional logging.
---
### Author:  [@stressedsalmon](https://discuss.elastic.co/u/stressedsalmon)
#### Post date: [January 9, 2020, 2:51pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/16 "2020-01-09T14:51:39Z")
Thank you all for your input I really do appreciate it! It seems like the issue resides with the systemd timeout like David mentioned. I set the timeout to 160sec, restarted after a successful install and attempted to start the service with systemd again. It worked!! I am getting an active running service now. It is still very strange to me that a internet connected machine is able to spin up the service in a shorter time frame than an offline machine. Nevertheless I am very glad I was able to get it going with all your help.
Thanks again!
Cheers!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 6, 2020, 2:51pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-7-5-on-rhel-7/214244/17 "2020-02-06T14:51:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.