you have a resources(template), that is setup to notify another
resource(service) which is not present. Now, notifications are only
triggered once the resource is changes, i.e. unless the template resource
is changed, the service restart notification wont be triggered. It seems
like for some reason your template is not changed in the first run, it
changes in the second run (which is a different issue). But also, you dont
have to service resource missing. Check your recipes, for a service
"testservice" resource, if its not there , then you might have to remove
the notification, or create that service resource. Also check if you are
supposed to include another recipe (if you find that the service is indeed
decalred in another recipe).
template “config.conf” do
notifies :restart ,"service[testservice]"
— somewhere in your cookbook you should have–, if not, then create one
service “testservice” do
On Thu, Jan 31, 2013 at 9:37 AM, Gabriel ss email@example.com wrote:
I’m having the following issue, hoping someone might be able to help.
When running chef-client in daemon mode, the first run goes perfect with
no errors. All runs after that, I get the following:
"Resource template[config.conf] is configured to notify resource
service[testservice] with action restart, but service[testservice] cannot
be found in the resource collection."
Chef: 10.12.0 RHEL 2.6.18-308.1.1.el5