similar to: CSR and SSL Key being regenerated on a puppet node

I restarted puppetmasterd and it announced that the Cert does not match existing key ! [root@puppet ~]# puppetmasterd --verbose --no-daemonize info: Starting server for Puppet version 0.24.1 info: mount[files]: allowing 10.100.0.0/16 access info: mount[files]: allowing *.gridapp.com access info: mount[files]: allowing *.dev.gridapp.com access info: Retrieving existing certificate for

Sorry if this is obvious, but how can I have reports emailed to me- I want to know what each puppetd update is changing Thanks --e Eugene Ventimiglia Director of Systems GridApp Systems e: eventi@gridapp.com o: 646 452 4081 _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

I tried using it in a template: <%= memory %> and it put "0" in my file when i switched the variable name to the_memory, it worked Eugene Ventimiglia Director of Systems GridApp Systems e: eventi@gridapp.com o: 646 452 4081 _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com

Is there any way to do a simple search and replace on the puppetmaster server? I''m passing one IP address for one interface on a box, and attempting to set the second according to a convention we use, so I need something like $eth1_ip = `echo "10.100.6.99" | sed -r -e ''s/\.[0-9]+\.([0-9]+)$/.94.\1/''` # eth1_ip = 10.100.94.99 interface {

How can I do this?: foo { name: $bar => "frob" } define foo( $bar = false, $baz = false ) { if #$bar and $baz both defined $cmd = "frobnicate --bar=$bar --baz=$baz ${name}" else if #$bar defined $cmd = "frobnicate --bar=$bar ${name}" else if #$baz defined $cmd = "frobnicate --baz=$baz ${name}" else

I''ve been hacking at puppet for the past week or two, and came up with some great stuff, but I''m wondering if there''s a way to tie it all together To create a virtual machine for our company''s QA environment, I''m currently doing 3 things: #create a vm node vmsvr2 inherits default { include vmserver vmserver::vm {

I got the following error, but there''s no "cycle" I commented out File["/dev/sdb3"] and it works, but of course would choke if I ran it and the requirement were not met err: Could not apply complete catalog: Found cycles in the following relationships: File[/dev/sdb1] => Exec[echo -e "0,290\n,290\n," | sfdisk /dev/sdb] Here''s the node: node

this time when I try to connect the first node: [root@qaagt20 ~]# /etc/init.d/puppet start Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

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

Hi. When registering a new client with the puppetmaster I get the following error: [root@host ~]# puppetd --server puppetmaster --waitforcert 50 --test info: Creating a new certificate request for host info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/ host.pem warning: peer certificate won''t be verified in this SSL session err: Could not call puppetca.getcert:

I''m having difficulty getting my head around some CA issues My client has: [puppetd] ca_server=puppetca.mydomain.com and puppet resolves to a different machine. when puppet connects, it requests a signature from puppetca.mydomain.combut then on the next pass fails with the following: err: Could not retrieve catalog: Certificates were not trusted: SSL_connect returned=1 errno=0

Hi I am looking for quite a while now to run Puppet inside a vserver. The installation worked perfectly, but when I run a test I get this message: smb-configmaster / # puppetd --server 192.168.0.144 --waitforcert 60 --test /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Could not connect to 192.168.0.144 on port 8140

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

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!-- #msg dl { border: 1px #006 solid; background: #369; padding:

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

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. I have a client and server running Puppet 2.7.1 from GEMS (though the same problem occurs using the Ubuntu Lucid standard packages). I try to update the client against the server, and it freezes at this line: debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson Any idea what would cause that? I''m afraid I didn''t recognize any usable

I installed all required pkgs for Puppet & other configurations are done. I have issues getting certificates from server. vm1 is server & vm2 is client. In client I run, root@vm2# puppetd --server vm-devserver-18.dev.s.vonagenetworks.net -- waitforcert 60 --test and I see, /usr/lib/ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Could

Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd