RE: [Puppet Users] RE: enterprise puppet architecture

2012-02-23 Thread Steve Shipway
Your Puppet master has twice the CPU of ours; but more importantly, you have far simpler manifests. Ours are very complex, and can take 20seconds on average to build - some taking a minute for the whole process to finish. We're going to completely redesign our setup, as per the instructionsin t

Re: [Puppet Users] Announce: Puppet 2.7.11 Available [security/maintenance update]

2012-02-23 Thread hai wu
It says bug 12572 is fixed in 2.7.11, but this is not the case. It seems the released RPM packages for RHEL6 (both binary and source RPM) do not contain the real fix here at https://github.com/puppetlabs/puppet/commit/411828be395a68d70fec634fa8d8ff12572e8501. I still see the old code .. On Wed,

[Puppet Users] Mounts occasionally not applied on first run

2012-02-23 Thread Gonzalo Servat
Hi All, Strange problem specifically to do with mounts. When I run Puppet for the first time on a server, occasionally everything will get applied except for mounts, and other times mounts are applied as part of the first run. No errors in /var/log/messages unfortunately. Has anyone else experien

Re: [Puppet Users] Sorted hash in template example

2012-02-23 Thread Nathan Powell
On Thu, Feb 23, 2012 at 5:20 PM, Jared Curtis wrote: > Does anyone have a better solution? Better? I dunno. But an array of hashes will do what you want as well. dbs = [{:foo => 'bar'}, {:hai => 'bai'} ] dbs[0] etc. -- Nathan Powell Linux System Administrator "Now I see it clearly. My who

Re: [Puppet Users] 32bit and 64bit version of a package

2012-02-23 Thread Nathan Powell
On Thu, Feb 23, 2012 at 5:57 PM, Alan Laird wrote: > I'm trying to write a recipe to install the latest libstdc++ in both > 32bit and 64bit flavors and running into issues.  Yum only wants to > install the 64bit version if I do: > > yum install libstdc++ > > If I do something like: > > package { "

[Puppet Users] Announce: Facter 1.6.6 Available

2012-02-23 Thread Matthaus Litteken
Facter 1.6.6 is a maintenance release with fixes, refactoring and packaging improvements. It includes contributions from the following people: Daniel Pittman, Jeremy Katz, Josh Cooper, Moses Mendoza This release is available for download at: http://downloads.puppetlabs.com/facter/facter-1.6.6.ta

[Puppet Users] 32bit and 64bit version of a package

2012-02-23 Thread Alan Laird
Hi, I'm trying to write a recipe to install the latest libstdc++ in both 32bit and 64bit flavors and running into issues. Yum only wants to install the 64bit version if I do: yum install libstdc++ If I do something like: package { "libstdc++.i386" : ensure => latest } It tells me "nothing to

[Puppet Users] Sorted hash in template example

2012-02-23 Thread Jared Curtis
I'm building a module to handle django local_settings.py and I'm using a hash to store the database settings. The problem I ran into was the if I had multiple databases defined then it was possible for the config file to be recreated as the order of the databases in the hash wasn't guaranteed. To w

[Puppet Users] Connections from any host to puppetmaster server times out

2012-02-23 Thread weloki
Every time I try to do puppetd --test on a host to get configs from the puppetmaster server it fails with this error: Could not retrieve catalog from remote server: Connection timed out - connect(2) Of course running it on the puppetmaster server itself works fine, so it's some kind of netwo

Re: [Puppet Users] Re: node regex not working in 2.7.9

2012-02-23 Thread Christopher Johnston
I think I found my issue, we may have had doubling of node types. One file has node /someregex/, and another has node theactualhost, so could be that we are duplicating node definition/namespaces. -Chris On Thu, Feb 23, 2012 at 1:37 PM, Christopher Johnston wrote: > John, > > Thx for your repl

[Puppet Users] Re: Unresponsive Agents - PE 2.0

2012-02-23 Thread Robert Stinnett
And what do we do about that? I've restarted the services, even restarted the server and nothing comes back to life. Robert On Feb 23, 9:10 am, Kenneth Lo wrote: > If that's the case I believe your pe-puppet-dashboard-workers service died > somehow in your master. > > --KL > > On 2/23/12 9:51

[Puppet Users] hiera-redis

2012-02-23 Thread windowsrefund
A Redis backend for Hiera http://github.com/reliantsecurity/hiera-redis enjoy! -- 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 p

Re: [Puppet Users] Error 400 on SERVER: Cannot append, variable node_data is defined in this scope at

2012-02-23 Thread M. Piscaer
Thanks for the response, I see that I made an typo.. The parameter nodes_data needs to be node_data as I have corrected below. But the error stands. -- testnode.pp -- node testnode { class { 'testclass': node_data => { 'node1' => { 'server' => '

[Puppet Users] Re: Deploying puppet via NFS

2012-02-23 Thread Forrie
I just did a basic find statement and found: # pwd /local/lib/ruby/gems/1.8/gems/puppet-2.7.11 # find . -exec grep -i site_ruby {} \; SITELIBDIR="/usr/lib/ruby/site_ruby/1.8" sitelibdir = $LOAD_PATH.find { |x| x =~ /site_ruby/ } sitelibdir = File.join(libdir, "site_ruby")

[Puppet Users] Re: Deploying puppet via NFS

2012-02-23 Thread Forrie
This must have to do with an include path, as here is where I find the code: /local/lib/ruby/site_ruby/1.8/rubygems/gem_openssl.rb it's been a while, but I think the SITE_RUBY include is configured somewhere - and that may be the issue. -- You received this message because you are subscribed to

Re: [Puppet Users] Error 400 on SERVER: Cannot append, variable node_data is defined in this scope at

2012-02-23 Thread Walter Heck
Where you call the class you mention nodes_data, and inside the class it's node_data. Unless this is not a one-to-one copy-paste that might be your problem? On Wed, Feb 22, 2012 at 15:21, M. Piscaer wrote: > Hi, > > I have an problem that I can't get resolved. I have an hash like > www.krzywans

[Puppet Users] Re: Deploying puppet via NFS

2012-02-23 Thread Forrie
> This is probably not an issue with the executable search path, but > rather with the Ruby path.  It looks like whichever Ruby interpreter > you are using to run Puppet is unable to find one of the files > (probably openssl.rb) that it expects to see in the Ruby library.  The > Ruby interpreter i

Re: [Puppet Users] Re: node regex not working in 2.7.9

2012-02-23 Thread Christopher Johnston
John, Thx for your reply, yea putting notifies in would be useful but simply seeing the class not get run or not included in classes.txt is also an indicator that its not working. I actually have a few regex for standard hostnames in our company here, simple stuff that is service oriented dev*, e

Re: [Puppet Users] Re: Unresponsive Agents - PE 2.0

2012-02-23 Thread Kenneth Lo
If that's the case I believe your pe-puppet-dashboard-workers service died somehow in your master. --KL On 2/23/12 9:51 AM, "Robert Stinnett" wrote: >We are using RHEL - 2.6.18-238.1.1.0.1.el5xen > >I do not know of any recent kernel patches (let me put it this way -- >I didn't make any!). > >I

[Puppet Users] Re: Deploying puppet via NFS

2012-02-23 Thread jcbollinger
On Feb 22, 6:50 pm, Forrie wrote: > I'm attempting to deploy puppet via an NFS share. It's on a local-only > network, and it will contain only ruby (gems) and whatever is needed. > > Seems simple enough, but tonight I am having an issue with this error: > > # service puppet start > Starting pupp

Re: [Puppet Users] hiera for defines?

2012-02-23 Thread Nigel Kersten
On Thu, Feb 23, 2012 at 5:21 AM, Markus Falb wrote: > > And Question 3, finally: Does it make sense to you what I am trying to > do, actually? It feels significantly simpler for you to use hiera to pick out values that you then pass to instances of defines, rather than baking hiera into the def

[Puppet Users] Re: Unresponsive Agents - PE 2.0

2012-02-23 Thread Robert Stinnett
We are using RHEL - 2.6.18-238.1.1.0.1.el5xen I do not know of any recent kernel patches (let me put it this way -- I didn't make any!). If I go to the "Live Management" part of the dashboard I can control the agents, etc -- but they won't do anything in the dashboard view and it shows up as over

[Puppet Users] Re: node regex not working in 2.7.9

2012-02-23 Thread jcbollinger
On Feb 22, 7:42 pm, Christopher Johnston wrote: > Anyone know of any issues in 2.7.9 when trying to use a regex pattern for > matching a hostname?  If I specify the following below the client never > loads the proper class, but if I put the fully qualified name in it works > fine. > > Fails: > >

[Puppet Users] Re: node regex not working in 2.7.9

2012-02-23 Thread Christopher Johnston
Anyone have any ideas here? All these manifests worked fine in 2.5 puppet and suddenly broke in 2.7.9 when we upgraded. On Feb 22, 2012, at 8:42 PM, Christopher Johnston wrote: > Anyone know of any issues in 2.7.9 when trying to use a regex pattern for > matching a hostname? If I specify

Re: [Puppet Users] hiera for defines?

2012-02-23 Thread Felix Frank
Hi, On 02/23/2012 02:21 PM, Markus Falb wrote: > Does it make sense to you what I am trying to > do, actually? no. Not at that degree of obfuscation, at least ;-) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send emai

Re: [Puppet Users] Re: "SSLv3 read server certificate B: certificate verify failed." -- Not time related

2012-02-23 Thread Felix Frank
Hi, On 02/22/2012 08:58 PM, Jon Davis wrote: > How can I track down where the issue for this is? it's always troublesome, but the only clean approach I'm aware of is "openssl s_client" and "openssl x509" to carefully compare what the master is presenting when the agent connects to whatever the ag

[Puppet Users] Re: Change user password only on systems where they exist

2012-02-23 Thread jcbollinger
On Feb 22, 9:49 pm, Romeo Theriault wrote: > Hi, We're just getting started with puppet and one of the things we'd > like to automate across a mix of Solaris and RHEL boxes is resetting a > users password. But we only want to reset the users password on the > boxes they already exist on. We don'

Re: [Puppet Users] "SSLv3 read server certificate B: certificate verify failed." -- Not time related

2012-02-23 Thread Mukul Malhotra
Just remove the certificates from the client & server from /var/lib/puppet/ssl/* & it will be ok. mukulm On Wed, Feb 22, 2012 at 6:26 AM, Jon Davis wrote: > I recently built, added to puppet and then nuked a server. Before I > re-added the machine (after I rebuilt it, with the same name), I w

[Puppet Users] hiera for defines?

2012-02-23 Thread Markus Falb
Hi, I thinking about how I could use hiera and I cant work it out, so I would like to ask for some enlightenment. class a {... $x = hiera('x') ...} define a::b ( $x = hiera('x') {...} define a::c ( $x = hiera('x') {...} include a a::b { "b": } a::c { "c": } so I thought about a directory structu

Re: [Puppet Users] Best way to test changes?

2012-02-23 Thread Felix Frank
Hi, On 02/23/2012 01:27 PM, Gonzalo Servat wrote: > On Thu, Feb 23, 2012 at 11:09 PM, jimbob palmer > wrote: > > I'm worried about making bad changes to a module which will impact > lots of hosts. > > How can I avoid this? > > Ideally I'd like eve

Re: [Puppet Users] Best way to test changes?

2012-02-23 Thread Gonzalo Servat
On Thu, Feb 23, 2012 at 11:09 PM, jimbob palmer wrote: > I'm worried about making bad changes to a module which will impact > lots of hosts. > > How can I avoid this? > > Ideally I'd like every node to run in noop, and then to approve the > changes if they look right. > Hi Jim, We're not current

[Puppet Users] Best way to test changes?

2012-02-23 Thread jimbob palmer
I'm worried about making bad changes to a module which will impact lots of hosts. How can I avoid this? Ideally I'd like every node to run in noop, and then to approve the changes if they look right. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet

Re: [Puppet Users] RE: enterprise puppet architecture

2012-02-23 Thread Luke Bigum
On 23/02/12 07:26, Steve Shipway wrote: Our Puppet system here is currently managing about 500 nodes. We anticipate about 1000 eventually. I have had to reduce the client frequency to once every 4 hours; it seems that the maximum that can be handled by a single (dual-CPU, 8GB) puppet master