On 24/05/2013, at 4:35 PM, Andrey Groshev wrote:
>
>
> 24.05.2013, 01:39, "Andrew Beekhof" :
>> On 24/05/2013, at 3:49 AM, Andrey Groshev wrote:
>>
>>> 23.05.2013, 02:51, "Andrew Beekhof" :
On 22/05/2013, at 10:25 PM, Groshev Andrey wrote:
> Hello,
>
> I try build cl
24.05.2013, 01:39, "Andrew Beekhof" :
> On 24/05/2013, at 3:49 AM, Andrey Groshev wrote:
>
>> 23.05.2013, 02:51, "Andrew Beekhof" :
>>> On 22/05/2013, at 10:25 PM, Groshev Andrey wrote:
Hello,
I try build cluster with 2 nodes + one quorum node (without pacemaker).
>>> This
On 24/05/2013, at 3:49 AM, Andrey Groshev wrote:
>
>
> 23.05.2013, 02:51, "Andrew Beekhof" :
>> On 22/05/2013, at 10:25 PM, Groshev Andrey wrote:
>>
>>> Hello,
>>>
>>> I try build cluster with 2 nodes + one quorum node (without pacemaker).
>>
>> This is the root of your problem.
>>
>> Y
23.05.2013, 02:51, "Andrew Beekhof" :
> On 22/05/2013, at 10:25 PM, Groshev Andrey wrote:
>
>> Hello,
>>
>> I try build cluster with 2 nodes + one quorum node (without pacemaker).
>
> This is the root of your problem.
>
> Your config has:
>
>> service {
>> name: pacemaker
>>
On 22/05/2013, at 10:25 PM, Groshev Andrey wrote:
> Hello,
>
> I try build cluster with 2 nodes + one quorum node (without pacemaker).
This is the root of your problem.
Your config has:
> service {
> name: pacemaker
> ver: 1
> }
So even though you thought you only started co
Hello,
I try build cluster with 2 nodes + one quorum node (without pacemaker).
The sequence of actions like the following:
1. setup/start corosync on TREE nodes - all right.
# corosync-quorumtool -l|sed 's/\..*$//'
Nodeid Votes Name
295521290 1 dev-cluster2-node2
312298506 1 dev-clust
