similar to: rollbacks

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

I think that I''m running into the warning on external node support here but after a recent upgrade for my puppetmaster I get: puppetmasterd[19397]: Could not find aa0-006-4.foo.com with names aa0-006-4.foo.com, aa0-006-4 I''ve not changed puppetd.conf which contains: ldapnodes = true ldapserver = my.ldap.foo.com ldapbase = ou=hosts,dc=foo,dc=com I''ve not

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

hi,all I want set up a puppet HA structure. but if the puppetd can set more than one server address ,the work will be simple :D if one puppetmaster have error, the client can auto try the next. I think I can use the heartbeat or dns to do this same thing,but not so good. so I want know the puppetd can direct set in the configure file ? if not,will be add this option? -- Huang

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

Hello, I recently started deploying puppet on our server farm. It works wonderfully with RHEL4, Gentoo and Debian. I''m looking for a way to determine the state of all nodes. Say for example that I change a file on the puppetmaster which affects 200 nodes. Then I go to lunch. When I get back, I''d like to know which nodes have been updated and which have not. I asked this in

Greetings, Shouldn''t puppetd -o --ignoreschedules ... imply that splay* options are ignored :-) If that''s not the intended behavior could we get a --run-now that ignores splay* and schedules? Cheers, Ryan

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point

With both puppet-0.23.0 and 0.23.1 if I setup just the configuration file puppet.conf, none of the puppetd options seem to get parsed. I first noticed this when monit failed to start/stop services due to the lack of a pid file being generated (and mine is not in one of the usual places). I''m sure that something like the patch attached but I bet it breaks other assumptions :-) Cheers,

I made an attempt to switch to mongrel today and I''m running into a strange error message I can''t seem to track down: debug: puppetmaster: Setting servertype to ''mongrel'' Server is not a class Tracing through with the debugger shows: [snip] /foo/lib/gems/puppet-0.22.4/bin/puppetmasterd:248: case Puppet[:servertype] (rdb:1) n

I''ve been pondering how to handle our file distribution issues - we''re starting to roll puppet out, and I''d like to get it somewhat right from the start. I''ve been watching the list for a while, and observed ''complaints'' about the speed of the fileserver method when dealing with recursive directories. If I can avoid this, I''d

seems that the tracksite is down ? -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

Hi all, Hobbeswalsh on IRC has discovered a backward compatibility issue in 0.24.0, preventing 0.23.x clients working well with 0.24.0 servers. Specifically, you can''t specify relationships to builtin resources when the client is 0.23.x, although specifying relationships to defined resources still works. The problem is that prior to 0.24.0 there was no central class

Hi There, I''m implementing puppet for a large scale Enterprise, with a lot of sites and a lot of different setups (for about 1500 Linux and Solaris machines). Now, the time has come to get some management attention, and of course, the first question I''ll have is who else is using puppet.... So I thought it Worth''s a try to ask - who is using puppet in a large scale

Hi All, In my companies environment, we have multiple sites in multiple geographic locations, sometimes with high latency between the sites. I''m trying to come up with a solution that could provide puppet infrastructure to all sites nodes. ----a few assumptions--- - puppet manifest / configuration is fetched from a centralized version control system. - store db is needed (ssh keys,

I just started digging into puppet and it looks like puppet is using a pull model. You have a master server and clients talk to it to get config info. Is anyone out there using a push model? If not, why not? Are there security reasons you would use one over the other? It seems that cfengine also uses a push model, so I wondered if this is a "standard" or if there are specific

Hey, I just updated from the edge and it looks like this _issue_ has resurfaced. Yesterday things were working (stories and specs). No code base changes, only rspec and rspec_on_rails After updating today I now need to set <config.txn...fixtures> to false in the spec_helper.rb to get the specs running, the stories are fine. Looks like the fixture loading is trying to start a txn. I

I''m wondering if there is any easy way to run a command after everything else, something like: exec { when => "last" command => "/usr/local/bin/update", } Or even "run these commands in the following order", as the last step. The bottom line is that I''m trying to trigger certain behaviors after the state of the system has

I just discovered that puppet makes an assumption about which ruby ldap implementation is used. FWIW, ruby/ldap and not net/ldap is the preferred choice. Just curious, why choose on over the other? Cheers, Ryan

So one of the behaviors that seems to wedge puppetmasterd is if you re-initialize a client, the example here being that I installed an older version of puppet on a bunch of machines to test out how things work: * at some point in the past install older rev of puppet - client regiesters itself with the server, etc. - works fine. * recently, remove the old puppet in favor of a new version that