I am trying to make use of a custom type mentioned in the wiki page
http://projects.puppetlabs.com/projects/1/wiki/Sysctl_Patterns
I created the module sysctl, inserted the custom type in there and
created a simple manifest to make use of the introduced type.
I add the module to a client and start a puppetrun there.
I see the custom type being synced, but after that I get the error,
that the used type is unknown:
puppetd -t
info: Retrieving plugin
notice: /File[/var/lib/puppet/lib/puppet]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/provider]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl]/ensure:
created
notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl/parsed.rb]/
ensure: defined content as
''{md5}f1ad6c1cd610b6fe33fcd245759c09d1''
notice: /File[/var/lib/puppet/lib/puppet/type]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/type/sysctl.rb]/ensure:
defined content as ''{md5}65fe3deaf4e245b7a5f031dac3d73f4d''
info: Loading downloaded plugin /var/lib/puppet/lib/puppet/provider/
sysctl/parsed.rb
info: Loading downloaded plugin /var/lib/puppet/lib/puppet/type/
sysctl.rb
info: Redefining sysctl in Puppet::Type
info: Loading facts in proxyinfo
info: Loading facts in sapcheck
info: Loading facts in servicepack
info: Loading facts in proxyinfo
info: Loading facts in sapcheck
info: Loading facts in servicepack
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError:
Invalid resource type sysctl at /etc/puppet/development/modules/sysctl/
manifests/init.pp:4 on node myhost
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
My manifest is this:cat manifests/init.pp
class sysctl {
sysctl {
"kernel.shmni": val => "4096";
}
}
I am using puppet version 2.6.7 on master and client
It seems to me, that the path where de custom type has been placed
isn''t checked, then again, the used type might just not work on my
version of puppet.
I checked the docs on "custom types" and "plugins in
modules" , but
i''m a bit at a loss right now.
can someone point me in the right direction?
thx
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
If its a pure ruby provider, try running something like ''puppet agent -t --pluginsync'' on the server first, so it gets synced there. Then try your client again. The problem is your server isn''t scanning your modulepath for types ... its expecting types to be in its own libdir first. Hence why an pluginsync is needed ... ken. On Thu, Jul 7, 2011 at 12:18 PM, JohnW <boerma.j.w@gmail.com> wrote:> I am trying to make use of a custom type mentioned in the wiki page > http://projects.puppetlabs.com/projects/1/wiki/Sysctl_Patterns > > I created the module sysctl, inserted the custom type in there and > created a simple manifest to make use of the introduced type. > > I add the module to a client and start a puppetrun there. > I see the custom type being synced, but after that I get the error, > that the used type is unknown: > > puppetd -t > info: Retrieving plugin > notice: /File[/var/lib/puppet/lib/puppet]/ensure: created > notice: /File[/var/lib/puppet/lib/puppet/provider]/ensure: created > notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl]/ensure: > created > notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl/parsed.rb]/ > ensure: defined content as ''{md5}f1ad6c1cd610b6fe33fcd245759c09d1'' > notice: /File[/var/lib/puppet/lib/puppet/type]/ensure: created > notice: /File[/var/lib/puppet/lib/puppet/type/sysctl.rb]/ensure: > defined content as ''{md5}65fe3deaf4e245b7a5f031dac3d73f4d'' > info: Loading downloaded plugin /var/lib/puppet/lib/puppet/provider/ > sysctl/parsed.rb > info: Loading downloaded plugin /var/lib/puppet/lib/puppet/type/ > sysctl.rb > info: Redefining sysctl in Puppet::Type > info: Loading facts in proxyinfo > info: Loading facts in sapcheck > info: Loading facts in servicepack > info: Loading facts in proxyinfo > info: Loading facts in sapcheck > info: Loading facts in servicepack > err: Could not retrieve catalog from remote server: Error 400 on > SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: > Invalid resource type sysctl at /etc/puppet/development/modules/sysctl/ > manifests/init.pp:4 on node myhost > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > > My manifest is this:cat manifests/init.pp > class sysctl { > sysctl { > "kernel.shmni": val => "4096"; > } > } > > I am using puppet version 2.6.7 on master and client > > It seems to me, that the path where de custom type has been placed > isn''t checked, then again, the used type might just not work on my > version of puppet. > I checked the docs on "custom types" and "plugins in modules" , but > i''m a bit at a loss right now. > > can someone point me in the right direction? > > thx > > John > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Thanks Ken That did the trick. I was afraid I had to reinvent a wheel here, as I was a bit on a deadline John On Jul 7, 2:50 pm, Ken Barber <k...@puppetlabs.com> wrote:> If its a pure ruby provider, try running something like ''puppet agent > -t --pluginsync'' on the server first, so it gets synced there. Then > try your client again. > > The problem is your server isn''t scanning your modulepath for types > ... its expecting types to be in its own libdir first. Hence why an > pluginsync is needed ... > > ken. > > On Thu, Jul 7, 2011 at 12:18 PM, JohnW <boerma....@gmail.com> wrote: > > I am trying to make use of a custom type mentioned in the wiki page > >http://projects.puppetlabs.com/projects/1/wiki/Sysctl_Patterns > > > I created the module sysctl, inserted the custom type in there and > > created a simple manifest to make use of the introduced type. > > > I add the module to a client and start a puppetrun there. > > I see the custom type being synced, but after that I get the error, > > that the used type is unknown: > > > puppetd -t > > info: Retrieving plugin > > notice: /File[/var/lib/puppet/lib/puppet]/ensure: created > > notice: /File[/var/lib/puppet/lib/puppet/provider]/ensure: created > > notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl]/ensure: > > created > > notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl/parsed.rb]/ > > ensure: defined content as ''{md5}f1ad6c1cd610b6fe33fcd245759c09d1'' > > notice: /File[/var/lib/puppet/lib/puppet/type]/ensure: created > > notice: /File[/var/lib/puppet/lib/puppet/type/sysctl.rb]/ensure: > > defined content as ''{md5}65fe3deaf4e245b7a5f031dac3d73f4d'' > > info: Loading downloaded plugin /var/lib/puppet/lib/puppet/provider/ > > sysctl/parsed.rb > > info: Loading downloaded plugin /var/lib/puppet/lib/puppet/type/ > > sysctl.rb > > info: Redefining sysctl in Puppet::Type > > info: Loading facts in proxyinfo > > info: Loading facts in sapcheck > > info: Loading facts in servicepack > > info: Loading facts in proxyinfo > > info: Loading facts in sapcheck > > info: Loading facts in servicepack > > err: Could not retrieve catalog from remote server: Error 400 on > > SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: > > Invalid resource type sysctl at /etc/puppet/development/modules/sysctl/ > > manifests/init.pp:4 on node myhost > > warning: Not using cache on failed catalog > > err: Could not retrieve catalog; skipping run > > > My manifest is this:cat manifests/init.pp > > class sysctl { > > sysctl { > > "kernel.shmni": val => "4096"; > > } > > } > > > I am using puppet version 2.6.7 on master and client > > > It seems to me, that the path where de custom type has been placed > > isn''t checked, then again, the used type might just not work on my > > version of puppet. > > I checked the docs on "custom types" and "plugins in modules" , but > > i''m a bit at a loss right now. > > > can someone point me in the right direction? > > > thx > > > John > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ken Barber
2011-Jul-07 13:43 UTC
Re: [Puppet Users] Re: Problems with the use of custom types
The issue I think is here: http://projects.puppetlabs.com/issues/4409 But this is to do with 2.6+ and environments specifically. If you''re running an older puppet and a single environment, I believe this issue should been resolved by upgrading to 2.6+ - but I''m not 100% sure, so perhaps someone can correct me on that. ken. On Thu, Jul 7, 2011 at 2:31 PM, JohnW <boerma.j.w@gmail.com> wrote:> Thanks Ken > > That did the trick. > > I was afraid I had to reinvent a wheel here, as I was a bit on a > deadline > > John > > > On Jul 7, 2:50 pm, Ken Barber <k...@puppetlabs.com> wrote: >> If its a pure ruby provider, try running something like ''puppet agent >> -t --pluginsync'' on the server first, so it gets synced there. Then >> try your client again. >> >> The problem is your server isn''t scanning your modulepath for types >> ... its expecting types to be in its own libdir first. Hence why an >> pluginsync is needed ... >> >> ken. >> >> On Thu, Jul 7, 2011 at 12:18 PM, JohnW <boerma....@gmail.com> wrote: >> > I am trying to make use of a custom type mentioned in the wiki page >> >http://projects.puppetlabs.com/projects/1/wiki/Sysctl_Patterns >> >> > I created the module sysctl, inserted the custom type in there and >> > created a simple manifest to make use of the introduced type. >> >> > I add the module to a client and start a puppetrun there. >> > I see the custom type being synced, but after that I get the error, >> > that the used type is unknown: >> >> > puppetd -t >> > info: Retrieving plugin >> > notice: /File[/var/lib/puppet/lib/puppet]/ensure: created >> > notice: /File[/var/lib/puppet/lib/puppet/provider]/ensure: created >> > notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl]/ensure: >> > created >> > notice: /File[/var/lib/puppet/lib/puppet/provider/sysctl/parsed.rb]/ >> > ensure: defined content as ''{md5}f1ad6c1cd610b6fe33fcd245759c09d1'' >> > notice: /File[/var/lib/puppet/lib/puppet/type]/ensure: created >> > notice: /File[/var/lib/puppet/lib/puppet/type/sysctl.rb]/ensure: >> > defined content as ''{md5}65fe3deaf4e245b7a5f031dac3d73f4d'' >> > info: Loading downloaded plugin /var/lib/puppet/lib/puppet/provider/ >> > sysctl/parsed.rb >> > info: Loading downloaded plugin /var/lib/puppet/lib/puppet/type/ >> > sysctl.rb >> > info: Redefining sysctl in Puppet::Type >> > info: Loading facts in proxyinfo >> > info: Loading facts in sapcheck >> > info: Loading facts in servicepack >> > info: Loading facts in proxyinfo >> > info: Loading facts in sapcheck >> > info: Loading facts in servicepack >> > err: Could not retrieve catalog from remote server: Error 400 on >> > SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: >> > Invalid resource type sysctl at /etc/puppet/development/modules/sysctl/ >> > manifests/init.pp:4 on node myhost >> > warning: Not using cache on failed catalog >> > err: Could not retrieve catalog; skipping run >> >> > My manifest is this:cat manifests/init.pp >> > class sysctl { >> > sysctl { >> > "kernel.shmni": val => "4096"; >> > } >> > } >> >> > I am using puppet version 2.6.7 on master and client >> >> > It seems to me, that the path where de custom type has been placed >> > isn''t checked, then again, the used type might just not work on my >> > version of puppet. >> > I checked the docs on "custom types" and "plugins in modules" , but >> > i''m a bit at a loss right now. >> >> > can someone point me in the right direction? >> >> > thx >> >> > John >> >> > -- >> > You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> > To post to this group, send email to puppet-users@googlegroups.com. >> > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.