[SOLVED] CT; Elasticsearch startet nicht

[Tealk]

Hallo zusammen,

hat jemand Elasticsearch auf einem CT laufen oder ist bekannt das es da Probleme gibt? Auf einer VM hab ich das ohne große Probleme am laufen, wollte Mastodon nur eben gerne auch auf ein CT verschieben.

systemctl status elasticsearch.service

* elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Thu 2021-07-15 17:02:36 UTC; 6min ago
     Docs: https://www.elastic.co
  Process: 51372 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=killed, signal=KILL)
 Main PID: 51372 (code=killed, signal=KILL)
      CPU: 35.335s

Jul 15 17:02:13 Fediverse systemd[1]: Starting Elasticsearch...
Jul 15 17:02:36 Fediverse systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
Jul 15 17:02:36 Fediverse systemd[1]: elasticsearch.service: Failed with result 'signal'.
Jul 15 17:02:36 Fediverse systemd[1]: Failed to start Elasticsearch.
Jul 15 17:02:36 Fediverse systemd[1]: elasticsearch.service: Consumed 35.335s CPU time.

journalctl -xe

Jul 15 17:45:24 Fediverse systemd[1]: Starting Elasticsearch...
-- Subject: A start job for unit elasticsearch.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit elasticsearch.service has begun execution.
--
-- The job identifier is 2933.
Jul 15 17:45:34 Fediverse systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit elasticsearch.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 9.
Jul 15 17:45:34 Fediverse systemd[1]: elasticsearch.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit elasticsearch.service has entered the 'failed' state with result 'signal'.
Jul 15 17:45:34 Fediverse systemd[1]: Failed to start Elasticsearch.
-- Subject: A start job for unit elasticsearch.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit elasticsearch.service has finished with a failure.
--
-- The job identifier is 2933 and the job result is failed.
Jul 15 17:45:34 Fediverse systemd[1]: elasticsearch.service: Consumed 36.878s CPU time.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit elasticsearch.service completed and consumed the indicated resources.

/var/log/elasticsearch/gc.log

[2021-07-15T17:09:34.638+0000][51734][gc] Using G1
[2021-07-15T17:09:34.664+0000][51734][gc,init] Version: 16+36 (release)
[2021-07-15T17:09:34.664+0000][51734][gc,init] CPUs: 12 total, 6 available
[2021-07-15T17:09:34.664+0000][51734][gc,init] Memory: 64305M
[2021-07-15T17:09:34.664+0000][51734][gc,init] Large Page Support: Disabled
[2021-07-15T17:09:34.664+0000][51734][gc,init] NUMA Support: Disabled
[2021-07-15T17:09:34.664+0000][51734][gc,init] Compressed Oops: Enabled (Non-zero disjoint base)
[2021-07-15T17:09:34.664+0000][51734][gc,init] Heap Region Size: 16M
[2021-07-15T17:09:34.664+0000][51734][gc,init] Heap Min Capacity: 31G
[2021-07-15T17:09:34.664+0000][51734][gc,init] Heap Initial Capacity: 31G
[2021-07-15T17:09:34.664+0000][51734][gc,init] Heap Max Capacity: 31G
[2021-07-15T17:09:34.664+0000][51734][gc,init] Pre-touch: Disabled
[2021-07-15T17:09:34.664+0000][51734][gc,init] Parallel Workers: 6
[2021-07-15T17:09:34.664+0000][51734][gc,init] Concurrent Workers: 2
[2021-07-15T17:09:34.664+0000][51734][gc,init] Concurrent Refinement Workers: 6
[2021-07-15T17:09:34.664+0000][51734][gc,init] Periodic GC: Disabled
[2021-07-15T17:09:34.664+0000][51734][gc,metaspace] CDS disabled.
[2021-07-15T17:09:34.664+0000][51734][gc,metaspace] Compressed class space mapped at: 0x00000017c1000000-0x0000001801000000, reserved size: 1073741824
[2021-07-15T17:09:34.664+0000][51734][gc,metaspace] Narrow klass base: 0x00000017c1000000, Narrow klass shift: 0, Narrow klass range: 0x40000000
[2021-07-15T17:09:34.705+0000][51734][gc,heap,exit] Heap
[2021-07-15T17:09:34.705+0000][51734][gc,heap,exit]  garbage-first heap   total 32505856K, used 24578K [0x0000001001000000, 0x00000017c1000000)
[2021-07-15T17:09:34.705+0000][51734][gc,heap,exit]   region size 16384K, 2 young (32768K), 0 survivors (0K)
[2021-07-15T17:09:34.705+0000][51734][gc,heap,exit]  Metaspace       used 3562K, committed 3648K, reserved 1056768K
[2021-07-15T17:09:34.705+0000][51734][gc,heap,exit]   class space    used 282K, commit

 

[Tealk]

Ich weiß nicht woher aber elasticsearch bekommt wohl die Größe des Arbeitsspeichers des Host-servers heraus, deswegen steht in der log auch der Container hätte 64GB Ram. Der Container hat aber nur 16 zugewiesen und da die minimale Größe auf 31GB berechnet wurde konnte der Prozess nicht starten.
Folgende Einstellung hat das dann behoben:

etc/elasticsearch/jvm.options.d/jvm.options
-Xms4g
-Xmx4g