similar to: puppet-3.2.2 runs fine - but doesn't work. 2.7.22 works fine.

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

hello: i currently am using Puppet to run some commands in a sequence. there are two sequences of exec resources. we found that we cannot use require => Exec and it does not work at all as expected. here is some sample code. exec { "exec-AAA": command => "/bin/true", returns => 0, notify => Exec["exec-BBB"], } exec { "exec-BBB":

I am at the end of my rope here so I pray to the gods that puppet-users can help. Using Debian apt-get install puppetmaster-passenger you get a fairly complete puppetmaster setup. I have the Pro Puppet book next to me and following Chapter 4 on setting up Puppet with Passenger I can see that apt has already done most of the ground work. For example the config.ru script is owned by puppet,

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

I''m not really sure the problem is a Plugin problem!! Note than a puppet client was installed, i change the setting of ip/hosname and try to re inscription the node to puppetmaster. I would like to understand what happen. The errors/warnings messages are not very easy to understand and sometime i''m lost. thank you for you advice. Eric Puppet version: 0.25.4-2ubuntu6

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, We''re using puppet from longer time, but now want to switch into stored configs. When I ran locally puppet on puppetmaster server, ie: puppet /var/lib/puppet/manifests/nodes.pp --debug it works smooth. When running client with debug I get message: root@puppet-client:~# puppet agent -v --fqdn=puppet-client.ig.local -- waitforcert 60 --onetime --no-daemonize --logdest console --test

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

Hi, I just upgrade to the next version of puppet (0.25.1-2) and now passenger broke (puppetmaster is still working). I have followed the guide on http://github.com/reductivelabs/puppet/tree/master/ext/rack but still I get a errorcode 500 with the error: support:~# puppetd --test --debug debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug:

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

Hello folks, I am getting this error on one of the clients, here''s all of the output. It was working on this client and today it stopped working. I cleaned the cert for this client puppetmaster by "puppetca --clean host.domain.com" and I removed the "/var/lib/puppet/ssl" directory so it would get new certs. But I still keep getting the same error as below. I have other

Hello, It seems that, for one reason or another, two thing happened: the postgres for puppetdb was dead, and the puppetmaster service was started, even though it''s run from apache. After a bit of cleanup, everything works now. Thanks for your suggestion, and sorry for the stupid issue. On Tue, Mar 26, 2013 at 11:43 AM, Keith Burdis <keith@burdis.org> wrote: > The agent only

- ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] - puppet-2.7.19-1.el5 I''m facing with the following error when starting puppet agent: **`puppet agent --server=puppetmaster.domain.com --no-daemonize --verbose --debug`** debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Puppet::Type::User::ProviderDirectoryservice:

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

Hello all, I''ve tried to run ''puppetrun'', but there seems something unconfigured regarding the certificates. The reverse way (puppetd pulls the config from puppetmasterd) works fine. The namespaceauth.conf on the client (where puppetd runs) is configured as follows: [puppetrunner] allow *.abc.net (also tried the calling host: puppet1.abc.net) But when I call

Hello all, I have what is certainly a stupid problem on my part. I have setup puppet in a test environment and it''s been working wonderfully. I am now in the process of moving this to our production systems and I have rebuilt our puppetmaster completely from scratch using the same modules/manifests, etc. from my test system. Unfortunately I am running into an issue with what I

Hi, My puppet master don''t want to start anymore. Any idea ? [root@puppetmaster requests]# puppet master --no-daemonize --debug debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug:

I am having troubles with getting puppetd running on some of my Solaris10 update 7 (05/2009) boxes. I use Jumpstart to build my servers, so the installation is repeatable, consistent, and automated, so it is especially confusing that some boxes work, and others don''t. I can ssh into both of these machines, so the host certs should be OK. As part of my installation, I download the

When I use the latest puppet 0.25.1 I got the same problem. This is what I do: 0. Install the Ubuntu 8.04 server with ssh, ruby, rdoc, libopenssl- ruby and git-core (which gets removed after clone). 1. Install the latest puppet from git repositories on both machines using git clone «git clone git://github.com/reductivelabs/puppet» and «git clone git://github.com/reductivelabs/facter» 2. Install it

Can someone, anyone, help me understand what it takes -- if indeed it''s even possible -- to use a custom CA with puppetmasterd. Such that, for every client it signs, the cert for that client actually says something meaningful about my organization, and was ultimately signed by our own root CA. I made a valid sub-CA for my puppet server, signed by my organization''s root CA. I