Hi,

I upgraded to Heatbeat v2.1.2. I kept my old configuration and I still don't
have any primary drbd node... (the result are the same as in my first
message)
I looked at LMB's documentation (nice nickname :) ) but I didn't find
anything that could help, I may have not searched well...
I also tried what David tried i.e <nvpair id="ms-drbd0_target_role"
name="target_role" value="started" />, but it screws everything... or
almost. It is stange to see that the configuration good is 1 sec out of 2,
heartbeat tries to launch my secondary node as a slave and I can see that
its drbd status is good... but it never last more than 1 second

"crm_mon" and "cat /proc/drbd" when heartbeat seems working well:
----------------------------
============
Last updated: Wed Aug  1 12:42:48 2007
Current DC: ha2 (96c80a7f-1ca9-44cd-b616-70603f77bb78)
2 Nodes configured.
2 Resources configured.
============

Node: ha2 (96c80a7f-1ca9-44cd-b616-70603f77bb78): online
Node: ha1 (25956cf4-3004-4488-aeed-15adc2531490): online

Resource Group: group_1
    IPaddr_1    (heartbeat::ocf:IPaddr):        Started ha2
Master/Slave Set: ms-drbd0
    resource_drbd:0     (heartbeat::ocf:drbd):  Slave ha1 FAILED
    resource_drbd:1     (heartbeat::ocf:drbd):  Master ha2

Failed actions:
    resource_drbd:0_promote_0 (node=ha1, call=54, rc=1): Error

----------------------------
Every 2.0s: cat
/proc/drbd
Wed Aug  1 12:44:16 2007
version: 8.0.4 (api:86/proto:86)
SVN Revision: 2947 build by [EMAIL PROTECTED], 2007-07-26 14:52:58
 0: cs:Connected st:Secondary/Primary ds:UpToDate/UpToDate C r---
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
        resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
        act_log: used:0/257 hits:0 misses:0 starving:0 dirty:0 changed:0
-------------------------

let's hope somebody has an idea about where the problem comes from...
thanks,
Sébastien.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to