Having issues with Elasticsearch stopping. I can get it to start for a few moments but, then it fails. I'm trying to perform some testing with The Hive Project and this is consistent hangup. Thanks. RA.
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-05-21 19:53:10 EDT; 14min ago
Docs: http://www.elastic.co
Process: 1580 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG_DIR} -Edefault.
Process: 1576 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 1580 (code=exited, status=1/FAILURE)
May 21 19:52:59 thehive systemd[1]: Starting Elasticsearch...
May 21 19:52:59 thehive systemd[1]: Started Elasticsearch.
May 21 19:53:10 thehive systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
May 21 19:53:10 thehive systemd[1]: elasticsearch.service: Unit entered failed state.
May 21 19:53:10 thehive systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
May 21 19:49:27 thehive systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
May 21 19:49:27 thehive systemd[1]: elasticsearch.service: Unit entered failed state.
May 21 19:49:27 thehive systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
May 21 19:52:59 thehive systemd[1]: Starting Elasticsearch...
May 21 19:52:59 thehive systemd[1]: Started Elasticsearch.
May 21 19:53:10 thehive systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
May 21 19:53:10 thehive systemd[1]: elasticsearch.service: Unit entered failed state.
May 21 19:53:10 thehive systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
GNU nano 2.5.3 File: /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: 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: 192.168.0.1
#
# Set a custom port for HTTP:
#
#http.port: 9200
#
# 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: 3
#
# 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
network.host: 127.0.0.1
index.name: the_hive
script.inline: true
cluster.name: hive
thread_pool.index.queue_size: 100000
thread_pool.search.queue_size: 100000
thread_pool.bulk.queue_size: 100000
http.port: 9300
echo $JAVA_HOME
/usr/lib/jvm/open-jdk`Preformatted text`Please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you 
We will also need to see relevant content from your elasticsearch log file (which should be in /var/log/elasticsearch/)
Sorry for the bad formatting. I didn't notice when I created the thread. What would you like to see from the logs below?
hive_deprecation.log hive_index_search_slowlog.log
hive_index_indexing_slowlog.log hive.log
Thanks.
RA.
You need to read hive.log and look for important information that might explain why your node won't stay up.
We're here to help, but you need to do the work.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.