Hi,
I had installed Elasticsearch on a cluster of three Redhat 7.9 servers, but the service failed to start.
When I check the elasticsearch status it's displayed several errors
main ERROR Null object returned for RollingFile in Appenders
main ERROR Unable to locate appender "rolling" for logger config "root"
root@OLTPDMIN402:/data# systemctl status elasticsearch.service -l
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2022-09-01 03:11:23 WEST; 5s ago
Docs: http://www.elastic.co
Process: 28559 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 28559 (code=exited, status=1/FAILURE)
Sep 01 03:11:22 OLTPDMIN402.corporativo.pt elasticsearch[28559]: 2022-09-01 03:11:22,875 main ERROR Null object returned for RollingFile in Appenders.
Sep 01 03:11:22 OLTPDMIN402.corporativo.pt elasticsearch[28559]: 2022-09-01 03:11:22,875 main ERROR Null object returned for RollingFile in Appenders.
Sep 01 03:11:22 OLTPDMIN402.corporativo.pt elasticsearch[28559]: 2022-09-01 03:11:22,875 main ERROR Null object returned for RollingFile in Appenders.
Sep 01 03:11:22 OLTPDMIN402.corporativo.pt elasticsearch[28559]: 2022-09-01 03:11:22,876 main ERROR Unable to locate appender "rolling" for logger config "root"
Sep 01 03:11:22 OLTPDMIN402.corporativo.pt elasticsearch[28559]: 2022-09-01 03:11:22,876 main ERROR Unable to locate appender "index_indexing_slowlog_rolling" for logger config "index.indexing.slowlog.index"
Sep 01 03:11:22 OLTPDMIN402.corporativo.pt elasticsearch[28559]: 2022-09-01 03:11:22,876 main ERROR Unable to locate appender "index_search_slowlog_rolling" for logger config "index.search.slowlog"
Sep 01 03:11:22 OLTPDMIN402.corporativo.pt elasticsearch[28559]: 2022-09-01 03:11:22,876 main ERROR Unable to locate appender "deprecation_rolling" for logger config "org.elasticsearch.deprecation"
Sep 01 03:11:23 OLTPDMIN402.corporativo.pt systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Sep 01 03:11:23 OLTPDMIN402.corporativo.pt systemd[1]: Unit elasticsearch.service entered failed state.
Sep 01 03:11:23 OLTPDMIN402.corporativo.pt systemd[1]: elasticsearch.service failed.
root@OLTPDMIN402:/data# timed out waiting for input: auto-logout
I changed the path data and path logs to other filesystem that has a lot of storage, here it's the elascticsearch.yml file
root@OLTPDMIN402:~# 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:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: DMS-Elastic-Prod
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: OLTPDMIN402
#
# 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: /data/Elastic/data
#
# Path to log files:
#
path.logs: /data/Elastic/logs
#
# ----------------------------------- 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: 10.172.74.35
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
#-------------------------------- Node Master ---------------------------------
#
# define node 1, 2 and 3 as master-eligible:
node.master: true
#
#
#
# --------------------------------- 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: ["10.172.74.35", "10.172.74.36", "10.172.74.37"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
discovery.zen.minimum_master_nodes: 2
#
# 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: 2
gateway.expected_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
root@OLTPDMIN402:~#
The java version
root@OLTPDMIN402:~# java -version
openjdk version "11.0.16" 2022-07-19 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.16.0.8-1.0.1.el7_9) (build 11.0.16+8-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.16.0.8-1.0.1.el7_9) (build 11.0.16+8-LTS, mixed mode, sharing)
root@OLTPDMIN402:~#
root@OLTPDMIN402:~#
Could you help ? Thanks