Project

General

Profile

Actions

tickets #160409

closed

Elasticsearch does not start on water4

Added by crameleon 27 days ago. Updated 26 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Wiki
Target version:
-
Start date:
2024-05-15
Due date:
% Done:

0%

Estimated time:

Description

Observed on water4.i.o.o:

water4 (wiki search backend):~ # rcelasticsearch status
× elasticsearch.service - Elasticsearch
     Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
    Drop-In: /etc/systemd/system/elasticsearch.service.d
             └─es-apparmor.conf
     Active: failed (Result: exit-code) since Mon 2024-05-13 19:28:53 UTC; 1 day 22h ago
       Docs: http://www.elastic.co
    Process: 1078 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=78)
   Main PID: 1078 (code=exited, status=78)

May 13 19:28:38 water4 systemd[1]: Started Elasticsearch.
May 13 19:28:38 water4 elasticsearch[1078]: warning: Falling back to java on path. This behavior is deprecated. Specify JAVA_HOME
May 13 19:28:40 water4 elasticsearch[1078]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
May 13 19:28:53 water4 systemd[1]: elasticsearch.service: Main process exited, code=exited, status=78/CONFIG
May 13 19:28:53 water4 systemd[1]: elasticsearch.service: Failed with result 'exit-code'.

In /var/log/elasticsearch:

[2024-05-13T19:28:52,758][INFO ][o.e.n.Node               ] [water4] initialized
[2024-05-13T19:28:52,758][INFO ][o.e.n.Node               ] [water4] starting ...
[2024-05-13T19:28:53,071][INFO ][o.e.t.TransportService   ] [water4] publish_address {127.0.0.1:9300}, bound_addresses {[::]:9300}
[2024-05-13T19:28:53,148][INFO ][o.e.b.BootstrapChecks    ] [water4] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2024-05-13T19:28:53,161][ERROR][o.e.b.Bootstrap          ] [water4] node validation exception
[1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2024-05-13T19:28:53,171][INFO ][o.e.n.Node               ] [water4] stopping ...
[2024-05-13T19:28:53,204][INFO ][o.e.n.Node               ] [water4] stopped
[2024-05-13T19:28:53,204][INFO ][o.e.n.Node               ] [water4] closing ...
[2024-05-13T19:28:53,222][INFO ][o.e.n.Node               ] [water4] closed

Starting the service by hand, it comes up fine.


Related issues 1 (0 open1 closed)

Related to openSUSE admin - tickets #160412: Re: Search function in openSUSE wiki brokenResolvedcrameleon2024-05-15

Actions
Actions #1

Updated by crameleon 27 days ago

  • Private changed from Yes to No
Actions #2

Updated by crameleon 27 days ago

On water3.i.o.o it successfully started automatically after the last reboot.

Actions #3

Updated by crameleon 27 days ago

  • Subject changed from ElasticSearch does not start after reboot to Elasticsearch does not start on water4

Seems my initial analysis was flawed, it crashed again on water4 shortly after.

Actions #4

Updated by crameleon 27 days ago

  • Status changed from New to In Progress
  • Assignee set to crameleon
Actions #5

Updated by crameleon 27 days ago

After

water4 (wiki search backend):~ # sysctl vm.max_map_count=262144
vm.max_map_count = 262144

it seems to really start up.

Permanent patch: https://gitlab.infra.opensuse.org/infra/salt/-/merge_requests/1829.

Actions #6

Updated by crameleon 27 days ago

  • Related to tickets #160412: Re: Search function in openSUSE wiki broken added
Actions

Also available in: Atom PDF