[ClusterLabs] CentOS 7 - Corosync configuration
Willi Fehler
willi.fehler at t-online.de
Fri Mar 6 15:05:26 CET 2015
Hi,
anybody an idea? I think something in my corosync configuration is
incorrect. The default Corosync configuration is working. But I want to
use redundant rings and secuath should be set to on.
[root at linsrv006 ~]# cat /etc/corosync/corosync.conf
totem {
version: 2
secauth: off
cluster_name: databasecluster
transport: udpu
}
nodelist {
node {
ring0_addr: linsrv006.willi-net.local
nodeid: 1
}
node {
ring0_addr: linsrv007.willi-net.local
nodeid: 2
}
}
quorum {
provider: corosync_votequorum
two_node: 1
}
logging {
to_syslog: yes
}
[root at linsrv006 ~]# pcs status
Cluster name: databasecluster
WARNING: no stonith devices and stonith-enabled is not false
Last updated: Fri Mar 6 15:04:13 2015
Last change: Fri Mar 6 15:03:23 2015 via crmd on linsrv007.willi-net.local
Stack: corosync
Current DC: linsrv007.willi-net.local (2) - partition with quorum
Version: 1.1.10-32.el7_0.1-368c726
2 Nodes configured
0 Resources configured
Online: [ linsrv006.willi-net.local linsrv007.willi-net.local ]
Full list of resources:
PCSD Status:
linsrv006.willi-net.local: Online
linsrv007.willi-net.local: Online
Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled
Regards - Willi
Am 06.03.15 um 10:49 schrieb Willi Fehler:
> Hi,
>
> I've fixed the node issue. I changed the /etc/hosts file and rebuilded
> the Cluster with the fqdn names:
>
> [root at linsrv006 corosync]# pcs status
> Cluster name:
> WARNING: no stonith devices and stonith-enabled is not false
> Last updated: Fri Mar 6 10:47:25 2015
> Last change: Fri Mar 6 10:45:43 2015 via crmd on
> linsrv006.willi-net.local
> Stack: corosync
> Current DC: NONE
> 2 Nodes configured
> 0 Resources configured
>
>
> Node linsrv006.willi-net.local (1): UNCLEAN (offline)
> Node linsrv007.willi-net.local (2): UNCLEAN (offline)
>
> Full list of resources:
>
>
> PCSD Status:
> 192.168.0.9: Unable to authenticate
> 192.168.0.10: Unable to authenticate
>
> Daemon Status:
> corosync: active/disabled
> pacemaker: active/disabled
> pcsd: active/enabled
>
>
>
>
> totem {
> version: 2
> threads: 2
> secauth: on
> cluster_name: databasecluster
> rrp_mode: passive
> join: 100
> max_messages: 20
> vstype: none
> token: 1000
> consensus: 1200
> clear_node_high_bit: true
> token_retransmits_before_loss_const: 10
> interface {
> ringnumber: 0
> bindnetaddr: 192.168.0.0
> mcastaddr: 239.255.1.1
> mcastport: 5404
> }
> interface {
> ringnumber: 1
> bindnetaddr: 10.10.10.0
> mcastaddr: 239.255.2.1
> mcastport: 5406
> }
> transport: udpu
> }
>
> nodelist {
> node {
> ring0_addr: 192.168.0.9
> ring1_addr: 10.10.10.1
> nodeid: 1
> }
> node {
> ring0_addr: 192.168.0.10
> ring1_addr: 10.10.10.2
> nodeid: 2
> }
> }
>
> logging {
> to_syslog: yes
> }
>
>
>
> [root at linsrv006 corosync]# tail -f /var/log/messages
> Mar 6 10:49:02 linsrv006 stonith-ng[8025]: notice: get_node_name:
> Could not obtain a node name for corosync nodeid 2
> Mar 6 10:49:02 linsrv006 crmd[8029]: error: cluster_connect_quorum:
> Corosync quorum is not configured
> Mar 6 10:49:02 linsrv006 stonith-ng[8025]: notice:
> corosync_node_name: Unable to get node name for nodeid 1
> Mar 6 10:49:02 linsrv006 stonith-ng[8025]: notice: get_node_name:
> Defaulting to uname -n for the local corosync node name
> Mar 6 10:49:02 linsrv006 crmd[8029]: notice: corosync_node_name:
> Unable to get node name for nodeid 1
> Mar 6 10:49:02 linsrv006 crmd[8029]: notice: corosync_node_name:
> Unable to get node name for nodeid 2
> Mar 6 10:49:02 linsrv006 crmd[8029]: notice: corosync_node_name:
> Unable to get node name for nodeid 2
> Mar 6 10:49:02 linsrv006 crmd[8029]: notice: get_node_name: Could not
> obtain a node name for corosync nodeid 2
> Mar 6 10:49:02 linsrv006 crmd[8029]: notice: corosync_node_name:
> Unable to get node name for nodeid 2
> Mar 6 10:49:02 linsrv006 crmd[8029]: notice: get_node_name: Could not
> obtain a node name for corosync nodeid 2
>
> Regards - Willi
>
> Am 06.03.15 um 10:41 schrieb Willi Fehler:
>> [root at linsrv006 corosync]# rpm -qa | grep corosync
>> corosynclib-2.3.3-2.el7_0.1.x86_64
>> corosync-2.3.3-2.el7_0.1.x86_64
>>
>> Am 06.03.15 um 10:32 schrieb Michael Schwartzkopff:
>>> Am Freitag, 6. März 2015, 10:18:46 schrieb Willi Fehler:
>>>> Hi Michael,
>>>>
>>>> firewalld is disabled. It looks like corosync-objctl does not exist.
>>>>
>>>> Regards - Willi
>>> which version of corosync?
>>>
>>> Mit freundlichen Grüßen,
>>>
>>> Michael Schwartzkopff
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list:Users at clusterlabs.org
>>> http://clusterlabs.org/mailman/listinfo/users
>>>
>>> Project Home:http://www.clusterlabs.org
>>> Getting started:http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs:http://bugs.clusterlabs.org
>>
>>
>>
>> _______________________________________________
>> Users mailing list:Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home:http://www.clusterlabs.org
>> Getting started:http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs:http://bugs.clusterlabs.org
>
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://clusterlabs.org/pipermail/users/attachments/20150306/6826122b/attachment.html>
More information about the Users
mailing list