On Feb 3, 2009, at 1:01 PM, Ian Burrell wrote:
>
> We are having a problem with some of the puppet clients dying during
> the weekly log rotation reload. We are using Centos 4 with puppet
> 0.24.6. It seems to be a race condition with clients that reload when
> the puppetmaster is restarting exit. The redhat logrotate script does
> "/etc/init.d/puppetmaster condrestart" and "/etc/init.d/puppet
> reload". Reloading puppet when the puppetmaster is stopped doesn't
> seem to be a problem. My guess is that there is a period when the
> puppetmaster is starting when the puppetd fails when it contacts the
> server. Unfortunately, I don't see anything in the logs on the
> clients.
>
> Has anyone seen this problem?
Can you get a stack trace from the clients?
The last few releases have seen us greatly reduce the number of cases
where puppetd can exit on failure, and we might have already resolved
the one you're seeing. I know that either 0.24.6 or 0.24.7 had a
problem where if the first connection to the master failed, the client
would exit. I hope that was fixed in 0.24.7, because that could mean
your problem's already fixed. :)
--
At my lemonade stand I used to give the first glass away free and charge
five dollars for the second glass. The refill contained the antidote.
-- Emo Phillips
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
