reload/restarting puppetd after puppet.conf change

[Derek Yarnell]

Subject basically says it all. Anyone have a good idea of how to get
puppetd restarted after installing a updated puppet.conf? Using the
Service types obviously doesn't work since puppet is already running.
Is there no, please reload your config on the next run option? I mean
there is always some screwing with a cronjob to just restart puppet once
and awhile but I dunno I was hoping for something more clean.

Thanks,
derek

--
--
Derek Yarnell

[Ohad Levy]

What is the problem you are trying to solve? afaik puppet reload its config file if it has changed.

saying that, I am a long cron based puppet user.. so I cant be 100% sure.
(I find cron based puppet to be far more effective).

cheers,
Ohad

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

[Derek Yarnell]

On 1/18/10 1:37 AM, Ohad Levy wrote:
> What is the problem you are trying to solve? afaik puppet reload its
> config file if it has changed.
>
> saying that, I am a long cron based puppet user.. so I cant be 100% sure.
> (I find cron based puppet to be far more effective).
>

Yes, reloading the puppet.conf for a long running puppetd. You are
obviously using the splay options if you are running from cron? Are
most people running puppetd from cron and not demonizing?

[Rob McBroom]

On Jan 18, 2010, at 1:19 AM, Derek Yarnell wrote:

> Subject basically says it all. Anyone have a good idea of how to get puppetd restarted after installing a updated puppet.conf?

It’s automatic. Check the logs on the client.

I did this for a while, then undid it when I realized I had blown away puppet.conf on my puppet master. :)

--
Rob McBroom
<http://www.skurfer.com/>

[JL]

> It’s automatic. Check the logs on the client.

Is this true for puppetmasterd as well?

[Rob McBroom]

On Jan 20, 2010, at 4:15 PM, JL wrote:

> Is this true for puppetmasterd as well?

If I recall, my Puppet Master wasn’t destroyed until I restarted it (I think it ran for a while with a nearly empty config), so no. But that was a pretty stressful day, so I could be remembering wrong. :)

--
Rob McBroom
<http://www.skurfer.com/>

The magnitude of a problem does not affect its ownership.

[JL]

> If I recall, my Puppet Master wasn’t destroyed until I restarted it (I think it ran for a while with a nearly empty config), so no. But that was a pretty stressful day, so I could be remembering wrong. :)

It looks like puppetmasterd automatically reparses:

puppetmasterd[6163]: [ID 702911 local1.notice] Reparsing /etc/puppet/
puppet.conf

So I guess there is no need to restart puppetd or puppetmasterd on
puppet.conf changes. As there any definitive documentation on this?
Does anyone know if puppetmasterd should ever be restarted (for
example if tagmail.conf or fileserver.conf are changed)?

[Eric Gerlach]

I don't know about that, and I don't know if this is fixed in 0.25.x, but in
0.24.x if you changed the "listen" parameter in puppet.conf while puppetd was
running it would not change its listen state. A restart was required. I
think.

Cheers,

--
Eric Gerlach, Network Administrator
Federation of Students
University of Waterloo
p: (519) 888-4567 x36329
e: eger...@feds.uwaterloo.ca