Skip to content
This repository has been archived by the owner on Feb 4, 2020. It is now read-only.

Service enable loop #76

Closed
dzeleski opened this issue Aug 30, 2016 · 3 comments
Closed

Service enable loop #76

dzeleski opened this issue Aug 30, 2016 · 3 comments

Comments

@dzeleski
Copy link

Not exactly sure whats going on here but on RHEL 7 I am seeing on every puppet run the uchiwa service trying to be enabled for boot. In order to fix the problem I set the class to stop managing its services and did my own notify and service declaration:

https://github.com/Yelp/puppet-uchiwa/blob/master/manifests/service.pp

class { '::uchiwa':
    install_repo        => false,
    user                => 'sensu',
    pass                => 'sensu',
    port                => '3000',
    sensu_api_endpoints => $uchiwa_api_config,
    manage_services     => false,
    notify              => Service['uchiwa'],
  }
   service { ['uchiwa']:
    ensure   => 'running',
    enable   => true,
    provider => 'redhat',
  }

Also as a side note init.pp has better documentation then the readme file does. It would be cool if that could get ported over or at least an FYI stating there is more info there.

@solarkennedy
Copy link
Contributor

Do you know if this is still going on?

@dzeleski
Copy link
Author

We moved to enterprise and I dont have this issue there but we are not using this module anymore so I could not say unfortunately.

@jaxxstorm
Copy link

Doesn't happen for me, I think it was an issue with the systemd unit/init.d script in the old uchiwa releases. I think it can be closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants