parse error - uncexpected '}' (500)

[gdi2k]

I have an issue where I get the following error when trying to create a new HA resource in my cluster (Datacenter -> HA -> Resources -> Add).

parse error - uncexpected '}' (500)

I am sure this is my own fault - I modified corosync.conf to add a separate corosync network as backup as per the guide here:
https://pve.proxmox.com/wiki/Separate_Cluster_Network

But I messed up (added an additional curly bracket), which broke corosync. After fixing the bracket issue, everything seems to work fine, but I have this issue. Any idea where I could look?

For reference, my corosync.conf now looks like this:

root@sb1:~# cat /etc/corosync/corosync.conf
logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: sb1
    nodeid: 1
    quorum_votes: 1
    ring0_addr: sb1
    ring1_addr: 10.32.112.1
  }
  node {
    name: sb2
    nodeid: 2
    quorum_votes: 1
    ring0_addr: sb2
    ring1_addr: 10.32.112.2
  }
  node {
    name: sb3
    nodeid: 3
    quorum_votes: 1
    ring0_addr: sb3
    ring1_addr: 10.32.112.3
  }
}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: smiles2
  config_version: 5
  interface {
    bindnetaddr: 10.32.32.1
    ringnumber: 0
  }
  interface {
    bindnetaddr: 10.32.112.1
    ringnumber: 1
  }


  ip_version: ipv4
  rrp_mode: passive
  secauth: on
  version: 2
}

 

[Alwin]

'/etc/pve/corosync.conf' and '/etc/corosync/corosync.conf' need to be identical.

 

[gdi2k]

Thanks for the suggestion - I checked and both files are identical on all 3 cluster members.

root@smiles3:~# diff /etc/corosync/corosync.conf /etc/pve/corosync.conf -s
Files /etc/corosync/corosync.conf and /etc/pve/corosync.conf are identical

 

[gdi2k]

I'd like to gently bump this. This cluster will go into production and I can't afford for there to be any issues with HA. If I can't resolve it I'll need to reinstall it from scratch which I would prefer to avoid.

 

[wolfgang]

Are you cluster updated and all nodes on the same version?
Do you use the correct repositories?

 

[gdi2k]

Yes, the cluster members are fully up to date using the free repo configs (for now).

In the end I just reinstalled - I didn't want to risk there being a problem with clustering down the line.