Elasticsearch service fails in my machine

Hi all,

Kibana is active in my system.
Elasticsearch was also running fine.

But i wanted it to start on boot and i made some changes in java files.
I made some changes in jvm files,but don't remember.

Now elasticsearch throws up error as:

Loaded: loaded (/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-11-30 13:26:26 IST; 12min ago
Docs: https://www.elastic.co
Process: 6097 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FA>
Main PID: 6097 (code=exited, status=1/FAILURE)

Nov 30 13:26:26 hinclude-Latitude-E6430 systemd-entrypoint[6243]: error:
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd-entrypoint[6243]: OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000004c000000>
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd-entrypoint[6243]: at org.elasticsearch.tools.launchers.JvmErgonomics.flagsFinal(JvmEr>
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd-entrypoint[6243]: at org.elasticsearch.tools.launchers.JvmErgonomics.finalJvmOptions(>
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd-entrypoint[6243]: at org.elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgono>
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd-entrypoint[6243]: at org.elasticsearch.tools.launchers.JvmOptionsParser.jvmOptions(Jv>
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd-entrypoint[6243]: at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptio>
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Nov 30 13:26:26 hinclude-Latitude-E6430 systemd[1]: Failed to start Elasticsearch.

Need help here...

Welcome to our community! :smiley:

Please check the Elasticsearch log for more information.

Hi all, I had changed the path in one of yml files...

Issue resolved

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