Hi, On Apr 11, 2012, at 7:38 PM, 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.
Yup - that did it. Time to modify my check-puppet script to do the echo. :-) ...thnx, ...dave -- 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.
