Issue #5246 has been updated by Andrew Forgue.
I have seen this before as well. 0,30 * * * * /usr/local/bin/puppet agent --splay --onetime >/dev/null 2>&1 However it seems to be an issue if the catalog finished before the next cron run, but the report is bing submitted. Here's a rudimentary timeline.. :00 - puppet agent --onetime --splay :29:00 - catalog retrival :29:56 - catalog finishes :30 - puppet agent --onetime --splay (Run of Puppet configuration client already in progress; skipping) :30:xx - report submitted, original process ends >From here, puppet will never run again and I have to manually delete the pid >file. I'm not sure if this is the same issue as RI, but it's the first one that showed up when searching and sounded familiar. ---------------------------------------- Bug #5246: Puppetd does not remove it's pidfile when it exits https://projects.puppetlabs.com/issues/5246 Author: R.I. Pienaar Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.2 Keywords: Branch: When running puppetd it should delete its pid file when it exits <pre> root 20572 2.0 0.5 116736 35256 ? Ss 23:10 0:00 /usr/bin/ruby /usr/sbin/puppetd --onetime --splaylimit 30 --splay </pre> The pid file /var/run/puppet/agent.pid would have 20572 as expected, the puppet run completes ok: <pre> Nov 9 23:11:27 xen1 puppet-agent[20572]: Finished catalog run in 19.68 seconds </pre> But it leaves the pid file on the disk after exiting -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
