Unable to start elastcsearch 5.5.0 service, getting 203 error

Elastic Stack Elasticsearch
1

Hi,

I have just installed elasticsearch 5.5.0 using RPM and I am not able to start the services, here is all the details, also I have uploaded the yml file.

[root@xxxxxx]# systemctl status elasticsearch.service

● elasticsearch.service - Elasticsearch

Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Mon 2020-03-23 17:02:04 GMT; 45min ago

 Docs: http://www.elastic.co

Process: 37956 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=203/EXEC)

Mar 23 17:02:04 xxxxxx.net systemd[1]: Starting Elasticsearch...

Mar 23 17:02:04 xxxxxx.net systemd[1]: elasticsearch.service: control process exited, code=exited status=203

Mar 23 17:02:04 xxxxxx.net systemd[1]: Failed to start Elasticsearch.

Mar 23 17:02:04 xxxxxxx.net systemd[1]: Unit elasticsearch.service entered failed state.

Mar 23 17:02:04 xxxxxxxx

elasticsearch
elasticsearch1014×386 50.4 KB
.net systemd[1]: elasticsearch.service failed.

2

Please take your time to properly format snippets and do not use screenshots. They are hard to read. Thank you.

You could probably check via journalctl for further output as well as checking the logfiles why the service has not started. See https://www.elastic.co/guide/en/elasticsearch/reference/7.6/starting-elasticsearch.html

3

I have tried all documents step but no luck. receiving below error in #journalctl --unit elasticsearch

Mar 24 17:44:31 xxx.net systemd[1]: Starting Elasticsearch...
Mar 24 17:44:31 xxx.net systemd[1]: elasticsearch.service: control process exited, code=exited status=203
Mar 24 17:44:31 xxx.net systemd[1]: Failed to start Elasticsearch.
Mar 24 17:44:31 xxx.net systemd[1]: Unit elasticsearch.service entered failed state.
Mar 24 17:44:31 xxx.net systemd[1]: elasticsearch.service failed.

4

I have searched lot in google nowhere find any solution, could somebody help on this. this is how my yml file looks.

cluster.name: zephyr

node.name: "Node1"

node.master: true

node.data: true

script.inline: true

script.stored: true

network.bind_host: x.x.x.x

network.publish_host: x.x.x.x

network.host: x.x.x.x

transport.tcp.port: 9300

http.port: 9200

discovery.zen.ping.unicast.hosts: ["x.x.x.x:9300"]

indices.query.bool.max_clause_count: 9012

path.data: /var/lib/elasticsearch

path.logs: /var/log/elasticsearch

5

Please don't post unformatted code, logs, or configuration as it's very hard to read.

Instead, paste the text and format it with </> icon or pairs of triple backticks (```), and check the preview window to make sure it's properly formatted before posting it. This makes it more likely that your question will receive a useful answer.

It would be great if you could update your post to solve this.

6

I have searched lot in google nowhere find any solution, could somebody help on this. this is how my yml file looks.

cluster.name: zephyr

node.name: "Node1"

node.master: true

node.data: true

script.inline: true

script.stored: true

network.bind_host: x.x.x.x

network.publish_host: x.x.x.x

network.host: x.x.x.x

transport.tcp.port: 9300

http.port: 9200

discovery.zen.ping.unicast.hosts: ["x.x.x.x:9300"]

indices.query.bool.max_clause_count: 9012

path.data: /var/lib/elasticsearch

path.logs: /var/log/elasticsearch
7

any help?

8

What are the logs?

9

Application is not generating any logs. Journalctl -xe gives me below error.


Mar 25 15:55:40 xxxx.net systemd[4753]: Failed at step EXEC spawning /usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec: Permission Denied
Mar 25 15:55:40 xxxx.net systemd[1]: elasticsearch.service: control process exited, code=exited statu
Mar 25 15:55:40 xxxx.net systemd[1]: Failed to start Elasticsearch.
Mar 25 15:55:40 xxxx.net systemd[1]: Unit elasticsearch.service entered failed state.
Mar 25 15:55:40 xxxx.net systemd[1]: elasticsearch.service failed.
10

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