search for: puppetclients

Hi When using puppetrun to trigger machines to get and apply their configuration, it will only trigger the machine when executing puppetrun for the second time: puppetmaster # puppetrun --host puppetclient puppetclient log: -- snip Apr 13 08:19:49 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08

Hi Puppet-Team, first thanks for this great configuration management tool ! My name is Matt and i am on creating a puppet plugin for openQRM. The basic framework is already existing and working well so far. Now, after having it working ok once i now ran into a problem that my puppet-clients do not get their configuration any more from the puppetmasterd. What i saw on the puppetmasterd logs is :

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret

I''m trying to load balance multiple puppetmasters using apache and passenger as described in James''s book. Was able to get a single passenger server installation to work correctly. When I configure the frontend load balancer and backend workers, the backend workers does not authenticate even though I am passing the headers to it. curl -v -H "Accept: pson, yaml" \

Hello all, I''m running puppet for the first ime. I''ve finished the install but I''m stuck at the certificate part. The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet client (0.24.8-4.el5) is running on CentOS 5.3. After the install, from the client side, I''ve run: puppetd --server puppetmaster.domain.com --waitforcert 60 --test On the

Hi guys, I''m doing some hackish stuff with manually installing RPMs. Basically I''m pulling them down to /tmp and installing them using provider => rpm, then making the service check that the package is installed before it''ll start. Here are the relevant sections of the pp file: class tomcat inherits httpd { $tomcat_connectors_pkg = $architecture ? {

Hi, I would like to use Puppet in the cloud (think gogrid) to configure stem images. Virtual machines are created/destroyed on the fly under control of a load monitor. For this reason we cannot sign manually new Puppet clients, instead, we must use Puppet''s autosign feature. At the moment, Puppet just permits to filter client manifest requests with some regex over the hostname of the

Hi, I''m trying to puppet kick with class option. Pupper Master: puppetmaster.example.com Puppet Client1: host1.example.net Puppet Client2: host2.example.net But I get this error. --- [root@puppetmaster ~]# puppet kick --class test --debug test: host1.example.net.example.com, host2.example.net.example.com Triggering host1.example.net.example.com, host2.example.net.example.com Host

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

Seems straight forward enough but I keep getting errors. On a client... err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node ubuntu5.ttinet: LDAP Search failed on the puppet master... puppet.conf [master] # ENC (external node classificiations) node_terminus = ldap ldapnodes = true ldapclassattrs = puppetclass # LDAP ldapserver =

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

I''m trying to be able to use puppet to modify an existing firewall on a web server. The idea is that if I use puppet to do this, then if the machine ever has to be rebuilt, aside from backups, I have a documented configuration. I looked at the module that was on the wiki that had a perl program and what not, but I don''t think I''m clear on what my thinking should be

I''m trying to wrap my head around these files... do both of them need to reside on the client and master? are there any docs that describe these files and what all the option/ sections are and what they do? Thanks all.... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hello a newbie here. The situation is that: 2 machine one master one client Puppet 0.24.5 This my configuration: Client: /etc/puppet/puppetd.conf [puppetd] server = Asus-Vista-Box logdir = /var/log/puppet vardir = /var/lib/puppet rundir = /var/run master /etc/puppet/manifests/classes/sudo.pp class sudo { file { "/etc/sudoers": owner => "root",

I am attempting to move our test puppet installation from looking for node information in a manifest to LDAP. I followed the instructions at: https://reductivelabs.com/trac/puppet/wiki/LdapNodes and was able to get the puppet schema loaded into our LDAP. I can now query LDAP and modify/load data without any issues using the OpenLDAP tools. e.g. ldapsearch -h ldapdev1.domain.com -x

Hi, I''ve set up puppet to get node definitions from LDAP as per the docs. It''s been working well, but I now want to use fully qualified domain names instead of simple domain-less hostnames for the node name. I replaced the ou=Hosts entries with equivalent ones using FQDNs, restarted the puppetmasterd, and tried a "puppetd --test" from one of the nodes. However, I

I am running into a problem with my LDAP puppet setup with this error message: PuppetClient: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment DR: undefined method `to_sym'' for ["ENV1", "ENV2"]:Array PuppetMaster: err: Could not parse for environment DR: undefined method `to_sym'' for ["ENV1",

I have a problem today. In my business, i have more than 10 linux servers , each of which runs a puppet client. on my puppet master server， sometimes , i need trigger every server to update from puppet master right now , so i wirte a shell script to traversal each server to run command "puppet kick node_name.example.com", but some client will cause a timeout for a long time. I

I am banging my head against the wall for recently built hosts that are unable to verify the server''s certs. The usual is not working. on the puppet agent machine: find /var/lib/puppet/ssl -type f -delete on puppet master: puppetca --clean <new_host_cert> on agent: puppetd --server puppet --waitforcert 2 --no-daemonize -d -o on puppet master: puppetca --sign

> On Jul 6, 2007, at 1:36 PM, barsalou wrote: >> What I''d like to do is something like this: >> >> define task ( firewall: >> add rule add rule >> delete rule >> } >> >> node puppetclient { >> apply firewall >> } > Don''t think about it in terms of verbs, just stick to nouns. > What rules do you want to