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

Florian Haas florian at hastexo.com
Fri Dec 7 00:13:15 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?


Need help with High Availability?

More information about the drbd-user mailing list