You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sensu::server::service class will correctly set ensure and enable but when notifying the class puppet will log confusing lines:
Notice: /Stage[main]/Sensu::Server::Service/Service[sensu-server]: Triggered 'refresh' from 1 events
when in fact what it's doing is the right thing, it notices that the service is stopped and does not restart it:
Debug: Executing '/etc/init.d/sensu-api status'
Debug: Service[sensu-server](provider=upstart): Could not find sensu-server.conf in /etc/init
Debug: Service[sensu-server](provider=upstart): Could not find sensu-server.conf in /etc/init.d
Debug: Service[sensu-server](provider=upstart): Could not find sensu-server in /etc/init
Debug: Executing '/etc/init.d/sensu-server status'
Debug: Executing '/etc/init.d/sensu-server status'
Debug: /Stage[main]/Sensu::Server::Service/Service[sensu-server]: Skipping restart; service is not running
Notice: /Stage[main]/Sensu::Server::Service/Service[sensu-server]: Triggered 'refresh' from 1 events
To avoid the confusing message I think the server::service class should only be notified if $sensu::server is true
The text was updated successfully, but these errors were encountered:
https://github.com/sensu/sensu-puppet/blob/master/manifests/check.pp#L119 will notify the sensu::server::service class whenever a check changes.
The sensu::server::service class will correctly set ensure and enable but when notifying the class puppet will log confusing lines:
when in fact what it's doing is the right thing, it notices that the service is stopped and does not restart it:
To avoid the confusing message I think the server::service class should only be notified if $sensu::server is true
The text was updated successfully, but these errors were encountered: