How to handle this error

Elastic Stack Elasticsearch
1 
 elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2021-11-09 13:38:12 PKT; 11s ago
     Docs: https://www.elastic.co
  Process: 4837 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
 Main PID: 4837 (code=exited, status=1/FAILURE)

Nov 09 13:38:12 centos8.linuxvmimages.local systemd-entrypoint[4837]:         at org.yaml.snakeyaml.scanner.ScannerImpl.needMoreTokens(ScannerImpl.java:278)
Nov 09 13:38:12 centos8.linuxvmimages.local systemd-entrypoint[4837]:         at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:226)
Nov 09 13:38:12 centos8.linuxvmimages.local systemd-entrypoint[4837]:         at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:558)
Nov 09 13:38:12 centos8.linuxvmimages.local systemd-entrypoint[4837]:         at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
Nov 09 13:38:12 centos8.linuxvmimages.local systemd-entrypoint[4837]:         at org.yaml.snakeyaml.parser.ParserImpl.getEvent(ParserImpl.java:168)
Nov 09 13:38:12 centos8.linuxvmimages.local systemd-entrypoint[4837]:         at com.fasterxml.jackson.dataformat.yaml.YAMLParser.nextToken(YAMLParser.java:355)
Nov 09 13:38:12 centos8.linuxvmimages.local systemd-entrypoint[4837]:         ... 14 more
Nov 09 13:38:12 centos8.linuxvmimages.local systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Nov 09 13:38:12 centos8.linuxvmimages.local systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Nov 09 13:38:12 centos8.linuxvmimages.local systemd[1]: Failed to start Elasticsearch.
~
~
2

Welcome to our community! :smiley:

We will need more information to help here.
What version of Elasticsearch are you running?
When are you getting this error?
Did you make changes to anything prior to getting this error? If so, what?
What do your Elasticsearch logs show?

3

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