# Error while restarting elastic service when I add xpack.security.enabled: true to the .yml file

**URL:** <https://discuss.elastic.co/t/error-while-restarting-elastic-service-when-i-add-xpack-security-enabled-true-to-the-yml-file/292938>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [December 26, 2021, 5:20pm UTC](https://discuss.elastic.co/t/error-while-restarting-elastic-service-when-i-add-xpack-security-enabled-true-to-the-yml-file/292938 "2021-12-26T17:20:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ayoub\_Mouloua](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayoub_mouloua/32/99551_2.png) [@Ayoub\_Mouloua](https://discuss.elastic.co/u/Ayoub_Mouloua)\
**Post date:** [December 26, 2021, 5:20pm UTC](https://discuss.elastic.co/t/error-while-restarting-elastic-service-when-i-add-xpack-security-enabled-true-to-the-yml-file/292938/1 "2021-12-26T17:20:17Z")

</div>

Hello ppl,

when I add xpack.security.enabled: true rule to .yml file and I restart the service using : sudo systemctl restart elasticsearch.service I got this error:

Job for elasticsearch.service failed because the control process exited with error code.  
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.

here is my .yml file configurations:

# ======================== 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](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 -----------------------------------

# 

# By default Elasticsearch is only accessible on localhost. Set a different

# address here to expose this node on the network:

# 

network.host: 10.30.211.141

# 

# By default Elasticsearch listens for HTTP traffic on the first free port it

# finds starting at 9200. Set a specific HTTP port here:

# 

#http.port: 9200

# 

# For more information, consult the network module documentation.

# 

# --------------------------------- Discovery ----------------------------------

# 

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

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

# 

discovery.seed\_hosts: ["host1", "10.30.211.141"]

# 

# Bootstrap the cluster using an initial set of master-eligible nodes:

# 

#cluster.initial\_master\_nodes: ["node-1", "node-2"]

# 

# For more information, consult the discovery and cluster formation module documentation.

# 

# ---------------------------------- Various -----------------------------------

# 

# Require explicit names when deleting indices:

# 

#action.destructive\_requires\_name: true

# 

# ---------------------------------- Security ----------------------------------

# 

# \*\*\* WARNING \*\*\*

# 

# Elasticsearch security features are not enabled by default.

# These features are free, but require configuration changes to enable them.

# This means that users don’t have to provide credentials and can get full access

# to the cluster. Network connections are also not encrypted.

# 

# To protect your data, we strongly encourage you to enable the Elasticsearch security features.

# Refer to the following documentation for instructions.

# 

# [Configure security for the Elastic Stack | Elasticsearch Guide [7.16] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.16/configuring-stack-security.html)

# ---------------------------------------------- X-pack monitoring --------------------

xpack.monitoring.collection.enabled: true  
xpack.monitoring.elasticsearch.collection.enabled: true  
xpack.security.authc.api\_key.enabled: true  
xpack.security.enabled: true

please anyone can help me out?

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [December 29, 2021, 5:49am UTC](https://discuss.elastic.co/t/error-while-restarting-elastic-service-when-i-add-xpack-security-enabled-true-to-the-yml-file/292938/2 "2021-12-29T05:49:52Z")

</div>

> [@Ayoub\_Mouloua](#):
>
> See "systemctl status Elasticsearch.service" and "journalctl -xe" for details.

What errors were reported when you did that?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 29, 2021, 6:56am UTC](https://discuss.elastic.co/t/error-while-restarting-elastic-service-when-i-add-xpack-security-enabled-true-to-the-yml-file/292938/3 "2021-12-29T06:56:50Z")

</div>

Welcome to our community! 😃

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 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 26, 2022, 6:57am UTC](https://discuss.elastic.co/t/error-while-restarting-elastic-service-when-i-add-xpack-security-enabled-true-to-the-yml-file/292938/4 "2022-01-26T06:57:21Z")

</div>

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