Invalid service provider 'supervisor'

[amiri]

I am attempting to use the puppet-module-supervisor module, but I keep getting the following error:

Error: Parameter provider failed on Service[supervisor::starling]:
Invalid service provider 'supervisor' at
/vagrant/etc/puppet/modules/supervisor/manifests/service.pp:90
Wrapped exception:
Invalid service provider 'supervisor'

I have 3 "supervisor::service" services, and this is just the first one.

I can provide more detailed logs if necessary.

I installed the module from the tarball at

https://github.com/plathrop/puppet-module-supervisor/releases/download/v0.1.0/jimdo-supervisor-0.1.0.tar.gz

by simply untarring it into the module path. But it seems that my puppet run never installs or activates the service provider.

[fungusakafungus]

Hi @amiri, this error means that the file lib/puppet/provider/service/supervisor.rb, which is a puppet plugin, can not be found by puppet.

You could try to find out, where puppet looks for this file and if the file is there. Puppet searches for plugins in modulepath(docs: http://docs.puppetlabs.com/guides/plugins_in_modules.html).

How do you run puppet? puppet agent or puppet apply or something like that?

Seeing /vagrant/ in path I suppose that you are using the puppet provisioner of vagrant, so you could set VAGRANT_LOG=INFO in the environment to make vagrant more verbose and let it tell you how it is running puppet. The interesting setting here is --modulepath, is it set to something? What does your Vagrantfile looks like?

TL;DR:

• detailed logs -> yes, please
• try setting --modulepath

[amiri]

@fungusakafungus: Thank you so much for replying! I was quite lost.

I run puppet apply via a script. No master/client.

I made a little test service following the steps here:

http://stackoverflow.com/questions/8175758/puppet-not-recognising-my-module

Then for the hell of it, I chmod -Rf 777 everything in etc/puppet/modules/supervisor.

puppet found my module, then, and proceeded to make a bunch of other errors not directly relevant here. In other words, it was a permissions problem somewhere. So, I will now find out which file/directory was the problem.

Is there a correct permissions set for this module?

[fungusakafungus]

I know nothing about correct permission for this module.

If you are able and willing to reproduce the bug, please repeat the steps with chmod -v and post it here.