# Elasticsearch service won't run on new installation
**URL:** https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179
**Category:** Elasticsearch
**Created:** [June 30, 2019, 7:26am UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179 "2019-06-30T07:26:48Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@marcerickson](https://discuss.elastic.co/u/marcerickson)
#### Post date: [June 30, 2019, 7:26am UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/1 "2019-06-30T07:26:49Z")
System - Dell T310 32 GB RAM Ubuntu Server 18.04 with Xubuntu GUI added. Installation of GUI for Elasticsearch hasn't been done because the service won't stay running.
Tell me what else you need to troubleshoot my issue. I've been beating my heat against Google for about 6 hours now. Thank you.
> # ======================== Elasticsearch Configuration =========================
>
> #
>
> # NOTE: Elasticsearch comes with reasonable defaults for most settings.
>
> # Before you set out to tweak and tune the configuration, make sure you
>
> # understand what are you trying to accomplish and the consequences.
>
> #
>
> # The primary way of configuring a node is via this file. This template lists
>
> # the most important settings you may want to configure for a production cluster.
>
> #
>
> # Please consult the documentation for further information on configuration options:
>
> # [Elasticsearch Guide | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/index.html)
>
> #
>
> # ---------------------------------- Cluster -----------------------------------
>
> #
>
> # Use a descriptive name for your cluster:
>
> #
>
> #cluster.name: my-application
>
> #
>
> # ------------------------------------ Node ------------------------------------
>
> #
>
> # Use a descriptive name for the node:
>
> #
>
> #node.name: node-1
>
> #
>
> # Add custom attributes to the node:
>
> #
>
> #node.attr.rack: r1
>
> #
>
> # ----------------------------------- Paths ------------------------------------
>
> #
>
> # Path to directory where to store the data (separate multiple locations by comma):
>
> #
>
> path.data: /var/lib/elasticsearch
>
> #
>
> # Path to log files:
>
> #
>
> path.logs: /var/log/elasticsearch
>
> #
>
> # ----------------------------------- Memory -----------------------------------
>
> #
>
> # Lock the memory on startup:
>
> #
>
> #bootstrap.memory\_lock: true
>
> #
>
> # Make sure that the heap size is set to about half the memory available
>
> # on the system and that the owner of the process is allowed to use this
>
> # limit.
>
> #
>
> # Elasticsearch performs poorly when the system is swapping the memory.
>
> #
>
> # ---------------------------------- Network -----------------------------------
>
> #
>
> # Set the bind address to a specific IP (IPv4 or IPv6):
>
> #
>
> ```
> network.host: 192.168.1.252
>
> ```
>
> #
>
> # Set a custom port for HTTP:
>
> #
>
> ```
> http.port: 9200
>
> ```
>
> #
>
> # For more information, consult the network module documentation.
>
> #
>
> # --------------------------------- Discovery ----------------------------------
>
> #
>
> # Pass an initial list of hosts to perform discovery when new node is started:
>
> # The default list of hosts is ["127.0.0.1", "[::1]"]
>
> #
>
> #discovery.zen.ping.unicast.hosts: ["host1", "host2"]
>
> #
>
> # Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
>
> #
>
> #discovery.zen.minimum\_master\_nodes:
>
> #
>
> # For more information, consult the zen discovery module documentation.
>
> #
>
> # ---------------------------------- Gateway -----------------------------------
>
> #
>
> # Block initial recovery after a full cluster restart until N nodes are started:
>
> #
>
> #gateway.recover\_after\_nodes: 3
>
> #
>
> # For more information, consult the gateway module documentation.
>
> #
>
> # ---------------------------------- Various -----------------------------------
>
> #
>
> # Require explicit names when deleting indices:
>
> #
>
> #action.destructive\_requires\_name: true
> systemctl status elasticsearch
> ● elasticsearch.service - Elasticsearch
> Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendo
> Active: failed (Result: exit-code) since Sat 2019-06-29 23:59:50 PDT; 20min a
> Docs: [http://www.elastic.co](http://www.elastic.co)
> Process: 4688 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DI
> Main PID: 4688 (code=exited, status=1/FAILURE)
>
> Jun 29 23:59:50 PET310S elasticsearch[4688]: in 'reader', line 55, column 5:
> Jun 29 23:59:50 PET310S elasticsearch[4688]: network.host: 192.168.1.252
> Jun 29 23:59:50 PET310S elasticsearch[4688]: ^
> Jun 29 23:59:50 PET310S elasticsearch[4688]: at org.yaml.snakeyaml.parse
> Jun 29 23:59:50 PET310S elasticsearch[4688]: at org.yaml.snakeyaml.parse
> Jun 29 23:59:50 PET310S elasticsearch[4688]: at org.yaml.snakeyaml.parse
> Jun 29 23:59:50 PET310S elasticsearch[4688]: at com.fasterxml.jackson.da
> Jun 29 23:59:50 PET310S elasticsearch[4688]: ... 13 more
> Jun 29 23:59:50 PET310S systemd[1]: elasticsearch.service: Main process exited,
> Jun 29 23:59:50 PET310S systemd[1]: elasticsearch.service: Failed with result 'e
> lines 1-17/17 (END)
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [July 1, 2019, 9:27am UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/2 "2019-07-01T09:27:10Z")
this forum supports markdown for formatting snippets. Please use this.
Also, it would be useful to include the full exception. Judging from the snippet something around the `network.host` setting is off - this may be indentation but is hard to tell without more logfiles.
Can you provide the logs and the **exact** configuration file in a gist or pastebin?
---
### Author:  [@marcerickson](https://discuss.elastic.co/u/marcerickson)
#### Post date: [July 1, 2019, 10:29am UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/3 "2019-07-01T10:29:09Z")
> 
>
> [spinscale](https://discuss.elastic.co/u/spinscale)
> [Alexander Reelsen](https://discuss.elastic.co/u/spinscale)
> Elastic Team Member
>
> ```
> July 1
>
> ```
>
> _this forum supports markdown for formatting snippets. Please use this._
What's markdown?
> _Also, it would be useful to include the full exception. Judging from the snippet something around the `network.host` setting is off - this may be indentation but is hard to tell without more logfiles._
Sorry about the formatting. Is there a tutorial for beginners?
> _Can you provide the logs and the **exact** configuration file in a gist or pastebin?_
/var/log/elasticsearch is locked and I can't access the logs.
Any help you can give would be great. Thank you very much.
---
### Author:  [@irobot678](https://discuss.elastic.co/u/irobot678)
#### Post date: [July 1, 2019, 11:16am UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/4 "2019-07-01T11:16:15Z")
Hi @marcerickson ,
change your
```auto
network.host: 192.168.1.25
```
into
```auto
network.host: "localhost"
```
and try running your elasticsearch once again.
---
### Author:  [@marcerickson](https://discuss.elastic.co/u/marcerickson)
#### Post date: [July 1, 2019, 7:06pm UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/5 "2019-07-01T19:06:14Z")
No luck.
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2019-07-01 11:56:53 PDT; 5min ago
Docs: [http://www.elastic.co](http://www.elastic.co)
Process: 2620 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 2620 (code=exited, status=1/FAILURE)
Jul 01 11:56:53 PET310S elasticsearch[2620]: in 'reader', line 55, column 5:
Jul 01 11:56:53 PET310S elasticsearch[2620]: network.host: "localhost"
Jul 01 11:56:53 PET310S elasticsearch[2620]: ^
Jul 01 11:56:53 PET310S elasticsearch[2620]: at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:569)
Jul 01 11:56:53 PET310S elasticsearch[2620]: at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:157)
Jul 01 11:56:53 PET310S elasticsearch[2620]: at org.yaml.snakeyaml.parser.ParserImpl.getEvent(ParserImpl.java:167)
Jul 01 11:56:53 PET310S elasticsearch[2620]: at com.fasterxml.jackson.dataformat.yaml.YAMLParser.nextToken(YAMLParser.java:340)
Jul 01 11:56:53 PET310S elasticsearch[2620]: ... 13 more
Jul 01 11:56:53 PET310S systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Jul 01 11:56:53 PET310S systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
~
~
~
~
~
~
~
lines 1-17/17 (END)
---
### Author:  [@marcerickson](https://discuss.elastic.co/u/marcerickson)
#### Post date: [July 1, 2019, 7:18pm UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/6 "2019-07-01T19:18:48Z")
I have Java 12 - does that make a difference?
---
### Author:  [@marcerickson](https://discuss.elastic.co/u/marcerickson)
#### Post date: [July 2, 2019, 1:44am UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/7 "2019-07-02T01:44:33Z")
/var/log/elasticsearch contains 21 files. They are gc.log and gc.log.00 through gc.log.19. Each file is 0 ( zero ) bytes.
I just ran sudo apt update and upgrade. I got this error:
Errors were encountered while processing:
elasticsearch
E: Sub-process /usr/bin/dpkg returned an error code (1)
---
### Author:  [@marcerickson](https://discuss.elastic.co/u/marcerickson)
#### Post date: [July 9, 2019, 11:41pm UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/8 "2019-07-09T23:41:10Z")
Elasticsearch still won't run.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 6, 2019, 11:41pm UTC](https://discuss.elastic.co/t/elasticsearch-service-wont-run-on-new-installation/188179/9 "2019-08-06T23:41:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.