On 06/11/17 10:43 +0000, Somanath Jeeva wrote:
> I am using a two node pacemaker cluster with teaming enabled. The cluster has
>
> 1. Two team interfaces with different subents.
>
> 2. The team1 has a NFS VIP plumbed to it.
>
> 3. The VirtualIP from pacemaker is configured to plumb to
> team0(Corosync ring number is 0)
>
> In this case the corosync takes the NFS IP as its ring address and
> checks the same in the corosync.conf. Since conf file has team0
> hostname the corosync start fails.
>
> Outputs:
>
>
> $ip a output:
>
> [...]
> 10: team1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
> qlen 1000
> link/ether 38:63:bb:3f:a4:ad brd ff:ff:ff:ff:ff:ff
> inet 10.64.23.117/28 brd 10.64.23.127 scope global team1
> valid_lft forever preferred_lft forever
> inet 10.64.23.121/24 scope global secondary team1:~m0
> valid_lft forever preferred_lft forever
> inet6 fe80::3a63:bbff:fe3f:a4ad/64 scope link
> valid_lft forever preferred_lft forever
> 11: team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
> qlen 1000
> link/ether 38:63:bb:3f:a4:ac brd ff:ff:ff:ff:ff:ff
> inet 10.64.23.103/28 brd 10.64.23.111 scope global team0
> valid_lft forever preferred_lft forever
> inet6 fe80::3a63:bbff:fe3f:a4ac/64 scope link
> valid_lft forever preferred_lft forever
>
> Corosync Conf File:
>
> cat /etc/corosync/corosync.conf
> totem {
> version: 2
> secauth: off
> cluster_name: DES
> transport: udp
> rrp_mode: passive
>
> interface {
> ringnumber: 0
> bindnetaddr: 10.64.23.96
> mcastaddr: 224.1.1.1
> mcastport: 6860
> }
> }
>
> nodelist {
> node {
> ring0_addr: dl380x4415
> nodeid: 1
> }
>
> node {
> ring0_addr: dl360x4405
> nodeid: 2
> }
> }
>
> quorum {
> provider: corosync_votequorum
> two_node: 1
> }
>
> logging {
> to_logfile: yes
> logfile: /var/log/cluster/corosync.log
> to_syslog: yes
> }
>
> /etc/hosts:
>
> $ cat /etc/hosts
> [...]
> 10.64.23.103 dl380x4415
> 10.64.23.105 dl360x4405
> [...]
>
> Logs:
>
> [3029] dl380x4415 corosyncerror [MAIN ] Corosync Cluster Engine exiting
> with status 20 at service.c:356.
> [19040] dl380x4415 corosyncnotice [MAIN ] Corosync Cluster Engine
> ('2.4.0'): started and ready to provide service.
> [19040] dl380x4415 corosyncinfo [MAIN ] Corosync built-in features: dbus
> systemd xmlconf qdevices qnetd snmp pie relro bindnow
> [19040] dl380x4415 corosyncnotice [TOTEM ] Initializing transport (UDP/IP
> Multicast).
> [19040] dl380x4415 corosyncnotice [TOTEM ] Initializing transmit/receive
> security (NSS) crypto: none hash: none
> [19040] dl380x4415 corosyncnotice [TOTEM ] The network interface
> [10.64.23.121] is now up.
> [19040] dl380x4415 corosyncnotice [SERV ] Service engine loaded: corosync
> configuration map access [0]
> [19040] dl380x4415 corosyncinfo [QB ] server name: cmap
> [19040] dl380x4415 corosyncnotice [SERV ] Service engine loaded: corosync
> configuration service [1]
> [19040] dl380x4415 corosyncinfo [QB ] server name: cfg
> [19040] dl380x4415 corosyncnotice [SERV ] Service engine loaded: corosync
> cluster closed process group service v1.01 [2]
> [19040] dl380x4415 corosyncinfo [QB ] server name: cpg
> [19040] dl380x4415 corosyncnotice [SERV ] Service engine loaded: corosync
> profile loading service [4]
> [19040] dl380x4415 corosyncnotice [QUORUM] Using quorum provider
> corosync_votequorum
> [19040] dl380x4415 corosynccrit [QUORUM] Quorum provider:
> corosync_votequorum failed to initialize.
> [19040] dl380x4415 corosyncerror [SERV ] Service engine 'corosync_quorum'
> failed to load for reason 'configuration error: nodelist or
> quorum.expected_votes must be configured!'I suspect whether teaming is involved or not is irrelevant here. You are not using the latest greatest 2.4.3, so I'd suggest either the upgrade or applying this patch (present in that version) if that helps: https://github.com/corosync/corosync/commit/95f9583a25007398e3792bdca2da262db18f658a -- Jan (Poki)
pgp0OKftGQYvR.pgp
Description: PGP signature
_______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.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
