-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Yes, my clients run with listen option. Already saw this bug repote and that's why I've restarted puppet agent without this option yesterday to see what happen.
Will see results when arriving at work :) JB On 12/04/2012 01:38, Jason Antman wrote: > Sorry I missed this thread until now. > > Are you running with --listen? If so, try: echo "" | nc localhost > 8139 and see if that helps. > > https://projects.puppetlabs.com/issues/12185 is tracking an issue > where puppetd, running with --listen, gets stuck in a socket read > loop. Any data whatsoever sent to port 8139 will cause puppetd to > continue where it left off (sometimes days ago). > > I've mainly seen this on Cent6.2 personally. I've setup one of my > test clients with a version of ruby patched for > caller_for_all_threads and with the "xray" rubygem, and will try to > get a thread dump next time it happens. > > -Jason > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+GcdwACgkQM2eZoKJfKd1y7ACfSbOHZGcH5z1se3DN43C5xPB4 U1sAn113IJ4fpY5ctUJhV04IObET+aY1 =Wh4Z -----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.
