Comment 3 for bug 1359088

in mcollective agent
2014-08-19T13:32:24.147397+00:00 debug: E, [2014-08-19T13:32:20.175654 #1444] ERROR -- : rabbitmq.rb:50:in `on_hbread_fail' Heartbeat read failed from 'stomp://mcollective@10.108.26.2:61613': {"read_fail_count"=>0, "lock_fail_count"=>1, "ticker_interval"=>29.5, "lock_fail"=>true}

this one related to initial deployment, not patching, and hb failure is casual stuff and handled properly by rabbitmq/mcollective

Maybe patching failed because overall execution was increased by 3 min of reconnections attemps?

2014-08-20T06:10:05 debug: [431] Retry #1 to run mcollective agent on nodes: '1'
2014-08-20T06:10:48 debug: [431] Retry #2 to run mcollective agent on nodes: '1'
2014-08-20T06:11:30 debug: [431] Retry #3 to run mcollective agent on nodes: '1'
2014-08-20T06:12:13 debug: [431] Retry #4 to run mcollective agent on nodes: '1'
2014-08-20T06:12:55 debug: [431] Retry #5 to run mcollective agent on nodes: '1'
2014-08-20T06:13:37 debug: [431] Data received by DeploymentProxyReporter to report it up: {"nodes"=>[{"uid"=>"1", "status"=>"error", "error_type"=>"deploy", "role"=>"controller"}]}
2014-08-20T06:13:37 debug: [431] Data send by DeploymentProxyReporter to report it up: {"nodes"=>[{"uid"=>"1", "status"=>"error", "error_type"=>"deploy", "role"=>"controller"}]}