Issue #4949 has been updated by Markus Roberts. Category set to error reporting Status changed from Unreviewed to Accepted
This is part of a broader need for better error handling. The problem is of course how to determine "what was happening" in a way that will make sense to the user. There are two main ways we could do this: passively, by having the error handler examine the stack trace and abstract the "significant" activity for reporting (the separation of concerns paradigm) which might result in something like: <pre> err: Could not run Puppet configuration client: execution expired in send_report/save/put/read_status_line </pre> or actively, by decorating "significant" routines with descriptions which are stashed somewhere to generate error messages if needed. ---------------------------------------- Bug #4949: non informative error message when reporting times out http://projects.puppetlabs.com/issues/4949 Author: Peter Meier Status: Accepted Priority: Normal Assignee: Category: error reporting Target version: Affected version: 2.6.1 Keywords: Branch: I have a host which take some time to send its report to the dashboard as well as import it there. The client then "fails" with the following error message: <pre> notice: Finished catalog run in 272.62 seconds err: Could not run Puppet configuration client: execution expired </pre> However, this error message is not really helpful and could be improved to say at which point it exactly timed out (while reporting!) Trace: <pre> notice: Finished catalog run in 204.90 seconds /usr/lib/ruby/1.8/timeout.rb:60:in `rbuf_fill' /usr/lib/ruby/1.8/net/protocol.rb:132:in `rbuf_fill' /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline' /usr/lib/ruby/1.8/net/http.rb:2020:in `read_status_line' /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new' /usr/lib/ruby/1.8/net/http.rb:1050:in `request' /usr/lib/ruby/1.8/net/http.rb:1037:in `request' /usr/lib/ruby/1.8/net/http.rb:543:in `start' /usr/lib/ruby/1.8/net/http.rb:1035:in `request' /usr/lib/ruby/1.8/net/http.rb:857:in `put' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:90:in `save' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:253:in `save' /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:64:in `save' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:178:in `send_report' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:172:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:114:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:88:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:300:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:397:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:300:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:55:in `execute' /usr/bin/puppet:4 err: Could not run Puppet configuration client: execution expired </pre> -- 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.
