[DRBD-user] Failover Behavior in Server-Crash Scenario

Robinson, Eric eric.robinson at psmnv.com
Fri Dec 7 00:26:28 CET 2012

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


> On 12/07/2012 12:04 AM, Robinson, Eric wrote:
> >> Have you checked your Pacemaker and DRBD logs to determine whether 
> >> (a) Pacemaker is not even _attempting_ a promotion, or (b) 
> Pacemaker 
> >> does attempt it but it fails at the DRBD level?
> >>
> > 
> > Pacemaker successfully demotes the resources on the primary 
> and then stops drbd. On the secondary, Pacemaker attempts to 
> promote the resource, but fails. The log on the secondary shows...
> > 
> > drbd(p_drbd0)[32708]:   2012/12/05_09:41:50 ERROR: 
> ha01_mysql: Called drbdadm -c /etc/drbd.conf primary ha01_mysql
> > drbd(p_drbd0)[32708]:   2012/12/05_09:41:50 ERROR: 
> ha01_mysql: Exit code 11
> 
> 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
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
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
Dec  6 13:51:25 ha09a kernel: d-con ha01_mysql: helper command: /sbin/drbdadm fence-peer ha01_mysql


Disclaimer - December 6, 2012 
This email and any files transmitted with it are confidential and intended solely for Florian Haas,drbd-user at lists.linbit.com. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/



More information about the drbd-user mailing list