similar to: how to disable runinterval option

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! 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"

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

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

Hello All I gather that the number of times the daemon checks in is controlled via runinterval (default 1800 seconds) Further, splay (and splaylimit) sets if a pseudo random time is used before checking in. BUT does splay have any meaning if i can not set when the daemon should attempt to check in? Or can i set the check-in time (i may have just missed the option)? cheers chakkerz

Hi all, I''ve set up a Puppet environment with a master managing around 80 agents. I would like to set a limit on the number of agents that can be performing puppet runs at any given moment...so, for example, if there are already 3 puppet runs ongoing, the 4th agent should be put on hold until one of the 3 runs finishes. Is there a way to configure this? It would be perfect if it can be

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

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.

I have a substantial number of Windows hosts running puppet 3.1.1 with the following in their puppet.conf: runinterval = 1800 > splay = true > splaylimit = 900 However in checking puppet logs, I''m finding that these hosts are dialing in at 30 minute intervals +/- 5-10 seconds. Can someone provide me an example puppet.conf that is properly implementing the splay feature on a

Here is my class class puppetconf { file { "/etc/puppet/puppetd.conf": mode => 644, owner => root, group => root, source => "puppet://puppet/cci/etc/puppet/puppetd.conf", notify => exec[puppet_restart] } file { "/etc/init.d/puppet": mode => 755, owner => root, group => root,

Hi, I''m still writing my djbdns module, I came to the following design issue with master and slave tinydns. Normally there is no such master and slave distinction in djbdns: all tinydns instance are equal. Usually one instance on one host is considered the master on, which the RR are changed, and when you need to propagate them, you rsync the datas to the other hosts, where they will be

Folks, I have installed puppet my network and it works great .. I have configured it such a way that when I make changes in the server source fiels..it gets updated in teh puppet clients. As the document reads the puppet clients checks for any changes from the server every 30 mins. But is there is any opiton of changing this value to lesser time .. say 15 mins .. or is there opiton for the

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#

Dear readers, When I have made a change to a template, class or file, is it then possible to push this change to the node(s), so they get the changes now? I would like to be able to push the change from the master, and not have to login to each node and pull. Is that possible? Hugs, Sandra -- You received this message because you are subscribed to the Google Groups "Puppet Users"

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

I have a test setup like this: host ======= *puppet-idc*: Ubuntu 12.04 running ActiveMQ, Mcollective, puppet agent and server *puppet-node1*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node2*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node3*: CentOS 6.3 running MCollective and puppet agent I installed the *mcollective-plugins-puppetd plugin* on all *3 Ubuntu

I am running puppet 2.7.14 - CentOS 6 server, CentOS and windows 2008 R2 clients. I''m having problems with the "puppet kick" command - it works on linux clients, and on my windows box when "puppet agent --no-daemonize --verbose" is run from a command prompt. However, when I run it as a windows service, I get "Host blah failed: Connection refused -

When an error occurs in prerun_command, puppet continues execution instead of stopping. We can see the error at the log file, but puppet cotinues doing changes: puppetd[18430]: Failed to prepare catalog: Could not run command from prerun_command: Execution of ''/path/to/command'' returned 1: We want to prevent changes when an error occurs in prerun_command. Our puppet.conf:

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

Hi, I am looking for a way, i.e. best practice for managing config changes safely and efficiently. Something like clever module organization could certainly help, but I am looking for something else as well: Is it possible to set up puppetd in a way, that it just listens and reports, but does not apply config changes automatically, and in the same time has the ability to trigger it somehow?