[PVE-User] Adding a cluster node breaks whole cluster

[Sten Aus]

Hi

Did a /etc/init.d/cman restart in this node, which have been in a cluster.
> # /etc/init.d/cman restart
> Stopping cluster:
>    Stopping dlm_controld... [  OK  ]
>    Stopping fenced... [  OK  ]
>    Stopping cman... [  OK  ]
>    Waiting for corosync to shutdown:[  OK  ]
>    Unloading kernel modules... [  OK  ]
>    Unmounting configfs... [  OK  ]
> Starting cluster:
>    Checking if cluster has been disabled at boot... [  OK  ]
>    Checking Network Manager... [  OK  ]
>    Global setup... [  OK  ]
>    Loading kernel modules... [  OK  ]
>    Mounting configfs... [  OK  ]
>    Starting cman... [  OK  ]
>    Waiting for quorum... Timed-out waiting for cluster
> [FAILED]
And syslog since cman restart is here: http://pastebin.com/rFhj2h0g

On 10.04.15 6:29, Dietmar Maurer wrote:
> Those are just debug messages - I cannot see real errors there.
>
>> On April 9, 2015 at 7:31 PM Sten Aus <sten.aus at eenet.ee> wrote:
>>
>>
>>> Are there any corosync/cman related messages in the syslog?
>> Yes, It's from 7th April, but anyway there are a lot of these messages
>> and they're at the same timestamp. Adding a new node (which has not been
>> in cluster)
>>> Apr 07 18:00:42 corosync [TOTEM ] A processor joined or left the
>>> membership and a new membership was formed.
>>> Apr 07 18:00:42 corosync [CMAN  ] quorum regained, resuming activity
>>> Apr 07 18:00:42 corosync [QUORUM] This node is within the primary
>>> component and will provide service.
>>> Apr 07 18:00:42 corosync [QUORUM] Members[1]: 2
>>> Apr 07 18:00:42 corosync [CMAN  ] quorum lost, blocking activity
>>> Apr 07 18:00:42 corosync [QUORUM] This node is within the non-primary
>>> component and will NOT provide any services.
>>> Apr 07 18:00:42 corosync [QUORUM] Members[1]: 2
>>> Apr 07 18:00:42 corosync [QUORUM] Members[2]: 2 4
>>> Apr 07 18:00:42 corosync [QUORUM] Members[2]: 2 4
>>> Apr 07 18:00:42 corosync [QUORUM] Members[3]: 2 4 6
>>> Apr 07 18:00:42 corosync [QUORUM] Members[3]: 2 4 6
>>> Apr 07 18:00:42 corosync [QUORUM] Members[4]: 2 4 5 6
>>> Apr 07 18:00:42 corosync [QUORUM] Members[4]: 2 4 5 6
>>> Apr 07 18:00:42 corosync [QUORUM] Members[5]: 2 3 4 5 6
>>> Apr 07 18:00:42 corosync [QUORUM] Members[5]: 2 3 4 5 6
>>> Apr 07 18:00:42 corosync [QUORUM] Members[6]: 2 3 4 5 6 7
>>> Apr 07 18:00:42 corosync [QUORUM] Members[6]: 2 3 4 5 6 7
>>> Apr 07 18:00:42 corosync [CMAN  ] quorum regained, resuming activity
>>> Apr 07 18:00:42 corosync [QUORUM] This node is within the primary
>>> component and will provide service.
>>> Apr 07 18:00:42 corosync [QUORUM] Members[7]: 2 3 4 5 6 7 13
>>> Apr 07 18:00:42 corosync [QUORUM] Members[7]: 2 3 4 5 6 7 13
>>> Apr 07 18:00:42 corosync [QUORUM] Members[8]: 2 3 4 5 6 7 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[8]: 2 3 4 5 6 7 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[9]: 2 3 4 5 6 7 9 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[9]: 2 3 4 5 6 7 9 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[10]: 2 3 4 5 6 7 8 9 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[10]: 2 3 4 5 6 7 8 9 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[11]: 2 3 4 5 6 7 8 9 10 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[11]: 2 3 4 5 6 7 8 9 10 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[12]: 2 3 4 5 6 7 8 9 10 11
>>> 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[12]: 2 3 4 5 6 7 8 9 10 11
>>> 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[13]: 2 3 4 5 6 7 8 9 10 11
>>> 12 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[13]: 2 3 4 5 6 7 8 9 10 11
>>> 12 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[14]: 1 2 3 4 5 6 7 8 9 10 11
>>> 12 13 14
>>> Apr 07 18:00:42 corosync [QUORUM] Members[14]: 1 2 3 4 5 6 7 8 9 10 11
>>> 12 13 14


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3242 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20150410/ea08b251/attachment.bin>