I think some of your questions are address here http://docs.chef.io/handlers.html, but the short version is that you *register* the handler very early on, and then it *executes* at the end of the Chef run.There is always a chance for failure before the handler is registered, so you generally want to do those very early on in your run_list.I'm not sure you will see any output from an exception handler if there are no errors, but a good way to test this would be to enable this handler: https://github.com/jtimberman/chef-handler-updated-resources. That will produce visible output of which resources were changed during your Chef run (while at the same time proving you registered a handler)On Wed, Sep 23, 2015 at 12:37 PM, Doug Garstang < " target="_blank"> > wrote:I've tried a number of times to get chef handlers to work. Failed each time. Thought I'd give it another shot.Started with this: http://onddo.github.io/chef-handler-sns/You can load the handler in the client.rb file so that it catches errors during the convergence phase. However, after installing the stated dependancies manually, and adding the necessary bits to the client.rb file, nothing seems to happen after a chef-client run. I can't see anything indicating anything happens in the client.log file.The document says:"We recommend using the chef_handler_sns cookbook for easy installation."Well, if I use a cookbook to install it, how's it going to catch any errors during the convergence phase on the initial chef-client run? Will using the cookbook allow it to catch errors during the convergence phase os subsequent chef-client runs?Doug.
Archive powered by MHonArc 2.6.16.