I push out changes to puppet.conf using puppet. (I have gsh as a backup for if I really screw things up, but I''ve never had to use it yet.) Is there any safe and/or good way to restart puppet after a change is made o it''s config? I''m assuming that just defining puppet as a service and subscribing to puppet.conf is bad because it will stop puppet in the middle of a run which might make other subscribes not work. Anyone have advice? I don''t want to put puppet in cron if I can avoid it. -Patrick Mohr -- 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.
Well depending on complexity of your manifests, you could define a
service for puppet and require certain classes to be executed before
the puppet service is checked in order to avoid that problem.
At least for me it works, but I have to admit that this solution isn''t
very pretty.
Example:
service { puppet:
require => [ class["class1"], class["class2"]
]
}
christian
On 22 Jun., 03:03, Patrick Mohr <kc7...@gmail.com>
wrote:> I push out changes to puppet.conf using puppet. (I have gsh as a backup
for if I really screw things up, but I''ve never had to use it yet.) Is
there any safe and/or good way to restart puppet after a change is made o
it''s config? I''m assuming that just defining puppet as a
service and subscribing to puppet.conf is bad because it will stop puppet in the
middle of a run which might make other subscribes not work.
>
> Anyone have advice? I don''t want to put puppet in cron if I can
avoid it.
> -Patrick Mohr
--
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.
David Schmitt
2010-Jun-22 09:43 UTC
Re: [Puppet Users] Refreshing puppetd from within puppetd
On 6/22/2010 3:03 AM, Patrick Mohr wrote:> I push out changes to puppet.conf using puppet. (I have gsh as a > backup for if I really screw things up, but I''ve never had to use it > yet.) Is there any safe and/or good way to restart puppet after a > change is made o it''s config? I''m assuming that just defining puppet > as a service and subscribing to puppet.conf is bad because it will > stop puppet in the middle of a run which might make other subscribes > not work.Puppetd does reload its configuration automatically when the config file changes. Any settings that do not get reloaded should be considered bugs and reported to the bug tracker. Best Regards, David -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg -- 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.
Trevor Vaughan
2010-Jun-22 11:15 UTC
Re: [Puppet Users] Refreshing puppetd from within puppetd
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes, I''ve never had a problem with this. If you wanted to be sure to run it right away after the current run, I would use an exec to fire off an ''at'' job for <insert length of your puppet runs + 1 minute here> minutes in the future. Make sure to set refreshonly => true on that exec. Trevor On 06/22/2010 05:43 AM, David Schmitt wrote:> On 6/22/2010 3:03 AM, Patrick Mohr wrote: >> I push out changes to puppet.conf using puppet. (I have gsh as a >> backup for if I really screw things up, but I''ve never had to use it >> yet.) Is there any safe and/or good way to restart puppet after a >> change is made o it''s config? I''m assuming that just defining puppet >> as a service and subscribing to puppet.conf is bad because it will >> stop puppet in the middle of a run which might make other subscribes >> not work. > > Puppetd does reload its configuration automatically when the config file > changes. Any settings that do not get reloaded should be considered bugs > and reported to the bug tracker. > > > Best Regards, David- -- Trevor Vaughan Vice President, Onyx Point, Inc. email: tvaughan@onyxpoint.com phone: 410-541-ONYX (6699) pgp: 0x6C701E94 - -- This account not approved for unencrypted sensitive information -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMIJs5AAoJECNCGV1OLcyp3C8IAJrHgFxjnObmLs8BmZvYmnXZ nHFlZtCxRxXLv3/VS2wXNjLvyIyE0Wu9uNsmnGPP0QXeIjaEXrR41tSfTNGIUqrg rin2usvzNAtMPYJT6f+30JW5pLSleNOca4ht5nQKnK8ROUT4P0t+iKnAkoVUYACo KjaLkVm/tu399T00j99LBoY2/amUyn3KEPBDXs5ZKiiNuwzNjMCtWor1jfyj8JFB jNLeHI3hSYZalgPd4m7bEJugYS6NgZ4uwg/XsbOotPX/2F6wipGV8iX20TWoFfdb Ue1r82IydJjka3dFmlBlLsnzLdBtC2vcEpFmI7KRND3tPo9M/ozubV8xzZUzEIQ=IBqx -----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-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.
Patrick Mohr
2010-Jun-22 14:18 UTC
Re: [Puppet Users] Refreshing puppetd from within puppetd
On Jun 22, 2010, at 2:43 AM, David Schmitt wrote:> On 6/22/2010 3:03 AM, Patrick Mohr wrote: >> I push out changes to puppet.conf using puppet. (I have gsh as a >> backup for if I really screw things up, but I''ve never had to use it >> yet.) Is there any safe and/or good way to restart puppet after a >> change is made o it''s config? I''m assuming that just defining puppet >> as a service and subscribing to puppet.conf is bad because it will >> stop puppet in the middle of a run which might make other subscribes >> not work. > > Puppetd does reload its configuration automatically when the config file changes. Any settings that do not get reloaded should be considered bugs and reported to the bug tracker. >It seemed to me that adding report=true to [puppetd] using augeas didn''t cause puppetd to start sending reports each run. I''ll check to see that''s actually true later today. -Patrick Mohr -- 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.
Derek J. Balling
2010-Jun-23 00:21 UTC
Re: [Puppet Users] Refreshing puppetd from within puppetd
On Jun 21, 2010, at 9:03 PM, Patrick Mohr wrote:> Anyone have advice? I don''t want to put puppet in cron if I can avoid it.We did this: service { puppet : enable => true, require => [ File[''etc-sysconfig-puppet''],File[''puppet.conf''] ], subscribe => [ File[''etc-sysconfig-puppet''],File[''puppet.conf''] ], hasrestart => true } the "hasrestart" tells it not to do a "stop, start" but instead to do a "restart", so it happily seems to work any time we change a config file. D -- 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.