[ClusterLabs] Could not initialize corosync configuration API error 2

[Jan Friesse]

Hi,

On 31/03/2023 11:36, S Sathish S wrote:
> Hi Team,
> 
> Please find the corosync version.
> 
> [root at node2 ~]# rpm -qa corosync
> corosync-2.4.4-2.el7.x86_64.

RHEL 7 never got 2.4.4 - there was 2.4.3 in RHEL 7.7 and 2.4.5 in RHEL 
7.8/7.9. Is this self compiled version? If so, please consider updating 
to distro provided package - RHEL 7 package IS actively maintained.


> 
> Firewall in disable state only.
> 
> Please find the debug and trace logs
> 
> Mar 31 10:07:30 [17684] node2 corosync notice  [MAIN  ] Corosync Cluster Engine ('UNKNOWN'): started and ready to provide service.
> Mar 31 10:07:30 [17684] node2 corosync info    [MAIN  ] Corosync built-in features: pie relro bindnow
> Mar 31 10:07:30 [17684] node2 corosync warning [MAIN  ] Could not set SCHED_RR at priority 99: Operation not permitted (1)

This is weird - is corosync running as a root?

> Mar 31 10:07:30 [17684] node2 corosync debug   [QB    ] shm size:8388621; real_size:8392704; rb->word_size:2098176
> Mar 31 10:07:30 [17684] node2 corosync debug   [MAIN  ] Corosync TTY detached
> Mar 31 10:07:30 [17684] node2 corosync debug   [TOTEM ] waiting_trans_ack changed to 1
> Mar 31 10:07:30 [17684] node2 corosync debug   [TOTEM ] Token Timeout (5550 ms)


...

> Mar 31 10:07:30 [17684] node2 corosync debug   [TOTEM ] entering GATHER state from 11(merge during join).


This is important. Usually this means there is forgotten node somewhere 
trying to connect to existing cluster or config files between nodes 
differs. Solution is:
1. Check corosync.conf is equal on all nodes
2. Update to distro package (2.4.5) which contains block_unlisted_ips 
functionality/option (enabled by default) and/or generate new crypto 
key, distribute it only to nodes within cluster (so node1 .. node9) and 
turn on crypto,


> Mar 31 10:07:30 [17684] node2 corosync debug   [TOTEM ] entering GATHER state from 11(merge during join).
> Mar 31 10:07:30 [17684] node2 corosync debug   [TOTEM ] entering GATHER state from 

...

> 
> 
> 
> 
> Please find the corosync conf file.
> 
> [root at node2 ~]# cat /etc/corosync/corosync.conf
> totem {
>      version: 2
>      cluster_name: OCC
>      secauth: off

it's really good idea to turn on crypto

>      transport: udpu
> }
> 
> 
> 
> nodelist {
>      node {
>          ring0_addr: node1
>          nodeid: 1
>      }
> 
> 
> 
>      node {
>          ring0_addr: node2
>          nodeid: 2
>      }
> 
> 
> 
>      node {
>          ring0_addr: node3
>          nodeid: 3
>      }
> 
> 
> 
>      node {
>          ring0_addr: node4
>          nodeid: 4
>      }
> 
> 
> 
>      node {
>          ring0_addr: node5
>          nodeid: 5
>      }
> 
> 
> 
>      node {
>          ring0_addr: node6
>          nodeid: 6
>      }
> 
> 
> 
>      node {
>          ring0_addr: node7
>          nodeid: 7
>      }
> 
> 
> 
>      node {
>          ring0_addr: node8
>          nodeid: 8
>      }
> 
> 
> 
>      node {
>          ring0_addr: node9
>          nodeid: 9
>      }
> }
> 
> 
> 
> quorum {
>      provider: corosync_votequorum
> }
> 
> 
> 
> logging {
>      to_logfile: yes
>      logfile: /var/log/cluster/corosync.log
>      to_syslog: no
> timestamp:on
> }
> 

Regards,
   Honza

> Thanks and Regards,
> S Sathish S
>