Puppet users - May 2008 - controlling puppetd configuration - is this safe?

Pushing a standardized puppet.conf down to the clients and sending a 
Notify to puppetd service to restart?

-- 
Mark Foster - Sr. Systems Engineer - BitPusher, LLC 

We push your bits so you don''t have to! http://www.bitpusher.com/


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

I do this, but no need to send a Notify, because puppet will notice
the changed config and reload.

On Fri, May 23, 2008 at 8:56 AM, Mark Foster <mfoster@bitpusher.com>
wrote:
>
> Pushing a standardized puppet.conf down to the clients and sending a
> Notify to puppetd service to restart?
>
> --
> Mark Foster - Sr. Systems Engineer - BitPusher, LLC
>
> We push your bits so you don''t have to! http://www.bitpusher.com/
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Paul Lathrop wrote:
> I do this, but no need to send a Notify, because puppet will notice
> the changed config and reload.
>   
In that case I may have discovered a bug...
When puppetd is start with nonexistent config file 
(/etc/puppet/puppet.conf) and afterwards, puppet.conf is created, it 
seems puppetd does not recognize and load this new file on subsequent runs.
Or is that a feature?


-- 
Mark Foster - Sr. Systems Engineer - BitPusher, LLC 

We push your bits so you don''t have to! http://www.bitpusher.com/


--~--~---------~--~----~------------~-------~--~----~
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 May 23, 2008, at 8:56 AM, Mark Foster wrote:
> Pushing a standardized puppet.conf down to the clients and sending a
> Notify to puppetd service to restart?
puppetd seems to notice a modified puppet.conf and reload on its own.

Having puppet restart the puppet service is problematic, since halfway  
through the restart puppetd dies.  Basically the "stop" part works,  
but the "start" part doesn''t happen.

Might be best to include something like the mutual restart recipe:
http://reductivelabs.com/trac/puppet/wiki/Recipes/MutualRestart
  -- that way if your recipes notify the puppetd service to restart  
and it doesn''t come back right, cron will come along later and get  
puppetd running again for you.  Also handy in case puppetd crashes.
-- 
Eric Eisenhart <eric.eisenhart@sonoma.edu>
Lead Unix/Linux System Administrator
1.707.664.3099
Sonoma State University, Information Technology
Jabber/XMPP: eisenhae@jabber.sonoma.edu
AIM: ericeisenhart


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Mark Foster schrieb:
> Paul Lathrop wrote:
>> I do this, but no need to send a Notify, because puppet will notice
>> the changed config and reload.
>>   
> In that case I may have discovered a bug...
> When puppetd is start with nonexistent config file 
> (/etc/puppet/puppet.conf) and afterwards, puppet.conf is created, it 
> seems puppetd does not recognize and load this new file on subsequent runs.
> Or is that a feature?

I wouldn''t think that. Can you reproduce this with a minimal setup and
a
obvious setting like noop and create a ticket in trac[1]

Please also check whether you''re not running into some known
problem[2].


Regards, David

[1] http://reductivelabs.com/trac/puppet/simpleticket

[2] 
http://reductivelabs.com/trac/puppet/query?status=new&status=assigned&status=reopened&order=priority


--~--~---------~--~----~------------~-------~--~----~
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 wrote:
>
> I wouldn''t think that. Can you reproduce this with a minimal setup
and a
> obvious setting like noop and create a ticket in trac[1]
>
>   
http://reductivelabs.com/trac/puppet/ticket/1269#preview
Thanks.

-- 
Mark Foster - Sr. Systems Engineer - BitPusher, LLC 

We push your bits so you don''t have to! http://www.bitpusher.com/


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---