similar to: New package provider

I have a package provider which is a modified form of one of the default ones in the FreeBSD ports version of Puppet 2.6.1r3. I placed the provider in /usr/local/etc/puppet/modules/test/lib/puppet/ provider/ and ran puppetd on the client with the following command line: puppetd -o --no-daemonize -l console --pluginsync --server example.net I got the following output: notice:

I''m having some trouble with getting an ENC to work alongside site.pp: Even with a ''default'' node definition, and an ENC that only returns 0, regardless of input, consistently results in a ''cannot find node'' error. I''m wondering what I''ve missed here. I''ve tried to reduce everything to a ''base case'': and

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

hi,guys- I have a mysql database which stores host informations,so I wrote a function to get some values. - Here is the function rb(this function should return the type I defined in the database): #hosttype.rb require "mysql" module Puppet::Parser::Functions newfunction(:hosttype, :type => :rvalue, :doc => "Gets host type from db.") do |args|

Hi everyone, I''m learning Puppet and I want to configure ssh server with different port on different nodes. Puppet v2.7.1 I have created module ssh: content of modules/ssh/manifests/install.pp class ssh::install { package { "ssh": ensure => present, } } content of modules/ssh/manifests/service.pp class ssh::service { service { "ssh": ensure =>

Hi, I''ve got some problems with setting up environments. On the master: [main] [...] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [...] environments = production,staging [production] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [staging] manifestdir = /opt/puppet-staging/manifests modulepath = /opt/puppet-staging/modules [puppetmasterd]

I''m running into a weird issue with a custom package provider for PEAR. I''m using the provider I found here<https://raw.github.com/gist/305778/13f46dea6eba07e38778d7159644b4210ebe7bbe/pear.rb>and the provider itself works fine. I''ve got it stored on the Puppet master under /etc/puppet/modules/common/lib/provider/package/pear.rb and the puppet.conf has pluginsync

hello, we just wanted to rollout our new puppetized dmz. therefore i change all ip adresses from the test network to the live ips. after restarting puppetmasterd it seems that the fileserver hangs: client log: debug: //true_base/update-check/File[/sbin/update_check.pl]/require: requires Package[libmail-sendmail-perl] debug: //true_base/puppetd/File[/etc/puppet/puppetd.conf]/require: requires

With custom type ''vcsrepo'', I''ve been getting this error ever since I restarted my master box: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider at /etc/puppet/environments/local/modules/user_mpeebles/manifests/init.pp:56 on node 1001.milespeebles.org Warning: Not using cache on failed catalog Error: Could not

Hello, I have a CentOS 6.0 Virtualbox VM to package as a Vagrant box for testing Puppet manifests. The problem i''m having is with the user resource type not working with CentOS. I keep having an error message when setting the password for a user. Provider useradd does not support features manages_passwords; not managing attribute password I have both ruby-shadow and shadow-utils

Hi all, I am new to puppet and also newcomer in this group. I heart good things about puppet and I decided to give it a try 2 weeks now. After reading various documentation, I began using the complete configuration collection of puppet modules (thanks to David). But I have a problem with the munin module. It works fine, except that it seems to not export virtual ressources. Let me give more detail

So I''m having some problems with some of my manifests that I''ve been using for a while and I''m not entirely certain what''s going on. What appears to be happening is that puppet when it runs can''t see the value for one of the default facter facts (domain). I''m not real certain that this is the actual problem I think this is just how

Hi again, From examples I have gleaned the following snippet for manifests/site.pp Package { provider => $operatingsystem ? { FreeBSD => freebsd, #FreeBSD => ports, debian => aptitude, redhat => up2date }} Are there providers documented somewhere? I''m not sure where to look, and I haven''t come across it in my

Hi I am a newbie to puppet. I have tried an initial config serving a simple file & dir from the puppetmaster, but the client will not mount. What obvious mistake am I making, I wonder? puppetmaster is a DNS alias for osiris3. Config files: [root@osiris3 puppet]# cat fileserver.conf [config] path /data/puppet/manifests/files allow *.pinnacle.co.uk [root@osiris3 puppet]# cat puppet.conf

Hello Folks! I am trying to learn puppet. Installed the puppet 3.0.2 and configured one node as the master and the other as the client. Generated the certs and all that. But, I seem to be doing something wrong wrt to the init.pp file. Attached is exact error and my current server configuration. Any help in helping me fix this issue is appreciated: *[root@pupclient ~]# puppet agent --test*

Hello, I''ve just run into an issue I''m not able to solve. I need to have puppet install both the mysql package through yum, AND the mysql gem. Those are the pieces of my config as I''m trying to use it: package { ''mysql-all'': ensure => latest, name => ''mysql'', provider => yum, } package

Hi, I''m using yum as our package provider and having an issue. Puppet is complaining of the version, this is the code I''m trying to implement: $snmp_version = "5.3.2.2" package { "net-snmp": ensure => "${snmp_version}"; } On the client I got: debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensure debug:

I believe the error indicates that hiera was installed as a rubygem which is not supported on Puppet 3.x. Maybe the error will go away if you remove the hiera gems? I think I have gotten around it by adding ''require rubygems'' to the puppet executable. I''m copying the puppet-users mailing list b/c I am guessing this is a common problem. On Wed, May 1, 2013 at 12:35

I''m having a problem with a pypi package/the pip provider. The package name is riak_pb https://pypi.python.org/pypi/riak_pb/. The problem I''m having is puppet keeps installing/upgrading the package every run. I suspect it has something to do with the hyphen/underscore. I have also tried changing the riak_pb package name in the init.pp to riak-pb. The pypi API

Hi, I''ve been trying to pass the http_proxy_host option to puppet but it''s not taking. I have tried the following: sudo puppet apply --debug --verbose --http_proxy_host http://user:pass@fqdn.com.au --modulepath ''/tmp/vagrant-puppet/modules-0'' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose