Puppet users - Mar 2010 - howto prevent puppetd fom scheduled runs

Hi all,

this one sounds silly , but so far I failed.:

starting my clients with "puppetd --listen" and puppetrun is working
fine. But puppetd is doing its runs every half an hour (per default)
despite I have configured "ignoreschedules=true"
Here comes my client puppet.conf
What am I doing wrong.

[main]
	environment = development
	server = puppet.domain.com
	listen = true
	ignoreschedules = true
[puppetd]
	listen = true
	ignoreschedules = true

thanks in advance

Lutz

-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 9 March 2010 15:11, Lutz Bergner <lutz.bergner@tomtom.com> wrote:
> Hi all,
>
> this one sounds silly , but so far I failed.:
>
> starting my clients with "puppetd --listen" and puppetrun is
working
> fine. But puppetd is doing its runs every half an hour (per default)
> despite I have configured "ignoreschedules=true"
> Here comes my client puppet.conf
> What am I doing wrong.
>
> [main]
>        environment = development
>        server = puppet.domain.com
>        listen = true
>        ignoreschedules = true
> [puppetd]
>        listen = true
>        ignoreschedules = true
>
> thanks in advance
>
There''s a bug raised for this.  At the moment the only way to get the
desired behaviour is to start with

puppetd --no-client

Matt

-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Tue, Mar 9, 2010 at 10:12 AM, Matt <mattmoran76@gmail.com>
wrote:
> On 9 March 2010 15:11, Lutz Bergner <lutz.bergner@tomtom.com> wrote:
>>
>> Hi all,
>>
>> this one sounds silly , but so far I failed.:
>>
>> starting my clients with "puppetd --listen" and puppetrun is
working
>> fine. But puppetd is doing its runs every half an hour (per default)
>> despite I have configured "ignoreschedules=true"
>> Here comes my client puppet.conf
>> What am I doing wrong.
>>
>> [main]
>>        environment = development
>>        server = puppet.domain.com
>>        listen = true
>>        ignoreschedules = true
>> [puppetd]
>>        listen = true
>>        ignoreschedules = true
>>
>> thanks in advance
>
> There''s a bug raised for this.  At the moment the only way to get
the
> desired behaviour is to start with
> puppetd --no-client
> Matt
I was going to say you could also configure Puppet to use no-op mode
and then trigger executions with puppetrun, though it appears this
isn''t possible.

http://projects.reductivelabs.com/issues/864

I rather like the idea :)

--Michael

-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 9 March 2010 15:17, Michael DeHaan <michael@reductivelabs.com> wrote:
> On Tue, Mar 9, 2010 at 10:12 AM, Matt <mattmoran76@gmail.com> wrote:
> > On 9 March 2010 15:11, Lutz Bergner <lutz.bergner@tomtom.com>
wrote:
> >>
> >> Hi all,
> >>
> >> this one sounds silly , but so far I failed.:
> >>
> >> starting my clients with "puppetd --listen" and
puppetrun is working
> >> fine. But puppetd is doing its runs every half an hour (per
default)
> >> despite I have configured "ignoreschedules=true"
> >> Here comes my client puppet.conf
> >> What am I doing wrong.
> >>
> >> [main]
> >>        environment = development
> >>        server = puppet.domain.com
> >>        listen = true
> >>        ignoreschedules = true
> >> [puppetd]
> >>        listen = true
> >>        ignoreschedules = true
> >>
> >> thanks in advance
> >
> > There''s a bug raised for this.  At the moment the only way to
get the
> > desired behaviour is to start with
> > puppetd --no-client
> > Matt
>
> I was going to say you could also configure Puppet to use no-op mode
> and then trigger executions with puppetrun, though it appears this
> isn''t possible.
>
> http://projects.reductivelabs.com/issues/864
>
> I rather like the idea :)
>
> + 1 That would be very handy!
-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Tue, 9 Mar 2010 07:11:01 -0800 (PST), Lutz Bergner
<lutz.bergner@tomtom.com> wrote:
> Hi all,
> 
> this one sounds silly , but so far I failed.:
> 
> starting my clients with "puppetd --listen" and puppetrun is
working
> fine. But puppetd is doing its runs every half an hour (per default)
> despite I have configured "ignoreschedules=true"
> Here comes my client puppet.conf
> What am I doing wrong.
Here''s what we do.

In sites.pp, we have this as the first line:

import "schedules"

This is /etc/puppet/manifests/schedules.pp:

schedule { never:
    period => never,
    repeat => 0
}

Then, back in sites.pp, we set a global default for files to use the
"never" schedule:

# Set global defaults
File { schedule => "never" }

You can do this for all resource types if you like.  Next, in our
puppet.conf on all systems, we added this, just so puppetd doesn''t try
to
connect pack to the puppet server every 30 minutes just to do nothing:

runinterval = 31536000

That''s 10 years, so puppetd will run once when it starts up (but not do
anything because of the default schedule), but then pretty much never check
back in on its own.  This is actually a hold-over from when we were using
puppetrun, but since we''re using puppetd with "--onetime
--no-daemonize"
it''s not really required anymore.

In order to make puppetd execute, we use --ignoreschedules on the command
line when running puppetd manually with --onetime.  We feel it''s a
pretty
good fail-safe, since a new admin who didn''t know our setup probably
wouldn''t think to use --ignoreschedules by default.

Hope this helps :)


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Many thanks to all , who responded. I''m going to evaluate the one or
other workaround now.

regards

Lutz

On Mar 9, 4:55 pm, James Cammarata <j...@sngx.net>
wrote:
> On Tue, 9 Mar 2010 07:11:01 -0800 (PST), Lutz Bergner
>
> <lutz.berg...@tomtom.com> wrote:
> > Hi all,
>
> > this one sounds silly , but so far I failed.:
>
> > starting my clients with "puppetd --listen" and puppetrun is
working
> > fine. But puppetd is doing its runs every half an hour (per default)
> > despite I have configured "ignoreschedules=true"
> > Here comes my client puppet.conf
> > What am I doing wrong.
>
> Here''s what we do.
>
> In sites.pp, we have this as the first line:
>
> import "schedules"
>
> This is /etc/puppet/manifests/schedules.pp:
>
> schedule { never:
>     period => never,
>     repeat => 0
>
> }
>
> Then, back in sites.pp, we set a global default for files to use the
> "never" schedule:
>
> # Set global defaults
> File { schedule => "never" }
>
> You can do this for all resource types if you like.  Next, in our
> puppet.conf on all systems, we added this, just so puppetd doesn''t
try to
> connect pack to the puppet server every 30 minutes just to do nothing:
>
> runinterval = 31536000
>
> That''s 10 years, so puppetd will run once when it starts up (but
not do
> anything because of the default schedule), but then pretty much never check
> back in on its own.  This is actually a hold-over from when we were using
> puppetrun, but since we''re using puppetd with "--onetime
--no-daemonize"
> it''s not really required anymore.
>
> In order to make puppetd execute, we use --ignoreschedules on the command
> line when running puppetd manually with --onetime.  We feel it''s a
pretty
> good fail-safe, since a new admin who didn''t know our setup
probably
> wouldn''t think to use --ignoreschedules by default.
>
> Hope this helps :)
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.