Hi!
I am basic startup user with ELK.
I could not start Elasticserach service
Platform
Linux SLMKibana 4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Error
sudo systemctl status elasticsearch
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-12-12 11:56:51 AEDT; 20min ago
Docs: http://www.elastic.co
Process: 31762 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG_DIR} -Edefault.path.data=${DATA_DIR} -Edefault.path.conf=${CONF_DIR} (code=exited, status=1/FAILURE)
Process: 31759 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 31762 (code=exited, status=1/FAILURE)
Dec 12 11:56:51 SLMKibana elasticsearch[31762]: # the most important settings you may want to configure for a production cluster.
Dec 12 11:56:51 SLMKibana elasticsearch[31762]: #
Dec 12 11:56:51 SLMKibana elasticsearch[31762]: # Please consult the documentation for further information on configuration options:
Dec 12 11:56:51 SLMKibana elasticsearch[31762]: # https://www.elastic.co/guide/en/elasticsearch/reference/index.html
Dec 12 11:56:51 SLMKibana elasticsearch[31762]: #
Dec 12 11:56:51 SLMKibana elasticsearch[31762]: # ---------------------------------- Cluster -----------------------------------
Dec 12 11:56:51 SLMKibana elasticsearch[31762]: #
Dec 12 11:56:51 SLMKibana systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 11:56:51 SLMKibana systemd[1]: elasticsearch.service: Unit entered failed state.
Dec 12 11:56:51 SLMKibana systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Configuration
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: slmkibana
#
# ------------------------------------ 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: /path/to/data
#
# Path to log files:
#
path.logs:/var/log/elasticsearch/slmkibana.log
#
# ----------------------------------- 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:localhost
#
# 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
Logs
No Logs found 
any help is highly apprecaited
Cheers
@IF
