Elasticsearch-7.9.2-amd64.deb exit status 78

[Sayantan_Chakraborty]

hi, i am facing a few issues for the Magento2.4.x installation.

The process' exit code is 'exited' and its exit status is 78.
Jul 04 02:12:40 somehost systemd[1]: elasticsearch.service: Failed with result>
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit elasticsearch.service has entered the 'failed' state with result 'e>
Jul 04 02:12:40 ocizoqolo systemd[1]: Failed to start Elasticsearch.
-- Subject: A start job for unit elasticsearch.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support

jvm options

# Xmx represents the maximum size of total heap space

-Xms256m
-Xmx256m

#############

elasticsearch.yml file

cluster.name: my-search
node.name: ${HOSTNAME}
node.data: false
node.master: true
node.ingest: false
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
http.port: 9200
transport.host: _site_
transport.tcp.port: 9300

installed : elasticsearch-7.9.2-amd64.deb
on ubuntu 20.4
OCI

i have no clue to figure it out.

thx
sayanan

type or paste code here

type or paste code here

[Christian_Dahlqvist]

Look in the Elasticsearch logs. I do not think I have ever seen Elasticsearch run with such small heap so would recommend you at least double it.

[Sayantan_Chakraborty]

hi
i doubled it but it is still not running

Job for elasticsearch.service failed because a timeout was exceeded.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.
systemd[1]: Failed to start Elasticsearch.

gclog21

[2021-07-04T08:08:51.782+0000][73994][gc,heap,exit]   region size 1024K, 2 young (2048K), 0 survivors (0K)
[2021-07-04T08:08:51.782+0000][73994][gc,heap,exit]  Metaspace       used 3309K, capacity 4480K, committed 4480K, reserved 1056768K
[2021-07-04T08:08:51.782+0000][73994][gc,heap,exit]   class space    used 266K, capacity 384K, committed 384K, reserved 1048576K

thx
sayantan

[Christian_Dahlqvist]

Have a look at the Elasticsearch logs for further clues. The location of these depend on how you installed Elasticsearch.

[Sayantan_Chakraborty]

no idea. i followed Elasticsearch: Job for elasticsearch.service failed

[Christian_Dahlqvist]

The location for various type of installs is shown here. Please find the logs and post them here as that will most likely show what the problem is.

[Sayantan_Chakraborty]

hi

i installed elasticsearch 7.6.0 following the steps

$apt remove elasticsearch
$apt purge elasticsearch
$apt install elasticsearch=7.6.0
 $systemctl daemon-reload
$systemctl enable elasticsearch.service
Synchronizing state of elasticsearch.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable elasticsearch
Created symlink /etc/systemd/system/multi-user.target.wants/elasticsearch.service → /lib/systemd/system/elasticsearch.service.

$systemctl start elasticsearch.service
Job for elasticsearch.service failed because a fatal signal was delivered to the control process.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.
$ journalctl -xe
--
-- The process' exit code is 'killed' and its exit status is 9.
Jul 04 12:21:48 somehost systemd[1]: elasticsearch.service: Failed with result>
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit elasticsearch.service has entered the 'failed' state with result 's>
Jul 04 12:21:48 myhost systemd[1]: Failed to start Elasticsearch.
-- Subject: A start job for unit elasticsearch.service has failed

$cat jvm.options|grep '256m'
-Xms256m
-Xmx256m

then changed elasticsearch.yml file

 $cat /etc/elasticsearch/elasticsearch.yml|grep localhost
network.host: localhost

$cat /etc/elasticsearch/elasticsearch.yml|grep 127.0.0.1
# The default list of hosts is ["127.0.0.1", "[::1]"]
discovery.seed_hosts: ["127.0.0.1", "[::1]"]

mostly it goes well with systemctl start elasticsearch and i got

$ curl -X GET "http://localhost:9200"
{
  "name" : "somehost",
  "cluster_name" : "my-application",
  "cluster_uuid" : "_na_",
  "version" : {
    "number" : "7.6.0",
    "build_flavor" : "default",
    "build_type" : "deb",
    "build_hash" : "7f634e9f44834fbc12724506cc1da681b0c3b1e3",
    "build_date" : "2020-02-06T00:09:00.449973Z",
    "build_snapshot" : false,
    "lucene_version" : "8.4.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

do I need to configure a proxy too?

thx
sayantan

[Christian_Dahlqvist]

@Sayantan_Chakraborty

-Xms256m
-Xmx256m

I have never seen Elasticsearch run with this small heap, so would recommend you at least double it.

[Sayantan_Chakraborty]

i think it was best for me as my max memory is 1G . i am with always free tier of OCI now. possibly if i move out from development i will put up 1G then. also I am planing to get separate host for this in future eg. t3. small or something on gcp would work best in that case. but i don't know how to integrate something like that with magento also magento community support forum had very limited response on such thing. increasing it to 512m will take a long time now for simple restart.

and i faced

Job for elasticsearch.service failed because a timeout was exceeded.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.