-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/01/2011 02:50 AM, Jo Rhett wrote: > Mon Oct 31 23:03:31 +0000 2011 Puppet (notice): Caught TERM; > calling stop > > Ever since the 2.6.12 upgrade I've been seeing these reports reach > us. As in, about a hundred of a half thou machines. Most of the > time we find that $vardir/state/puppetdlock is in place and > blocking further puppet runs, which requires a manual resolution. > > [...] > > No-- I have no other information than that it crosses all of our > machine types, and we have had no significant changes in our > modules in this time period. Many of the machines which have > failed have had zero module or manifest changes which would apply > to them. I cannot get this to replicate on the command line. >
Can you open a bugreport? Having already that information available is great. Thanks! ~pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6vqVsACgkQbwltcAfKi383WQCgl9Nx/s2XQ6si9n+XUgdVdEfE 3agAn3T2n+4HTJzpT+gqWw6a0m5H2GB5 =+5qz -----END PGP SIGNATURE----- -- 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.
