Hi, For some time now, we've seen this kind of logs in our machines : (note: we do manage the puppet agent config with puppet)
Mar 29 13:25:50 gate01 puppet-agent[2684]: Processing restart Mar 29 13:25:50 gate01 puppet-agent[2684]: Puppet::Agent::Locker.running? is deprecated as it is inherently unsafe. The only safe way to know if the lock is locked is to try lock and perform some action and then handle the LockError that may result. Mar 29 13:25:50 gate01 puppet-agent[2684]: (location: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent/locker.rb:37:in `running?') Mar 29 13:25:51 gate01 puppet-agent[38303]: Applied catalog in 16.78 seconds Mar 29 13:26:00 gate01 puppet-agent[2684]: Config file /etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all config files. Mar 29 13:44:16 gate01 puppet-agent[2684]: Shutdown/restart in progress (:restart_requested); skipping run Than puppet never runs again because of this stuck restart until we manually restart the agent. puppet-agent-5.5.12 here. This happens on both el6 and el7 hosts. Bad thing is that this even happens when puppet is upgraded during our install process ... and we get freshly installed nodes with stuck puppets... Off course, this did not happen before. Would anyone know of a way to get rid of this damn "can't restart" loop ? Regards Frédéric Schaer CEA/Saclay DRF/IRFU/DEDIP/LIS -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAB586860327CB498EF79903967FEA231ABC903E%40E-EXDAGE-A0.extra.cea.fr. For more options, visit https://groups.google.com/d/optout.
