Installation of opensearch fails with result exit-code

1. Describe your incident:
issues getting opensearch to start for the first time

2. Describe your environment:

  • OS Information: ubuntu server 22.04, 8 GB ram

  • Package Version:
    2.11.2

I thought I had successfully installed opensearch, but when I go to start it, with:
sudo systemctl start opensearch.service
I get back:
Jan 04 16:17:58 linuxserver systemd-entrypoint[16042]: at com.fasterxml.brown.dataformat.yaml.YAMLParser.nextToken(YAMLParser.java:482)
Jan 04 16:17:58 linuxserver systemd-entrypoint[16042]: at org.opensearch.common.xcontent.json.JsonXContentParser.nextToken(JsonXContentParser.java:66)
Jan 04 16:17:58 linuxserver systemd-entrypoint[16042]: at org.opensearch.common.settings.Settings.fromXContent(Settings.java:660)
Jan 04 16:17:58 linuxserver systemd-entrypoint[16042]: at org.opensearch.common.settings.Settings.fromXContent(Settings.java:629)
Jan 04 16:17:58 linuxserver systemd-entrypoint[16042]: at org.opensearch.common.settings.Settings$Builder.loadFromStream(Settings.java:1142)
Jan 04 16:17:58 linuxserver systemd-entrypoint[16042]: … 9 more
Jan 04 16:17:58 linuxserver systemd[1]: opensearch.service: Main process exited, code=exited, status=1/FAILURE
Jan 04 16:17:58 linuxserver systemd[1]: opensearch.service: Failed with result ‘exit-code’.
Jan 04 16:17:58 linuxserver systemd[1]: Failed to start OpenSearch.
Jan 04 16:17:58 linuxserver systemd[1]: opensearch.service: Consumed 3.465s CPU time.

when I run systemctl status opesearch.service it returns:

opensearch.service: Main process exited, code=exited, status=1/FAILURE
opensearch.service: Failed with result ‘exit-code’.

what can I do to drill down further and find the issue?

How did you install opensearch (e.g. package, manual install?)

Can you share the exact set of commands? (This is helpful to try and reproduce what you are seeing)

Also can you you share your opensearch config file and jvm options?

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