On 12/07/2012 12:26 AM, Robinson, Eric wrote: >> Any concurrent log entries in your kernel log, from the drbd0 device? >> > > > In fact, there are... > > Dec 6 13:51:17 ha09a kernel: d-con ha02_mysql: conn( Unconnected -> > WFConnection ) > Dec 6 13:51:19 ha09a root: drbd SA notify > Dec 6 13:51:19 ha09a crm_node[25546]: notice: crm_add_logfile: Additional > logging available in /var/log/corosync.log > Dec 6 13:51:19 ha09a crm_attribute[25547]: notice: crm_add_logfile: > Additional logging available in /var/log/corosync.log > Dec 6 13:51:20 ha09a root: drbd SA notify > Dec 6 13:51:20 ha09a crm_node[25577]: notice: crm_add_logfile: Additional > logging available in /var/log/corosync.log > Dec 6 13:51:20 ha09a crm_attribute[25578]: notice: crm_add_logfile: > Additional logging available in /var/log/corosync.log > Dec 6 13:51:21 ha09a crmd[3066]: notice: process_lrm_event: LRM operation > p_drbd0_notify_0 (call=500, rc=0, cib-update=0, confirmed=true) ok > Dec 6 13:51:21 ha09a crmd[3066]: notice: process_lrm_event: LRM operation > p_drbd1_notify_0 (call=502, rc=0, cib-update=0, confirmed=true) ok > Dec 6 13:51:22 ha09a root: drbd SA notify > Dec 6 13:51:23 ha09a root: drbd SA notify > Dec 6 13:51:24 ha09a crmd[3066]: notice: process_lrm_event: LRM operation > p_drbd0_notify_0 (call=506, rc=0, cib-update=0, confirmed=true) ok > Dec 6 13:51:24 ha09a crmd[3066]: notice: process_lrm_event: LRM operation > p_drbd1_notify_0 (call=508, rc=0, cib-update=0, confirmed=true) ok > Dec 6 13:51:25 ha09a root: drbd SA promote > Dec 6 13:51:25 ha09a kernel: d-con ha01_mysql: helper command: /sbin/drbdadm > fence-peer ha01_mysql > Dec 6 13:51:25 ha09a kernel: d-con ha01_mysql: helper command: /sbin/drbdadm > fence-peer ha01_mysql exit code 127 (0x7f00) > Dec 6 13:51:25 ha09a kernel: d-con ha01_mysql: fence-peer helper broken, > returned 127
Your DRBD refuses to promote because it's unable to get a meaningful response from the fence-peer handler. That in turn is because it's failing with a "command not found" error. (Try typing "foobarblatch; echo $?" in a shell.) Check your "fence-peer" setting in the handlers section of your DRBD config, and see whether it points to a non-existing script. If that script does exist, examine whether it _invokes_ something that doesn't. Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
