Ask Your Question

What does 'Unscheduling refresh on Service' mean in a puppet run output?

asked 2017-05-09 14:19:22 -0600

corywink gravatar image

updated 2017-05-09 14:21:03 -0600

I am trying to install an elasticsearch instance on a node using the elastic/elasticsearch module. It installs elasticsearch but the instance service does not start. In the puppet run output there are these lines at the end:

Notice: /Stage[main]/Profile::Elasticsearch/Elasticsearch::Instance[appsNode]/Elasticsearch::Service[appsNode]/Elasticsearch::Service::Systemd[appsNode]/Service[elasticsearch-instance-appsNode]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Profile::Elasticsearch/Elasticsearch::Instance[appsNode]/Elasticsearch::Service[appsNode]/Elasticsearch::Service::Systemd[appsNode]/Service[elasticsearch-instance-appsNode]: Unscheduling refresh on Service[elasticsearch-instance-appsNode]

What does this 'Unscheduling refresh on Service' mean? What causes that to occur? In the logs for elasticsearch I did find an error:

java.lang.IllegalArgumentException: unknown setting [default.path.home] did you mean any of [default.path.conf, default.path.logs]?

So I am assuming this could be the cause of the problem. But I would like to know in general what causes the 'Unscheduling refresh on Service' to occur for puppet runs, along with help in my specific case.

For the elasticsearch module there is no way to set the home path as a setting so this default is always the case, not sure where to begin to figure this out. Thanks for any help!

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2017-05-09 15:27:07 -0600

smarlow gravatar image

In Puppet you can specify a 'notify' relationship between resources. For example, let's say resource A notifies resource B. When resource A is changed then a refresh event is sent to resource B.

Generally speaking where you see this most often is a configuration file notifying a service. Service refreshes usually cause the service to restart or reload, thereby picking up the new values in your configuration file. In the agent run output you'll often see "Scheduling refresh on Service[service-name]', indicating that the change in the previous resource will cause a refresh of the service.

In this specific case the service isn't running (the value is going to change from 'stopped' to 'running'), so a refresh isn't needed, since starting the service will accomplish the same thing. I suspect that's why it's going through and unscheduling a previously scheduled refresh of the service.

This is unrelated to the problem that you're having, where the service appears to be failing to start due to the unknown config parameter. I would suggest finding where exactly that parameter is on the target system and then start looking into what is managing that file and that specific setting.

edit flag offensive delete link more


Thank you very much for your explanation! That has helped me understand what is going on. Also thank you for your suggestions for my specific problem!

corywink gravatar imagecorywink ( 2017-05-09 17:25:17 -0600 )edit

answered 2017-05-09 17:29:07 -0600

corywink gravatar image

The answer to my actual question is above by smarlow. As a note to anyone who is having my same issue with elasticsearch, I checked to make sure my version of elasticsearch was the most recent in my Puppetfile and it wasn't. So after updating that it fixed the issue and the service started. So as I am unsure as to what directly caused it, I know what fixed it for me.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2017-05-09 14:19:22 -0600

Seen: 1,010 times

Last updated: May 09 '17