Becase of this restart. My 1200 puppet agent runtime changed and so all
1200 puppet agents try to connect puppetmasters at same time because of
this most of the agent in out-of-sync or error stat.
Regards,
Suresh.
On Tuesday, 16 December 2014 20:10:21 UTC+5:30, Dirk Heinrichs wrote:
>
> Am 16.12.2014 um 15:26 schrieb Suresh P:
>
> This is configured to run daily by puppet installation itself. Does
> this restart puppet agent?
>
> /var/log/puppet/*log {
> missingok
> notifempty
> create 0644 puppet puppet
> sharedscripts
> postrotate
> pkill -USR2 -u puppet -f 'puppet master' || true
> [ -e /etc/init.d/puppet ] && /etc/init.d/puppet reload > /dev/null 2>&1
> || true
> endscript
> }
>
>
> Yes, it does, although it shouldn't. "/etc/init.d/puppet reload" sends a
> SIGHUP signal to the puppet agent, which restarts it. However, according to
> puppet-agent(8), this action should better be sending a SIGUSR2 ("Close
> file descriptors for log files and reopen them. Used with logrotate."),
> which wouldn't trigger an agent restart.
>
> Should this be considered a bug in /etc/init.d/puppet?
>
> Bye...
>
> Dirk
> --
>
> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 1596666 (Ansage) 1149
> *Email*: d...@recommind.com <javascript:>
> *Skype*: dirk.heinrichs.recommind
> www.recommind.com
>
--
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/06c18629-f482-4722-83c2-226ffabf11dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
