Hi Josh - thanks for the info. Can I make an assertion that having the default read timeout be unlimited is a mistake? In practical terms, anything over 60 seconds means something is broken.
Could I suggest (without having to go and update the bug because I'm a bad bad lazy person) that along with the watchdog you change the default timeout to, say, 5 minutes? That's effectively infinite, but would likely keep things from getting stuck. (I wrote some tools back in the early puppet 3 days to run puppet the way I wanted, and of course I included a timeout on the total run time. There were some interesting failure modes back in the olden days.) Thanks - cheers! John On Fri, 2018/01/05 11:53:12AM -0800, Josh Cooper <j...@puppet.com> wrote: | In Puppet 4 we added settings for configuring http connect and read | timeouts independently[1]. Previously they were both controlled by the | configfiletimeout. The default read timeout is unlimited, so the hung agent | may be stuck in a socket read. You might want to strace the stuck agent to | see what it's up to. | | In our upcoming 4.10.x/5.3.x releases, we've added a watchdog to kill a | stuck run[2]. | | Josh | | [1] https://tickets.puppetlabs.com/browse/PUP-3666 | [2] https://tickets.puppetlabs.com/browse/PUP-7517 | | -- | Josh Cooper | Software Engineer | j...@puppet.com | @coopjn | -- 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/20180105203151.GA30517%40syonex.com. For more options, visit https://groups.google.com/d/optout.
