Randomizing the time of logrotation as a workaround for this particular issue seems drastic to me.
https://docs.puppetlabs.com/references/latest/configuration.html#splay This may do the trick. Cheers, Felix On 01/08/2015 08:27 PM, Christopher Wood wrote: > Yes it does, and that's something that you would configure to not happen at > the same time (with fqdn_rand, or better, remote syslog). > > https://docs.puppetlabs.com/references/latest/function.html#fqdnrand > > I found some irritating hitches with running through a cut-down environment > using mcollective (plugin re-sync, usual hiccoughs with mcollective in our > environment), plus popular opinion here did not support adding to our lengthy > list of cron jobs. Long story short, we are still running the puppet agent as > a daemon. Which you would pick still depends on what criteria you are aiming > for. > > On Thu, Jan 08, 2015 at 04:40:05AM -0800, Suresh P wrote: >> > Hi All, >> > >> > I have found one more issue. >> > When we install puppet agent, it creates logrotate which will kill the >> > puppet and restart it. We have configured logroate for all the nodes >> > at >> > 1st minute of everday(00:01). Because of that all the node's puppet >> > agent get reloaded at 00:01 minutes so all agents trying to connect the >> > puppet masters at same polling interval. >> > >> > Regards, >> > Suresh. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54AFD9FF.2010606%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
