Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong service provider used on Linux Mint #194

rlipscombe opened this issue Jan 7, 2015 · 2 comments


None yet
2 participants
Copy link

commented Jan 7, 2015

When using the 'rabbitmq' ( cookbook, chef-solo (v11.16.4) fails with:

Error executing action `enable` on resource 'service[rabbitmq-server]'
File '/etc/init/rabbitmq-server.conf' does not exist

This is because chef assumes that Linux Mint uses upstart; for the rabbitmq package, it's still using init.d.

So the action [:enable] attribute does the wrong thing.

(Originally reported as chef/chef#2726)


This comment has been minimized.

Copy link

commented Jan 7, 2015

Ah, thanks for this. We don't test against Linux Mint. If you would like to put a PR in to have the support please do, but i'm planning on just focusing on what we support in

@jjasghar jjasghar closed this Jan 7, 2015


This comment has been minimized.

Copy link

commented Jan 7, 2015

I'd love to, but I'm unsure about the best way to fix this. At the moment, I've just put the following earlier in the run list:

if platform?("linuxmint")
    service node['rabbitmq']['service_name'] do
        provider Chef::Provider::Service::Debian

...which feels kinda dirty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.