[Puppet Users] puppet and CPU
Hi, I am running puppet on my machines (mainly all rhel 5) and notice that puppet is waking the CPU up between 90 - 100 times a second. Is this normal?? it is waking the CPU up more than the kernel itself (when not under load)!! All puppet instances run as a daemon. Just as a test I also get the same results using red hat 6 beta. Does anyone else experience this? Any ideas on how to stop it? Regards. Nathan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Input sought on changing default vardir on OS X.
On Wed, 09 Jun 2010, Nigel Kersten wrote: 0.25.5 changed the default vardir from /var/puppet to /var/lib/puppet and it's caused the odd issue we have to fix in the Mac pkg preflights. After re-reading 'man hier' I'm tempted to change the default on OS X to: /var/db/puppet instead. Yes, /var/db/puppet seems to fit much better on BSDish systems. I dislike /var/lib/puppet because the things in there are not libraries. Maybe it's some sort of Linux standard, but that doesn't make it right. Anyway, it's OK for the default installation to use any directories it likes, provided it's easy to change at build time (and it is easy enough). --apb (Alan Barrett) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet and CPU
On Jun 10, 2010, at 12:02 AM, Nat wrote: Hi, I am running puppet on my machines (mainly all rhel 5) and notice that puppet is waking the CPU up between 90 - 100 times a second. Is this normal?? it is waking the CPU up more than the kernel itself (when not under load)!! All puppet instances run as a daemon. Just as a test I also get the same results using red hat 6 beta. Does anyone else experience this? Any ideas on how to stop it? Puppet is misconfigured under some disros to do bad stuff before it gets its first certificate. Do these machines have a certificate? Also, you are talking about the client right? Some people run the client with cron and tell it do do a single run and then quit. That should solve this problem if you are talking about the client. (If the client has a certificate) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet and CPU
Hi, On Thu, 2010-06-10 at 17:02 +1000, Nat wrote: Hi, I am running puppet on my machines (mainly all rhel 5) and notice that puppet is waking the CPU up between 90 - 100 times a second. Is this normal?? it is waking the CPU up more than the kernel itself (when not under load)!! All puppet instances run as a daemon. Just as a test I also get the same results using red hat 6 beta. It is not normal and comes from an issue in the Ruby interpreter (MRI) when compiled with --with-pthread. If you rebuild your ruby interpreter without this option (or use Ruby Enterprise Edition), there is no more any background CPU consumption when puppet sleeps between runs (and puppet runs faster too). More information (see the last comment): http://projects.puppetlabs.com/issues/1781 Hope that helps, -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet and ruby 1.9?
Hi Jesse, Thanks for the reply and shading a light on this... -Fernand On Jun 8, 3:42 pm, Jesse Wolfe je...@puppetlabs.com wrote: Short answer: we intend to support ruby 1.9, and some work is being done. The next major release (Rowlf a.k.a 2.6.0) will probably not be 1.9 ready, but the release after that should be. ~Jesse Wolfe On Tue, Jun 8, 2010 at 12:23 PM, DeRailed fernand.gali...@gmail.com wrote: Thanks! I guess this could be an option but will require some trickery to switch out the env for puppet vs client application running environment. Could be done using rvm, I guess, but was really interested on knowing where the road map stands for supporting ruby.1.9? Thanks! On Jun 7, 3:51 pm, Patrick Mohr kc7...@gmail.com wrote: On Jun 7, 2010, at 10:40 AM, DeRailed wrote: Hi, I am just getting started with puppet. Our stack runs on 1.9 and it seems puppet is not quiet there yet. I figure I could run puppetmaster on 1.8 but the clients will need to install and run 1.9. Any advise there? or are we doomed for the time being? I know very little about ruby so I could be wrong, but can't just install both versions? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: using modules from the forge (variable setting)
See, for instancehttp://www.puppetmanaged.org/documentation/Puppet_Common_Modules.htmlhttp://www.example42.com/puppet/howto.phphttp://plathrop.tertiusfamily.net/blog/2008/04/18/creating-puppet-mod...http://serialized.net/2009/07/puppet-module-patterns/ Thus, the approach for customizing each module you download from the forge will vary. They will each take different amounts of work to merge updated releases with your customizations. In the case of the module you're talking about, I think the intended approach is for you to modify params.pp. Thank you for the feedback Brian! I'm surely going to have a look at the urls you included! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] After reporting an issue
Hi, after filing a bug report and patch, how should I proceed? The report now has Status: Unreviewed and Votes: 1. Is this group the right place to discuss a filed issue and get those values changed? Regards, Robert. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Storeconfigs connection pool problem
I have the same issue as well, seems puppetqd uses sqlite for caching? On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe jason.robert.ko...@gmail.comwrote: Queuing support from ActiveMQ doesn't even make a difference for me -- I thought the purpose of adding the queuing support was to queue the data in puppetqd's memory and let that flush out to the database when it could. I'm still seeing this error from the puppetmaster (not puppetqd). err: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. Am I misunderstanding how puppetmasterd+puppetqd is supposed to function? On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley dan.car...@gmail.com wrote: On 9 June 2010 06:09, Jason Koppe jason.robert.ko...@gmail.com wrote: On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh joseph.e.mcdon...@gmail.com wrote: Daniel Kerwin wrote: Hi list, i just enabled storeconfigs and cannot use puppetrun on more than 5 hosts. When i try 6+ i get the error message: puppetmasterd[16209]: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. My Mysql setup allows a lot more connections (500). Any suggestions? Do you have the proper rubygem for mysql installed? I think on deb/ubuntu it's something like libmysql-ruby1.8. I'm having the same problem with the mysql gem installed and the gem appears to be in-use The gem version is a bit of a red herring, so long are using the gem and not Ruby's own connector. As the warning suggests, ActiveRecord's pool option simply needs raising if it's to be put under any strain at all. There is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's configuration. But it's not due to be delivered until 2.6/rowlf. I've been slipstreaming the patch into 0.25 myself because storeconfigs grinds to a halt without it in my environment. Given the simplicity of the diff and that it seems to be affecting a number of people I think it probably warrants being brought forward to 0.25. [0] http://projects.puppetlabs.com/issues/2568 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Jason Koppe jason.robert.ko...@gmail.com Cell (210) 445-8242 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] After reporting an issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Hi, after filing a bug report and patch, how should I proceed? The report now has Status: Unreviewed and Votes: 1. Is this group the right place to discuss a filed issue and get those values changed? Somebody neds to look at the bugreport and accept it. If you have a patch you can send it to the puppet-dev list, where all changes to puppet are discussed and if they are accepted your patch will be integrated. for more information have a look at: http://projects.puppetlabs.com/projects/puppet/wiki/Development_Development_Lifecycle cheers pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwREdgACgkQbwltcAfKi3+7ZwCgl0AJBRpJPxzHtyqk7BtpL2+I PrwAniS4Hwz6zleikzs1nJ7nn+l5SzaK =iYuM -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] After reporting an issue
Robert Scheer wrote: Hi, after filing a bug report and patch, how should I proceed? The report now has Status: Unreviewed and Votes: 1. Is this group the right place to discuss a filed issue and get those values changed? Also - what's the ticket? Sharing the URL here helps too. :) Regards James Turnbull -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Storeconfigs connection pool problem
I'm not sure, I can't seem to find README.queuing or much documentation about how it's supposed to work. I'll checkout the code this weekend if there aren't responses here. On Thu, Jun 10, 2010 at 9:32 AM, Christopher Johnston chjoh...@gmail.comwrote: I have the same issue as well, seems puppetqd uses sqlite for caching? On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe jason.robert.ko...@gmail.comwrote: Queuing support from ActiveMQ doesn't even make a difference for me -- I thought the purpose of adding the queuing support was to queue the data in puppetqd's memory and let that flush out to the database when it could. I'm still seeing this error from the puppetmaster (not puppetqd). err: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. Am I misunderstanding how puppetmasterd+puppetqd is supposed to function? On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley dan.car...@gmail.com wrote: On 9 June 2010 06:09, Jason Koppe jason.robert.ko...@gmail.com wrote: On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh joseph.e.mcdon...@gmail.com wrote: Daniel Kerwin wrote: Hi list, i just enabled storeconfigs and cannot use puppetrun on more than 5 hosts. When i try 6+ i get the error message: puppetmasterd[16209]: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. My Mysql setup allows a lot more connections (500). Any suggestions? Do you have the proper rubygem for mysql installed? I think on deb/ubuntu it's something like libmysql-ruby1.8. I'm having the same problem with the mysql gem installed and the gem appears to be in-use The gem version is a bit of a red herring, so long are using the gem and not Ruby's own connector. As the warning suggests, ActiveRecord's pool option simply needs raising if it's to be put under any strain at all. There is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's configuration. But it's not due to be delivered until 2.6/rowlf. I've been slipstreaming the patch into 0.25 myself because storeconfigs grinds to a halt without it in my environment. Given the simplicity of the diff and that it seems to be affecting a number of people I think it probably warrants being brought forward to 0.25. [0] http://projects.puppetlabs.com/issues/2568 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Jason Koppe jason.robert.ko...@gmail.com Cell (210) 445-8242 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Jason Koppe jason.robert.ko...@gmail.com Cell (210) 445-8242 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] exec hanging with CentOS4/64-bit
On Thu, Jun 10, 2010 at 12:53 PM, tean...@gmail.com wrote:
I have my sudoers setup as per the puppet training class recommendation:
file { /etc/sudoers.check:
content = template(etc/sudoers.erb),
mode = 440,
notify = Exec['sudo-check'],
}
exec { 'sudo-check':
path = '/usr/sbin:/usr/bin',
command = 'visudo -c -f /etc/sudoers.check',
unless = diff /etc/sudoers.check /etc/sudoers,
require = File['/etc/sudoers.check'],
}
file { /etc/sudoers:
ensure = present,
mode = 440,
require = [Exec['sudo-check'],Package[sudo]],
source = '/etc/sudoers.check',
}
That works wonderfully on three out of four of our OS/arch combinations
(Centos4/32-bit, Centos5/32-bit, Centos5/64-bit). However, on all of
our Centos4/64-bit machines, we have inconsistent hangs, with the
following error:
err: //etc/Exec[sudo-check]/unless: Check diff /etc/sudoers.check
/etc/sudoers exceeded timeout
David, this sounds awfully similar to the problem we had (and resolved) in
this thread:
http://groups.google.com/group/puppet-users/browse_thread/thread/7efd79bcd807de4c/dc9f8e42082cd0aa?#dc9f8e42082cd0aa
Running the diff by hand returns instantaneously, and it does not seem
to matter (for the purposes of the hanging) if there is an actual change
between sudoers.check and sudoers. I've run puppet using --debug, with
nothing more helpful showing up. I've also run it under strace, and
after pruning out all of the useless garbage, I'm left with not much. I
put it up at http://www.nwind.net/puppet.strace if you want to look.
The versions of ruby and puppet all match across all 4 platforms. Any
idea where I should look next?
David
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkwRQrcACgkQTKX6T9GeRTY2VgCcDonmQcJNu/Ij3OyqI3r/xSns
p+wAn21w8L/DuuV4cpTSWso5E+vUPLNi
=ohzu
-END PGP SIGNATURE-
--
nigel
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] exec hanging with CentOS4/64-bit
I have my sudoers setup as per the puppet training class recommendation:
file { /etc/sudoers.check:
content = template(etc/sudoers.erb),
mode = 440,
notify = Exec['sudo-check'],
}
exec { 'sudo-check':
path = '/usr/sbin:/usr/bin',
command = 'visudo -c -f /etc/sudoers.check',
unless = diff /etc/sudoers.check /etc/sudoers,
require = File['/etc/sudoers.check'],
}
file { /etc/sudoers:
ensure = present,
mode = 440,
require = [Exec['sudo-check'],Package[sudo]],
source = '/etc/sudoers.check',
}
That works wonderfully on three out of four of our OS/arch combinations
(Centos4/32-bit, Centos5/32-bit, Centos5/64-bit). However, on all of
our Centos4/64-bit machines, we have inconsistent hangs, with the
following error:
err: //etc/Exec[sudo-check]/unless: Check diff /etc/sudoers.check
/etc/sudoers exceeded timeout
Running the diff by hand returns instantaneously, and it does not seem
to matter (for the purposes of the hanging) if there is an actual change
between sudoers.check and sudoers. I've run puppet using --debug, with
nothing more helpful showing up. I've also run it under strace, and
after pruning out all of the useless garbage, I'm left with not much. I
put it up at http://www.nwind.net/puppet.strace if you want to look.
The versions of ruby and puppet all match across all 4 platforms. Any
idea where I should look next?
David
signature.asc
Description: Digital signature
Re: [Puppet Users] Client connecting to 2 puppet masters
On Thu, Jun 10, 2010 at 2:31 PM, Mark m...@digital-morphosis.com wrote: We have a server where the OS and base services are managed by an external company. They use puppet to handle this. We would also like to use puppet to manage the configuration of the server for which we are responsible, mostly apache virtual hosts. Is it possible to get the puppetd process to use multiple puppet masters? Or if this is not possible, would there be any issues with running multiple puppetd processes on the same server, each connecting to a different puppet master? So long as they're not treading on each other's resources, you should be ok. You can define your own config file for puppet in another location and invoke it with puppetd --config=/path/to/my/puppet.conf which will let you set a diferent vardir etc location so you're not stomping on each other. Thanks in advance Mark -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
