similar to: is_virtual selector

I''m having a strange issue: A new machine created this morning showed thi error: ON PUPPET AGENT [root@wso2greg ~]# puppet agent --environment=production --verbose --no-daemonize --debug Debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Failed to load library ''ldap'' for

Hi all, Could anyone help me at least start debugging this issue? All agents have the same error, but i can''t find anything on the master-side logs. And the agent-side logs are non-existent (/var/log/puppet is empty). Thanks. Versions: Master: Red Hat Enterprise Linux Server release 6.3 puppet-server-3.1.0-1.el6.noarch puppetdb-1.1.1-1.el6.noarch puppetdb-terminus-1.1.1-1.el6.noarch

Hi, I wrote a little "hello world" script and I am a little concerned by execution that hangs for long periods of time. *computer:* Windows XP Professional Service Pack 3 Intel(R) Xeon(R) CPU W3550 @ 3.07GHz 3.07GHz, 3.50 GB of RAM *init.pp:* class hello { notice(''Hello world!'') } *command line:* puppet apply --debug -e ''include hello''

Hi, i recently updated our windows 2008 r2 servers to puppet 3.3.0 . Im getting the following error* (only on our exchange 2010 db servers)*ever since: LevelMessageSourceFileLineTimeerrCould not retrieve local facts: undefined method `gsub'' for nil:NilClassPuppet13.09.2013 15:12 CESTerrFailed to apply catalog: Could not retrieve local facts: undefined method `gsub'' for

my base/default includes this ntp manifest # cat modules/ntp/manifests/ntp.pp # ntp.pp class ntp { case $operatingsystem { centos, redhat: { $service_name = ''ntpd'' $conf_file = ''ntp.conf.el'' } debian, ubuntu: { $service_name = ''ntp'' $conf_file = ''ntp.conf.debian'' } } package {

I am new to using puppet and having trouble when updating an agent from a master which has a lot of files. Usually the updates work, but when there are a lot of files I get this error when running: sudo puppetd --test --server puppet.example.local --trace --debug >>> debug: Failed to load library ''rubygems'' for feature ''rubygems'' debug: Failed to load

Hi, I currently have a MySQL database containing all Puppet storeconfigs. My intention is to migrate to PuppetDB on a PostgreSQL server, so the first step is to use the ''storeconfigs'' face to export all the DB to a file PuppetDB can later consume. But the ''puppet storeconfigs export'' command always ends up being killed, I suspect due to some sort of OOM

Hi, i''m a newbie about Puppet( 1 month ~) i got error on generate temp file, i''ll explain my situation: -i have a puppetmaster(version: 3.3.0),executed on root and a puppet agent(version 2.7) provisioning by vagrant,executed on root -my site.pp, where webserv is a parametrized class, and typews is a parameter to choice nginx or lamp module, -i have my Enc node with path

If anybody knows? plese tell me what is a reason of this problem, i`m novice with puppet and sorry for my english=) have error on client: [root@node13 ~]# [root@node13 ~]# puppet agent --server=head02 --test warning: peer certificate won''t be verified in this SSL session warning: peer certificate won''t be verified in this SSL session info: Creating a new SSL certificate request

I''ve been confused by this question for near two days ...my puppet master version is 2.7.9-1.el6 and client versiong is 2.6.16-2.el5. This is what my command lines shows: *[root@agent1 ~]# puppet agent --server=edward --test --waitforce 30* info: Creating a new SSL key for agent1 warning: peer certificate won''t be verified in this SSL session info: Caching certificate for ca

whenever i run a test from client it finishes sucessfully but client is not getting any configuration changes from server [root@PROXY-02 tmp]# puppetd --noop --test notice: Ignoring --listen on onetime run info: Caching catalog for proxy-02.carnation.in info: Applying configuration version ''1327091881'' notice: Finished catalog run in 0.02 seconds [root@PROXY-03 modules]# puppet

I''ve gone over the documentation several times now and I can''t figure out how to ''apply'' a manifest to a client. The client does have a signed certificate but the only thing in the /etc/puppet folder on the client is an ssl directory. I have a manifest that works fine on the puppet ''master'' I have added the client into

on my puppet master server (v 2.7.17 , both server and client version) , the puppet agent can''t connect to itself. other clients connected to this puppet server are working fine. the hostname is puppet.domain.com [root@puppet /]# cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet

Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

For some reason I am unable to run "dry runs" of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not

Hi guys, I am fairly new to puppet and I am having a problem with one of the clients. I recently installed a new server that should get config from puppet master. All similar servers I recently installed didn''t have any problem. I installed puppet agent on the server and sent a sign request. SSL cert is signed but when I run puppetd manually I get the following: info: Retrieving

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

Hi guys, I''m trying to setup my first puppet installation and I''m running into problems. I''ve got the puppetmaster running on a fresh install of Centos 5.4. The puppet client is also on another Centos 5.4 server. Once I''ve signed the client certificate on the puppetmaster, the client seems to break. See below for the debug output from the client. Any clue as

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

Does anyone have some examples of using this create_resources function, https://github.com/puppetlabs/puppetlabs-create_resources, ? Based on the README example I can''t figure out exactly how to change from using defines to using this function. Maybe I misunderstand the purpose of create_resources...is it to replace defines, or is it to allow ENCs (for example) to use a define? Below