similar to: managing config changes

Hi All, I was surprised to notice that a call to noop from puppetrun did not work as expected. on the agent side (for this case the server side..), I ran: puppetd --verbose --no-daemonize (where listen is set in the puppet.conf) on the puppet server side(in this case the client side), I ran: puppetrun --noop --host SERVER notice: SERVER(IP) triggered run info: Caching catalog at

Hello... I need some help with tags. as an example: # pseudo code class ssh { file { "/etc/ssh/ssh_config": # normal stuff tag("dangerous") } file { "/etc/ssh/sshd_config": # normal stuff tag("dangerous") } file { "/etc/ssh/ssh_known_hosts": # normal stuff tag("safe") } } on client: puppetd --tags

I''m trying to get puppetrun to work, without luck so far. I have my puppetmaster and clients working fine with the clients polling the master. Now I want to be able to force an update. Using version 0.23.2 On the client I set listen=true and created the namespaceauth.conf file. Restarted puppetd and it appears fine. On the master I run puppetrun as root and get root@plane:/etc/puppet#

I was wondering how to configure the puppet clients to only listen, not to periodically pull configs down from the puppetmaster. I''d rather push the configs out from the puppetmaster with puppetrun... At a guess I need to set runinterval to 0 in /etc/puppet/puppet.conf? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

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

Guys, I seriously could not find this topic in the documentation. What do you do when you need to force puppetd hosts get the new settings from puppetmasterd? What I found was only sending USR1 signal to the client process in order to make it refresh its configuration from the master. But I find it a bit inconvenient for a large amount of hosts. There is also puppetrun which, if I understand

Hi, I have Redhat 9 & RHEL 4.2 with puppet clients installed. When is use puppetd -test the updates get effected, but when when running them as daemon mode nothing happens. ## Nothing Happens - no change is detected /etc/init.d/puppet status puppetd (pid 15538) is running... ## When running manually puppetd -test the changes from server gets updated. Is there any

I''m using puppet 0.24.7-4. I have a situation where I have some very long running puppet runs in order to do upgrades (removing applications from load balancers gracefully, et cetera). My puppet runs triggered via puppetrun are finishing successfully: Jun 8 20:31:29 puppetd[10178]: Finished catalog run in 345.18 seconds Puppetrun itself is timing out: err: Connection timeout calling

I''m thinking about how to set up the processes for Production puppet runs now. Being ultra-conservative here, we''d like to see what would happen before pressing the red button. I can run in noop mode, and everything is evaluated but nothing is done. A YAML report magically appears on the Puppetmaster which my script parses and spits out something the management can read

I was wondering how to trigger a configration run remotely. Is this possible? Looking through the docs, I see mention that puppet can listen on port 8139, but I don''t see that this is the case on my servers. Can someone please enlighten me as to the proper method of doing this, if it can indeed be done? Thanks!

The Big Picture doc says: When configuration needs to be "pushed" to the clients, the Server can be asked to attempt to trigger each client to request "pull" a new host configuration. How does this work? I''ve been using ''puppetd --test'' on the clients while building the manifest, but I''m getting close to going into production, and I

hi all , i want to disable runinterval option on puppetd . as i know , after every 1800 sec.( 30 mins) , puppet client pull configuration from puppet master . I want configuration to be pushed to puppet client when i wwould fire puppetrun on puppet master rather than after every 30 min , configuration pulled puppet client. runinterval :How often puppetd applies the client

hi,all I want the puppetd run in daemon only run by the puppetrun trigger, not schedule run . so how can do this ? what''s the maximum of the runinterval ? I want change this option to do this. Please help me . -- Huang Mingyou

Hello All, I am trying to put puppet into push mode only. The instructions I''ve seen have said to put listen=true in puppet.conf but that doesn''t seem to have stopped the pull every 30 minutes. What else needs to be set? Thanks, Jim -- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines.

Hello all, I have a little problem with the --listen option. Id like my client servers to update only when I run puppetrun on the puppetmaster server. So far, I tried: puppetd --listen --server mymasterserver -v (on the client server) Then: puppetrun --host myclientserver The updates runs ok... but the client check for updates again every 30 mins or so and I dont want him to do so. I tried:

Hello! By default puppet node connects to server periodically and looks if there is something execute. I''m wondering is it possible to make puppet clients not connect to server themselves? So that it would be possible to update a node only with puppetrun nodename. --- WBR, Sergey -- You received this message because you are subscribed to the Google Groups "Puppet Users"

I''ve tried this on two different setups all running 0.22.1. One group is Ubuntu/OpenBSD the other is RHEL4/RHEL4. Master has signed client certs. puppetd works fine from client. If I run from the server side: root@server:~# puppetrun --host client_host.example.com Failed to load ruby LDAP library. LDAP functionality will not be available Triggering client_host.example.com Host

Group - I''m putting a presentation together for $work (a large .gov) and I want to make sure I get my facts (pun intended) straight ... Are the following steps for Facter-Client-Server interaction correct (I have a feeling not): 1. Client puppet run is initiated (via regular schedule, puppetrun, or puppetd) 2. The client contacts the server and downloads any custom facts it does not

Hi, I''ve got some problems with setting up environments. On the master: [main] [...] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [...] environments = production,staging [production] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [staging] manifestdir = /opt/puppet-staging/manifests modulepath = /opt/puppet-staging/modules [puppetmasterd]

Hi, I''m running multiple vservers and have some aspects managed via puppet. I noticed that puppetd consumes from 20 to 60 mb RAM and the longer the process runs, the more RAM it takes. It looks like 60MB is the top what I measured. Having a couple of vservers (11 in my case) this can already take up to 500MB just for puppet! I''m wondering if there''s any downside in