/etc/pve read-only after "pvecm create ProxCluster01"

Matteo Calorio

Well-Known Member
Jun 30, 2017
34
0
46
53
Hello to everybody, I just subscribed to this group.

I have a machine running Debian 8.8 and Proxmox 4.4, with some KVM machines on it.

On this machine I run a "pvecm create ProxCluster01" and I broke the configuration.

All the machines are still running, but I cannot change their configuration or status, probably because the mount point /etc/pve is mounted but read only.

How can I go back? I'm quite sure is just a little configuration somewere, but I do not have enough experience to solve this issue.

Here are some errors I get:

Code:
# pvecm expected 1
Cannot initialize CMAP service

# systemctl status corosync.service; journalctl -xn
● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled)
   Active: failed (Result: exit-code) since gio 2017-06-29 17:53:24 CEST; 23min ago
  Process: 139199 ExecStart=/usr/share/corosync/corosync start (code=exited, status=1/FAILURE)

giu 29 17:52:23 proxmox corosync[139206]: [QB    ] server name: cmap
giu 29 17:52:23 proxmox corosync[139206]: [SERV  ] Service engine loaded: corosync configuration service [1]
giu 29 17:52:23 proxmox corosync[139206]: [QB    ] server name: cfg
giu 29 17:52:23 proxmox corosync[139206]: [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
giu 29 17:52:23 proxmox corosync[139206]: [QB    ] server name: cpg
giu 29 17:52:23 proxmox corosync[139206]: [SERV  ] Service engine loaded: corosync profile loading service [4]
giu 29 17:53:24 proxmox corosync[139199]: Starting Corosync Cluster Engine (corosync): [FAILED]
giu 29 17:53:24 proxmox systemd[1]: corosync.service: control process exited, code=exited status=1
giu 29 17:53:24 proxmox systemd[1]: Failed to start Corosync Cluster Engine.
giu 29 17:53:24 proxmox systemd[1]: Unit corosync.service entered failed state.
-- Logs begin at mar 2017-06-27 09:06:48 CEST, end at gio 2017-06-29 18:16:44 CEST. --
giu 29 18:16:32 proxmox pmxcfs[128357]: [dcdb] crit: cpg_initialize failed: 2
giu 29 18:16:32 proxmox pmxcfs[128357]: [status] crit: cpg_initialize failed: 2
giu 29 18:16:38 proxmox pmxcfs[128357]: [quorum] crit: quorum_initialize failed: 2
giu 29 18:16:38 proxmox pmxcfs[128357]: [confdb] crit: cmap_initialize failed: 2
giu 29 18:16:38 proxmox pmxcfs[128357]: [dcdb] crit: cpg_initialize failed: 2
giu 29 18:16:38 proxmox pmxcfs[128357]: [status] crit: cpg_initialize failed: 2
giu 29 18:16:44 proxmox pmxcfs[128357]: [quorum] crit: quorum_initialize failed: 2
giu 29 18:16:44 proxmox pmxcfs[128357]: [confdb] crit: cmap_initialize failed: 2
giu 29 18:16:44 proxmox pmxcfs[128357]: [dcdb] crit: cpg_initialize failed: 2
giu 29 18:16:44 proxmox pmxcfs[128357]: [status] crit: cpg_initialize failed: 2

Please, can you help me?

Matteo
 
Solved following a link I can't post:

linux-tips,com!t!couldnt-start-virtual-machines-after-proxmox-4-1-upgrade!317!2

I'll try again with "pvecm create ProxCluster01", now that I have the "antidote", but what if again it doesn't work?

Matteo