corosync not running, file /etc/pve/corosync.conf impossible write

[yann44]

Hi, I'm french and my English is very little (sorry),

the service corosynch no running because the file /etc/pve/corosync.conf is no good in the prox-1.

Jan 13 08:09:50 PROX-1 systemd[1]: Starting Corosync Cluster Engine...
Jan 13 08:09:50 PROX-1 corosync[1060]: [MAIN ] Corosync Cluster Engine 3.0.2 starting up
Jan 13 08:09:50 PROX-1 corosync[1060]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf snmp pie relro bindnow
Jan 13 08:09:50 PROX-1 corosync[1060]: [MAIN ] failed to parse node address 'PROX-2'
Jan 13 08:09:50 PROX-1 corosync[1060]: [MAIN ] Corosync Cluster Engine exiting with status 8 at main.c:1353.
Jan 13 08:09:50 PROX-1 systemd[1]: corosync.service: Main process exited, code=exited, status=8/n/a
Jan 13 08:09:50 PROX-1 systemd[1]: corosync.service: Failed with result 'exit-code'.
Jan 13 08:09:50 PROX-1 systemd[1]: Failed to start Corosync Cluster Engine.


i want enter address ip in file /etc/pve/corosync.conf but it's not writable. (r..r..r..)
chmod 644 /etc/pve/corosync.conf :

root@PROX-1:/etc/pve# chmod 644 /etc/pve/corosync.conf
chmod: changing permissions of '/etc/pve/corosync.conf': Operation not permitted

tank for help me

Yann

 

[Klaus Steinberger]

Look here:

https://pve.proxmox.com/wiki/Cluster_Manager

the relevant part for you:

https://pve.proxmox.com/wiki/Cluster_Manager

 

[Klaus Steinberger]

Look here:

https://pve.proxmox.com/wiki/Cluster_Manager

the relevant part for you:

https://pve.proxmox.com/wiki/Cluster_Manager

Sorry, just hit the post button to early, now here the relevant information:

Write Configuration When Not Quorate
If you need to change /etc/pve/corosync.conf on an node with no quorum, and you know what you do, use:
pvecm expected 1
This sets the expected vote count to 1 and makes the cluster quorate. You can now fix your configuration, or revert it back to the last working backup.
This is not enough if corosync cannot start anymore. Here it is best to edit the local copy of the corosync configuration in /etc/corosync/corosync.conf so that corosync can start again. Ensure that on all nodes this configuration has the same content to avoid split brains. If you are not sure what went wrong it’s best to ask the Proxmox Community to help you.

 

[yann44]

Hello, CMAP service HS?

systemctl service fail:

● cgmanager.service                                                                                loaded failed     failed          Cgroup management daemon

● corosync.service                                                                                    loaded failed     failed          Corosync Cluster Engine

● pvesr.service                                                                                          loaded failed     failed          Proxmox VE replication runner

root@PROX-1:~# pvecm status

Cluster information

-------------------

Name:             STFL

Config Version:   2

Transport:        knet

Secure auth:      on


Cannot initialize CMAP service