Elasticsearch service runs for 10s and then goes down

OS: CentOS
hostnamectl:-

Virtualization: kvm
Operating System: CentOS Linux 7 (AltArch)
CPE OS Name: cpe:/o:centos:centos:7:server
Kernel: Linux 3.10.0-1160.21.1.el7.ppc64le
Architecture: ppc64-le

ElasticSearch version: elasticsearch.noarch 0:6.8.15-1

This is the content from elasticsearch.yml file...

[root@con12 centos]# cat /etc/elasticsearch/elasticsearch.yml

======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

Elasticsearch Guide | Elastic

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

#cluster.name: my-application

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

#node.name: node-1

Add custom attributes to the node:

#node.attr.rack: r1

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

path.data: /var/lib/elasticsearch

Path to log files:

path.logs: /var/log/elasticsearch

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

Set the bind address to a specific IP (IPv4 or IPv6):

network.host: 0.0.0.0

Set a custom port for HTTP:

http.port: 9200

http.cors.enabled: true

http.cors.allow-origin: "*"

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when new node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

#discovery.zen.ping.unicast.hosts: ["host1", "host2"]

Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):

#discovery.zen.minimum_master_nodes:

For more information, consult the zen discovery module documentation.

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

#gateway.recover_after_nodes: 3

For more information, consult the gateway module documentation.

---------------------------------- Various -----------------------------------

Require explicit names when deleting indices:

#action.destructive_requires_name: true

Error:

[root@con12 centos]# sudo systemctl start elasticsearch

[root@con12 centos]# sudo systemctl status elasticsearch

elasticsearch.service - Elasticsearch

Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Thu 2021-04-22 09:44:41 EDT; 6s ago

Docs: http://www.elastic.co

Process: 25554 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)

Main PID: 25554 (code=exited, status=1/FAILURE)

Apr 22 09:44:38 con12.novalocal systemd[1]: Started Elasticsearch.

Apr 22 09:44:41 con12.novalocal systemd[1]: elasticsearch.service: main p...E

Apr 22 09:44:41 con12.novalocal systemd[1]: Unit elasticsearch.service en....

Apr 22 09:44:41 con12.novalocal systemd[1]: elasticsearch.service failed.

Hint: Some lines were ellipsized, use -l to show in full.

[root@con12 centos]# sudo systemctl start elasticsearch

[root@con12 centos]# sudo systemctl status elasticsearch

elasticsearch.service - Elasticsearch

Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)

Active: active (running) since Thu 2021-04-22 09:44:52 EDT; 2s ago

Docs: http://www.elastic.co

Main PID: 25661 (java)

Tasks: 22

Memory: 1.0G

CGroup: /system.slice/elasticsearch.service

└─25661 /bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMS...

Apr 22 09:44:52 con12.novalocal systemd[1]: Started Elasticsearch.

[root@con12 centos]# sudo systemctl status elasticsearch

elasticsearch.service - Elasticsearch

Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Thu 2021-04-22 09:44:55 EDT; 2s ago

Docs: http://www.elastic.co

Process: 25661 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)

Main PID: 25661 (code=exited, status=1/FAILURE)

Apr 22 09:44:52 con12.novalocal systemd[1]: Started Elasticsearch.

Apr 22 09:44:55 con12.novalocal systemd[1]: elasticsearch.service: main p...E

Apr 22 09:44:55 con12.novalocal systemd[1]: Unit elasticsearch.service en....

Apr 22 09:44:55 con12.novalocal systemd[1]: elasticsearch.service failed.

Hint: Some lines were ellipsized, use -l to show in full.

[root@con12 centos]#

[root@con12 centos]# journalctl -xe

[root@con12 centos]# journalctl -xe

Apr 22 10:23:08 con12.novalocal systemd[1]: Unit elasticsearch.service entered failed state.

Apr 22 10:23:08 con12.novalocal systemd[1]: elasticsearch.service failed.

Apr 22 10:23:11 con12.novalocal sudo[26667]: centos : TTY=pts/0 ; PWD=/home/centos ; USER=root ; COMMAND=/bin/systemctl st

Apr 22 10:23:11 con12.novalocal sudo[26667]: pam_unix(sudo:session): session opened for user root by centos(uid=0)

Apr 22 10:23:11 con12.novalocal sudo[26667]: pam_unix(sudo:session): session closed for user root

Apr 22 10:31:24 con12.novalocal dbus[1379]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='

Apr 22 10:31:24 con12.novalocal systemd[1]: Starting Hostname Service...

-- Subject: Unit systemd-hostnamed.service has begun start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit systemd-hostnamed.service has begun starting up.

Apr 22 10:31:24 con12.novalocal dbus[1379]: [system] Successfully activated service 'org.freedesktop.hostname1'

Apr 22 10:31:24 con12.novalocal systemd[1]: Started Hostname Service.

-- Subject: Unit systemd-hostnamed.service has finished start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit systemd-hostnamed.service has finished starting up.

--

-- The start-up result is done.

============

Tried existing solution available, no help.

Please advise.

As far as I know ppc64le is not a supported platform. As per the Support Matrix I believe only aarch64 and x86_64 are support.

Thanks Chris!

I tried other RPMs for which it said not supportable....I was able to install this version without compatibility warnings....

The fun part is that, the service stays running for about 10s and then goes down...

I just dont understand...the reason...is it low resources or some misconfigurations

If it was not supported platform, it would have warned/not allowed to install.

I followed the instructions provided at elastic.co

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