Displaying 6 results from an estimated 6 matches for "pemerson".
Did you mean:
emerson
2009 Sep 22
6
Monitoring the puppetmaster
I''m using 0.24 with Webrick (in the process of migrating to 0.25 / passenger).
Occasionally, the puppetmasterd becomes unavailable, and we see error
messages along the lines of:
Could not call puppetmaster.getconfig: #<Errno::ECONNRESET: Connection
reset by peer>
I believe the puppetmasterd does not completely die, so it is still in
the process list.
I''m wondering what
2009 Jul 10
3
Tracking down ensure => running problem
I''m trying to figure out how "ensure => running" determines whether a
service is running or not (CentOS using init controlled services).
I have a custom service that has enable => running set on it:
service { "foo":
ensure => running,
enable => true
}
Every time puppet runs I see this:
notice: //Service[foo]/ensure: ensure changed
2010 Apr 09
2
Custom facts for a puppetmasterless environment
I see the instructions for creating custom facter recipes here:
http://projects.reductivelabs.com/projects/puppet/wiki/Adding_Facts
and in this thread, James Turnbull suggests that Facter might some day
support other languages besides ruby:
http://groups.google.com/group/puppet-users/browse_thread/thread/8c127ae8898d3bcf/c5ca551b77c4eb67?lnk=gst&q=facter+perl#c5ca551b77c4eb67
He writes:
2009 Jul 08
1
Recursively templating files in a directory
Suppose I have 100 files distributed recursively:
file { "/var/sample":
source => "puppet:///files/sample",
ensure => directory,
recurse => true
}
What I''d like to do is have all files inside the directory be templated:
file { "/var/sample":
content =>
2009 Jul 01
1
Multiple default providers for service: init, base; using init
I have a bunch of CentOS machines. In the process of puppetizing one of them
I''m getting this warning (more complete debug info at the end):
warning: Found multiple default providers for service: init, base; using
init
info: /Service[gmond]: Provider init does not support features enableable;
not managing attribute enable
Given that all of my instances are running the same OS and should
2009 Jun 08
4
Puppetrun timeout
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