similar to: Puppet 2.7.9 package for Solaris

In my experimental area at the moment - http://buildfarm.opencsw.org/experimental.html#markp It''s been submitted to the catalog though. --Mark -- 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

I have very strange problem. I set up puppet client on serveral servers but have problem with one of them. When I invoke: root@www ~ # puppet agent --server puppetmaster.domain.ltd --test notice: Ignoring --listen on onetime run info: Caching catalog for puppetclient.domain.ltd info: Applying configuration version ''1326444431'' notice: Finished catalog run in

Just rolled, so it''s in my experimental area at the mo. I''m just about to test it, others please feel free to do so too. http://buildfarm.opencsw.org/experimental.html#markp Once I''ve confirmed it''s OK I''ll push to the main catalog. You might like to hang on for that event. --Mark -- You received this message because you are subscribed to the

Just installed the puppet master server in and the client just installed the puppet I managed to sign the certificates root@Puppetmaster:/etc/puppet# puppet cert --list --all + "puppetclient" (96:9A:C3:8D:B6:72:A4:5F:01:AA:40:A9:95:3E:FB:D2) + "puppetmaster" (12:92:DF:EB:72:E5:DF:99:D8:22:CA:5F:22:3A:1D:61) at the time I create the file site.pp in / etc / puppet / manifests

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 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 have followed many tutorials including the ones provided by puppetlabs and I keep seeing the same issues. I began by installing puppet on machine: puppet001, and puppet master on machine: puppetMaster. The hosts files were then configured so that both machines were reachable by the machine name. The puppet.conf files were then updated, and a cert was generated and sent from puppet001 to

Hello, First of all I am new to the Puppet technology. I am trying to get my puppet agent (windows) to reach my puppet master (Linux) server. In this tutorial: http://docs.puppetlabs.com/learning/agent_master_basic.html It claims to test your puppet agent you need to use the ''puppet agent --test'' command. My result when I tried this is: C:\Program Files (x86)\Puppet

Hello, Have a fully working setup with mostly Linux clients running on a 2.7.x master all is good. Trying to join Solaris clients to this master yields:- info: Creating a new SSL key for <FQDN> warning: peer certificate won''t be verified in this SSL session info: Caching certificate for ca warning: peer certificate won''t be verified in this SSL session warning: peer

Hi, I just installed & configured puppet-dashboard as per the official documentation <http://docs.puppetlabs.com/dashboard/manual/1.2/>, but now my nodes cannot retrieve their catalog: [root@puppetnode-01 ~]# puppetd --debug --verbose --no-daemonize ... err: Could not retrieve catalog from remote server: Server hostname > ''puppetmaster-01.mydomain.com''

I am trying to setup Puppet + Mongrel on RHEL5. So far I have followed this document: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel_On_Enterprise_Linux The puppetmasters all start up and Apache starts up on 8140. However, when my client connects I get the following errors: [root@lv1764p puppet]# puppetd --server puppetdev.encana.com --no- daemonize -o -v info: Retrieving

Hello everyone, I''m a new user regarding puppet but I''m skilled with linux. I have setup a puppetmaster server and also have a puppet client for testing on a different box. /etc/sysconfig/puppet has been edited to reach puppetmaster with option PUPPET_SERVER=puppet.mydomain.cr (I''m in Costa Rica) On the puppetmaster I was able to see the client with puppetca

I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host''s catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache & Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts

I''m just starting a roll out of Puppet and I''m seeing a problem on maybe 25% of client nodes. The symptoms are that the clients stop updating. In the Puppetmaster log, I''m seeing things like: Feb 9 20:10:23 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9 20:40:41 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9

I revoked the certificate of one of the clients by issuing the following command on puppetmaster : puppet cert clean <hostname> Then tried to access the catalog from <hostname> via : puppet agent --server=puppet .... and I can still access the catalogs from the master without any error. I checked that the certificate is no longer there in the puppetmaster for this

Hi, I reinstalled puppet-server and am now getting these error messages from clients: err: /File[/var/lib/puppet/facts]: Failed to generate additional resources during transaction: No such file or directory - /var/lib/puppet/yaml/node err: /File[/var/lib/puppet/facts]: Failed to retrieve current state of resource: No such file or directory - /var/lib/puppet/yaml/node Could not describe /facts:

Hi, I have a the annoying problem that the puppet master cannot connect to itself. It fails with: puppet# puppetd --test err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: tlsv1 alert decrypt error History: I have had this problem on our old puppet server: puppet.domain.com. It was annoying but not critical. Recently I built a new

Hi! I''ve installed puppetmaster 2.7.13 on a server with CentOS 6.2 with a rpm supplied by yum.puppetlabs.com. I''ve setup a apache2 vhost with mod_ssl and passenger. The server is configured to autosign the cert requests. The agent installed on the puppetmaster''s server works fine. I''ve a second agent on a server which can sync with the server too. This

Hello, I am trying to build puppet on Amazon VPC and am getting this error pretty consistently. >sudo puppet agent --test --server=ip-10-0-1-83 --waitforcert 60 err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed warning: Not using cache on failed catalog err: Could not retrieve catalog;

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