Issue #4462 has been updated by James Turnbull. Status changed from Ready for Checkin to Code Insufficient
This needs a rethink based on Peter's comments. ---------------------------------------- Bug #4462: uncaught timeout excpetion http://projects.puppetlabs.com/issues/4462 Author: Peter Meier Status: Code Insufficient Priority: Normal Assignee: Category: Target version: 2.6.1 Affected version: 2.6.1rc1 Keywords: Branch: http://github.com/jes5199/puppet/tree/ticket/2.6.x/4462 I encounter from time to time an uncaught timeout exception: <pre> /usr/lib/ruby/1.8/timeout.rb:60:in `open': execution expired (Timeout::Error) from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' from /usr/lib/ruby/1.8/net/http.rb:542:in `start' from /usr/lib/ruby/1.8/net/http.rb:1035:in `request' from /usr/lib/ruby/1.8/net/http.rb:772:in `get' from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:71:in `find' from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:193:in `find' ... 42 levels... from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:300:in `run' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:397:in `exit_on_fail' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:300:in `run' from /usr/sbin/puppetd:4 </pre> I think this one should be caught and translated into a puppet error?! -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
