Confused, does puppetrun require webrick or mongrel (please say no).
# puppetrun --host labhost --ping --foreground --debug
Failed to load ruby LDAP library. LDAP functionality will not be available
debug: Parsing /etc/puppet/puppet.conf
debug: Puppet::Network::Client::Runner: defining puppetrunne
On Sun, Jan 24, 2010 at 07:28:52PM -0600, Carl Caum wrote:
> Add:
>
> ignoreschedules = true
>
> to your puppet.conf. I think you can also set
>
> listen = true
>
> and that will disable runs and just run when triggered by authorized nodes.
> Others will know more about that than me. Anyon
I can offer two more options..
1. I didn't want to enable puppetd to start a whole webserver (puppetd
starts a webrick when listen=true) esp due to the amount of memory used, so
I wrote puppetlisten and puppetrun - which is based on a smaller footprint
daemon which does more or less th
I think that's only true for doing a puppet run on ALL hosts or a group of
hosts. For single host requests, puppetrun will work without using external
nodes.
On Jan 25, 2010, at 7:46 AM, Christopher Johnston wrote:
> I thought puppetrun _requires_ putting all your nodes into LDAP? Is that not
I thought puppetrun _requires_ putting all your nodes into LDAP? Is that
not the case anymore? (I am using version 0.24.8-4 from Fedora 10)
-Chris
On Sun, Jan 24, 2010 at 8:28 PM, Carl Caum wrote:
> Add:
>
> ignoreschedules = true
>
> to your puppet.conf. I think you can also set
>
> listen =
Add:
ignoreschedules = true
to your puppet.conf. I think you can also set
listen = true
and that will disable runs and just run when triggered by authorized nodes.
Others will know more about that than me. Anyone care to jump in?
On Jan 22, 2010, at 7:14 PM, Christopher Johnston wrote:
>
How do you disable autorun?
Sent from my iPhone
On Jan 22, 2010, at 3:29 PM, Carl Caum wrote:
I've run in to the same problem. I've started to solve this problem
by getting rid of puppetmasters and puppetd. Instead I'm building a
new management tool called Puppeteer. I'm almost ready to
I've run in to the same problem. I've started to solve this problem by getting
rid of puppetmasters and puppetd. Instead I'm building a new management tool
called Puppeteer. I'm almost ready to begin testing, but it's not ready for
others to try yet. I'll post to the list when it's read for
Hi,
I do not know if it's a bug, a feature or something I didn't
understood, but it's I can't update my clients hosts "synchronously".
What I mean by "synchronously" is that when I push a new configuration
on my master server, I do not know when my clients will be updated.
And it also appears that
