Samba CTDB resource unable to start and timeout errors logged when booting multiple nodes at the same time in a RHEL 7 High Availability cluster

Issue

• When rebooting 2 cluster nodes at same time, it fails to stat Samba service on server boot up.
• CTDB seems to timeout on start when the entire cluster is starting at once

Jan 14 20:12:35 node2  crmd[5420]: notice: te_rsc_command: Initiating action 57: start Samba_CTDB_start_0 on node1.example.com
Jan 14 20:12:56 node2  CTDB(Samba_CTDB)[9550]: ERROR: CTDB status call failed: 2015/01/14 20:12:56.845750 [ 9554]: client/ctdb_client.c:267 Failed to connect client socket to daemon. Errno:No such file or directory(2)
common/cmdline.c:156 Failed to connect to daemon
2015/01/14 20:12:56.845826 [ 9554]: Failed to init ctdb
Jan 14 20:12:57 node2  CTDB(Samba_CTDB)[9550]: INFO: Generating new /etc/sysconfig/ctdb
Jan 14 20:14:26 node2  lrmd[5417]: warning: child_timeout_callback: Samba_CTDB_start_0 process (PID 9550) timed out
Jan 14 20:14:26 node2  lrmd[5417]: warning: operation_finished: Samba_CTDB_start_0:9550 - timed out after 90000ms
Jan 14 20:14:26 node2  crmd[5420]: error: process_lrm_event: LRM operation Samba_CTDB_start_0 (72) Timed Out (timeout=90000ms)
Jan 14 20:14:26 node2  crmd[5420]: warning: status_from_rc: Action 59 (Samba_CTDB_start_0) on node2 .mboi.in failed (target: 0 vs. rc: 1): Error
Jan 14 20:14:26 node2  crmd[5420]: warning: update_failcount: Updating failcount for Samba_CTDB on node2 .mboi.in after failed start: rc=1 (update=INFINITY, time=1421246666)
Jan 14 20:14:26 node2  crmd[5420]: warning: update_failcount: Updating failcount for Samba_CTDB on node2 .mboi.in after failed start: rc=1 (update=INFINITY, time=1421246666)
Jan 14 20:14:26 node2  attrd[5418]: notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-Samba_CTDB (INFINITY)