Hi John, Thank you for your response. We use very short interval, so I think first scenario is applicable for us. We will try to reduce execution time.
Pavel On Tuesday, June 5, 2012 4:51:06 PM UTC+3, jcbollinger wrote: > > > > On Jun 5, 2:13 am, Pavel Drobushevich <p.drobushev...@gmail.com> > wrote: > > Hi all, > > > > Sometimes one of agent prints message "Skipping run of Puppet > configuration > > client; administratively disabled; use 'puppet Puppet configuration > client > > --enable' to re-enable." and stops working. No one disables it. Any > reason > > why it happens? > > > Puppet uses a lock file to prevent agent runs from overlapping, and it > multipurposes that same lock file to provide for administratively > disabling Puppet runs without actually shutting down the daemon. > Therefore, Puppet cannot distinguish between the agent being manually > disabled and the agent being disabled on account of another run being > in progress (or the agent being disabled because previously the > machine was abruptly halted while a run was in progress). > > There are several possible scenarios, but the most likely are these: > > 1) You are performing periodic one-off agent runs, via cron for > example, and occasionally a run takes longer to complete than the > interval between runs. > > 2) You have more than one Puppet agent daemon running on the affected > machine, or you are both running the agent as a daemon and separately > launching one-off agent runs by some other means (manually, cron, > etc.). > > > John > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5OqUi7jGRY8J. 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.
