On Wed, Dec 8, 2010 at 8:54 AM, Linux Cook <[email protected]> wrote:
> hi andrew,
>
> dpkg -l |grep corosync

Ah debian, better contact them directly.
They dont let us be involved in packaging and it looks to me like
they've messed something up (since stonithd can't start)

> ii  corosync                            1.2.1-1~bpo50+1
> Standards-based cluster framework (daemon and modules)
> ii  libcorosync4                        1.2.1-1~bpo50+1
> Standards-based cluster framework (libraries)
> dmcs1:~# dpkg -l |grep pacemaker
> ii  pacemaker                           1.0.9.1+hg15626-1~bpo50+1  HA
> cluster resource manager
>
>
> Oliver
>
> On Wed, Dec 8, 2010 at 3:41 PM, Andrew Beekhof <[email protected]> wrote:
>>
>> On Wed, Dec 8, 2010 at 8:03 AM, Linux Cook <[email protected]> wrote:
>> > Hi!
>> >
>> > Is this mean I need to enable stonith?
>>
>> No, it means your install is broken.
>> Which version of pacemaker?  Heartbeat or corosync?
>>
>> >
>> > On Wed, Dec 8, 2010 at 12:13 PM, Linux Cook <[email protected]> wrote:
>> >
>> >> I've followed the steps but I'm having issues right after it with the
>> >> following logs.
>> >>
>> >> ERROR: te_connect_stonith: Sign-in failed: triggered a retry
>> >> Dec  8 12:14:17 dmcs2 crmd: [2681]: info: te_connect_stonith:
>> >> Attempting
>> >> connection to fencing daemon...
>> >> Dec  8 12:14:18 dmcs2 crmd: [2681]: ERROR: stonithd_signon: Can't
>> >> initiate
>> >> connection to stonithd
>> >> Dec  8 12:14:18 dmcs2 crmd: [2681]: notice: Not currently connected.
>> >> Dec  8 12:14:18 dmcs2 crmd: [2681]: ERROR: te_connect_stonith: Sign-in
>> >> failed: triggered a retry
>> >> Dec  8 12:14:18 dmcs2 crmd: [2681]: info: te_connect_stonith:
>> >> Attempting
>> >> connection to fencing daemon...
>> >> Dec  8 12:14:19 dmcs2 crmd: [2681]: ERROR: stonithd_signon: Can't
>> >> initiate
>> >> connection to stonithd
>> >> Dec  8 12:14:19 dmcs2 crmd: [2681]: notice: Not currently connected.
>> >> Dec  8 12:14:19 dmcs2 crmd: [2681]: ERROR: te_connect_stonith: Sign-in
>> >> failed: triggered a retry
>> >>
>> >> and the server is doing stand-alone without promoting itself to both
>> >> primaries.
>> >>
>> >>
>> >>
>> >> On Wed, Dec 8, 2010 at 5:08 AM, Pavlos Parissis
>> >> <[email protected]
>> >> > wrote:
>> >>
>> >>> On 7 December 2010 21:25, Linux Cook <[email protected]> wrote:
>> >>> > hi!
>> >>> >
>> >>> > Where can I read a good documentation on how to configure pacemaker
>> >>> > in
>> >>> order
>> >>> > to promote dual primary drbd resource?
>> >>> >
>> >>>
>> >>>
>> >>> I think setting meta master-max="2" on ms clone for DRBD should be
>> >>> enough, take a look here
>> >>>
>> >>>
>> >>> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s06.html
>> >>>
>> >>
>> >>
>> > _______________________________________________
>> > Linux-HA mailing list
>> > [email protected]
>> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> > See also: http://linux-ha.org/ReportingProblems
>> >
>
>
_______________________________________________
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