Also, the timestamp on several clients puppetdlock file will be within minutes of each other, so it appears to be some sort of infrastructure issue. The puppet master is a VM and the backend mysql server physical.
On Thu, Nov 10, 2011 at 8:24 AM, Len Rugen <lenru...@gmail.com> wrote: > We've recently developed a problem where a puppetd scheduled catalog run > will hang or fail, then never resume. The puppetdlock file is present, but > I can't find any logged errors. If I stop the daemon, it will restart and > run the catalog without problem. > > Any suggestions on how to identify the problem? > > Puppet version 2.7.6 on both client and server and Foreman is managing > nodes. > > Thanks > -- 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.
