It seems like I have two sets of similar symptoms. I have another set of servers where puppetd -tv runs fine, but the daemon will never finish a catalog run. Again, puppetdlock lingers.
I think the first problem may track to a database backup. The clients with similar timestamps are near that time. I've changed that process and will see if that fixes the problem. On Thu, Nov 10, 2011 at 8:32 AM, Len Rugen <lenru...@gmail.com> wrote: > 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.
