# Yum install on Centos7 gives no broken service for systemd

**URL:** <https://discuss.elastic.co/t/yum-install-on-centos7-gives-no-broken-service-for-systemd/74361>\
**Category:** Elasticsearch\
**Created:** [February 8, 2017, 12:36pm UTC](https://discuss.elastic.co/t/yum-install-on-centos7-gives-no-broken-service-for-systemd/74361 "2017-02-08T12:36:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![m0n0lith](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@m0n0lith](https://discuss.elastic.co/u/m0n0lith)\
**Post date:** [February 8, 2017, 12:36pm UTC](https://discuss.elastic.co/t/yum-install-on-centos7-gives-no-broken-service-for-systemd/74361/1 "2017-02-08T12:36:34Z")

</div>

When I install Elasticsearch 5.1.2 on a Centos7 with help of Puppet/Puppet-forge is see this:

> ls -al /etc/systemd/system/elasticsearch.service  
> lrwxrwxrwx 1 root root 9 Feb 3 15:09 /etc/systemd/system/elasticsearch.service -\> /dev/null

Also I have no elasticsearch.yml files in /etc/elasticsearch/, only jvm\*.

I have tried and do a "pure" yum install and still get that the systemd service for elasticsearch goes towards /dev/null. Both Kibana and Logstash didn't have this problem.

My logs from YUM do not give any hints and Elasticsearch creates no logs.  
Anyone got any tricks for me to try?

---

<div class="post-metadata">

**Author:** ![m0n0lith](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@m0n0lith](https://discuss.elastic.co/u/m0n0lith)\
**Post date:** [February 8, 2017, 2:20pm UTC](https://discuss.elastic.co/t/yum-install-on-centos7-gives-no-broken-service-for-systemd/74361/2 "2017-02-08T14:20:55Z")

</div>

I have now seen this with help from a co-worker:

> systemctl status elasticsearch.service  
> ● elasticsearch.service  
> Loaded: masked (/dev/null; bad)

Why does it mask it and what have I missed in my profile?

---

<div class="post-metadata">

**Author:** ![tylerjl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylerjl/32/44965_2.png) [@tylerjl](https://discuss.elastic.co/u/tylerjl)\
**Post date:** [February 8, 2017, 2:29pm UTC](https://discuss.elastic.co/t/yum-install-on-centos7-gives-no-broken-service-for-systemd/74361/3 "2017-02-08T14:29:15Z")

</div>

Hi @m0n0lith,

The Puppet module works by managing _instances_ of Elasticsearch. This is done primarily because many people need the ability to run more than one instance of Elasticsearch on a host.

[The documentation explains how to define a running instance of elasticsearch](https://github.com/elastic/puppet-elasticsearch#instances), but in the simplest form:

```auto
elasticsearch::instance { 'master' : }

```

Will create and manage one instance of Elasticsearch on your host.

```auto
systemctl status elasticsearch-master

```

(or whatever you choose to name your instance). Does that answer your question?

---

<div class="post-metadata">

**Author:** ![m0n0lith](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@m0n0lith](https://discuss.elastic.co/u/m0n0lith)\
**Post date:** [February 14, 2017, 12:11pm UTC](https://discuss.elastic.co/t/yum-install-on-centos7-gives-no-broken-service-for-systemd/74361/4 "2017-02-14T12:11:07Z")

</div>

Tanks! that help me a lot.  
I thought that the name was just for cluster setup and so on.

---

<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:** [March 14, 2017, 12:12pm UTC](https://discuss.elastic.co/t/yum-install-on-centos7-gives-no-broken-service-for-systemd/74361/5 "2017-03-14T12:12:31Z")

</div>

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