# Puppet catalog error on version 5.2 for systemd

**URL:** <https://discuss.elastic.co/t/puppet-catalog-error-on-version-5-2-for-systemd/76774>\
**Category:** Elasticsearch\
**Created:** [February 28, 2017, 12:29pm UTC](https://discuss.elastic.co/t/puppet-catalog-error-on-version-5-2-for-systemd/76774 "2017-02-28T12:29:58Z")\
**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 28, 2017, 12:29pm UTC](https://discuss.elastic.co/t/puppet-catalog-error-on-version-5-2-for-systemd/76774/1 "2017-02-28T12:29:58Z")

</div>

Hello,  
I have an error after playing around with puppet-elasticsearch puppetForge mod version 'elastic-elasticsearch', '5.0.0'.  
Here is the error my puppet agent gives me:  
`
puppet-agent[115010]: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'homedir' at /etc/puppetlabs/code/environments/feature_elk5/modules/elasticsearch/manifests/service/systemd.pp:165 on Elasticsearch_service_file[/lib/systemd/system/elasticsearch-net.elastic.infra.service] at /etc/puppetlabs/code/environments/feature_elk5/modules/elasticsearch/manifests/service/systemd.pp:165 on node syslog03.test
`

As it don't say in the readme file for puppet-elasticsearch that I need to set an 'homedir' only add an instance name. I have only set my name for the instance and added a own 'datadir'. I use hiera for this, with the "lookup" command.  
Anyone else have this problem? Or can help me some to point me in the correct direction at least?

My system is as follows:  
Centos 7 as a VM. 8GB RAM, 2 CPU.  
Puppet version 4.8.  
Installed from Katello version 3.2.1.1.

---

<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 28, 2017, 2:46pm UTC](https://discuss.elastic.co/t/puppet-catalog-error-on-version-5-2-for-systemd/76774/2 "2017-02-28T14:46:41Z")

</div>

This is a very common problem when updating puppet modules, and can usually be solved by restarting the puppetmaster.

---

<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 28, 2017, 2:51pm UTC](https://discuss.elastic.co/t/puppet-catalog-error-on-version-5-2-for-systemd/76774/3 "2017-02-28T14:51:45Z")

</div>

Alright. Will have to try it then I guess.

---

<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 28, 2017, 3:37pm UTC](https://discuss.elastic.co/t/puppet-catalog-error-on-version-5-2-for-systemd/76774/4 "2017-02-28T15:37:47Z")

</div>

Thanks it solved the problem.

---

<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 28, 2017, 3:38pm UTC](https://discuss.elastic.co/t/puppet-catalog-error-on-version-5-2-for-systemd/76774/5 "2017-03-28T15:38:21Z")

</div>

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