I''m struggling once again with resource ordering with Puppet.
I''m using Puppet 3.2.4, v3.0.0 of the Puppetlabs RabbitMQ module and
v0.7.5 of the Sensu module. I''m trying to compose a system from these
modules that runs the Sensu server, as well as the RabbitMQ server. I have the
following relationships defined:
Service[''rabbitmq-server''] ->
Service[''sensu-client'']
Service[''rabbitmq-server''] ->
Service[''sensu-api'']
Service[''rabbitmq-server''] ->
Service[''sensu-dashboard'']
Service[''rabbitmq-server''] ->
Service[''sensu-server'']
However I''m consistently finding that Puppet is attempting to start
Service[sensu-api] before Service[rabbitmq-server]:
Notice: /Stage[main]/Sensu::Service::Server/Service[sensu-dashboard]/ensure:
ensure changed ''stopped'' to ''running''
Info: /Stage[main]/Sensu::Service::Server/Service[sensu-dashboard]:
Unscheduling refresh on Service[sensu-dashboard]
Error: Could not start Service[sensu-api]: Execution of
''/etc/init.d/sensu-api start'' returned 1:
Error: /Stage[main]/Sensu::Service::Server/Service[sensu-api]/ensure: change
from stopped to running failed: Could not start Service[sensu-api]: Execution of
''/etc/init.d/sensu-api start'' returned 1:
Notice: /Stage[main]/Rabbitmq::Service/Service[rabbitmq-server]/ensure:
ensure changed ''stopped'' to ''running''
Info: /Stage[main]/Rabbitmq::Service/Service[rabbitmq-server]: Unscheduling
refresh on Service[rabbitmq-server]
Notice: /Stage[main]/Sensu::Service::Server/Service[sensu-server]/ensure:
ensure changed ''stopped'' to ''running''
Info: /Stage[main]/Sensu::Service::Server/Service[sensu-server]:
Unscheduling refresh on Service[sensu-server]
Info: Class[Sensu::Service::Server]: Scheduling refresh of
Class[Sensu::Service::Client]
Info: Class[Sensu::Service::Client]: Scheduling refresh of
Service[sensu-client]
Notice: /Stage[main]/Sensu::Service::Client/Service[sensu-client]:
Dependency Service[sensu-api] has failures: true
Warning: /Stage[main]/Sensu::Service::Client/Service[sensu-client]: Skipping
because of failed dependencies
Notice: /Stage[main]/Sensu::Service::Client/Service[sensu-client]: Triggered
''refresh'' from 1 events
Notice: /Stage[main]/Sensu/Anchor[sensu::end]: Dependency Service[sensu-api]
has failures: true
Warning: /Stage[main]/Sensu/Anchor[sensu::end]: Skipping because of failed
dependencies
I''ve taken this down to the lowest-level resource and it''s
still failing. What am I doing wrong?
Thanks,
Brian
--
Brian Lalor
blalor@bravo5.org
http://github.com/blalor
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
On Sep 9, 2013, at 10:02 AM, Brian Lalor <blalor@bravo5.org> wrote:> I''m struggling once again with resource ordering with Puppet.*sigh* Looks like the if defined(Class[''rabbitmq::service'']) { … } guard I''ve got around these relationships is wrong. It''s gonna be that kind of week, isn''t it? :-( Sorry for the noise, everyone! -- Brian Lalor blalor@bravo5.org http://github.com/blalor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.