The root cause is that monitor command on the nodes that are not yet running rabbitmq return incorrect exit code 1 instead of 7 which leads to a cascade of post-stop notifications. Sometimes these post-stop notifications interfere with regular start sequence leading to this bug
2016-07-06T11:17:42.193913+00:00 warning: warning: Action 23 (p_rabbitmq-server_monitor_0) on node-4.test.domain.local failed (target: 7 vs. rc: 1): Error
2016-07-06T11:17:42.194349+00:00 warning: warning: Action 23 (p_rabbitmq-server_monitor_0) on node-4.test.domain.local failed (target: 7 vs. rc: 1): Error
2016-07-06T11:17:42.197117+00:00 warning: warning: Action 22 (p_rabbitmq-server_monitor_0) on node-3.test.domain.local failed (target: 7 vs. rc: 1): Error
2016-07-06T11:17:42.197469+00:00 warning: warning: Action 22 (p_rabbitmq-server_monitor_0) on node-3.test.domain.local failed (target: 7 vs. rc: 1): Error
The root cause is that monitor command on the nodes that are not yet running rabbitmq return incorrect exit code 1 instead of 7 which leads to a cascade of post-stop notifications. Sometimes these post-stop notifications interfere with regular start sequence leading to this bug
2016-07- 06T11:17: 42.193913+ 00:00 warning: warning: Action 23 (p_rabbitmq- server_ monitor_ 0) on node-4. test.domain. local failed (target: 7 vs. rc: 1): Error 06T11:17: 42.194349+ 00:00 warning: warning: Action 23 (p_rabbitmq- server_ monitor_ 0) on node-4. test.domain. local failed (target: 7 vs. rc: 1): Error 06T11:17: 42.197117+ 00:00 warning: warning: Action 22 (p_rabbitmq- server_ monitor_ 0) on node-3. test.domain. local failed (target: 7 vs. rc: 1): Error 06T11:17: 42.197469+ 00:00 warning: warning: Action 22 (p_rabbitmq- server_ monitor_ 0) on node-3. test.domain. local failed (target: 7 vs. rc: 1): Error
2016-07-
2016-07-
2016-07-