Nope, they think they are running. We had to reset the policy to downgrade facter, then login to each host and "service puppet stop ; puppet agent --test --ignoreschedules" (our systems are set to only upgrade packages in certain hours) to get the hosts back online.
This looks similar to the old problem with a kernel that changed proc semantics, but it's not the kernel this time. Reverting facter to 1.6.10 resolves the issue. On Aug 17, 2012, at 5:55 PM, Stuart Cracraft wrote: > Can you kick them somehow? > > On Aug 17, 2012, at 5:50 PM, Jo Rhett <jrh...@netconsonance.com> wrote: > >> At least on CentOS 5 and CentOS 6, after upgrading to facter 1.6.11 our >> hosts stopped checking in. Stale puppetdlock problem. >> >> -- >> Jo Rhett >> Net Consonance : net philanthropy to improve open source and internet >> projects. >> >> >> >> >> -- >> 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. > > > -- > 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. -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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.
