It does not start vm

[nevz00]

When you start the VM error....
cluster not ready - no quorum? (500)

Please help me in my problem...

If I write pvecm e 1 outputs Cannot initialize CMAP service

 

[t.lamprecht]

If I write pvecm e 1 outputs Cannot initialize CMAP service

That means that corosync does failed to start, any changes in the cluster configuration lately?

Can you post the output of:

cat /etc/pve/corosync.conf
journalctl -u corosync -u pve-cluster --since "-2days"

Adapt the "-2days" to roughly before the time it started to fail.

This will only work if you use Proxmox VE in version 4.0 or newer.

 

[nevz00]

cat /etc/pve/corosync.conf
ip_version ipv4
interface{
ringnumber: 0
bindnetaddr: 192.168.0.2
}
}
nodelist{
node{
ring0_addr: pve
name: pve
nodeid: 1
quorum_votes: 1
}
}
quorum{
provider: corosync_votequorum
}
logging{
to_syslog: yes
debug: off
}



It can be, in general, you can delete a cluster?
Or delete file corosync.conf ???

 

[t.lamprecht]

It can be, in general, you can delete a cluster?

Yes, and in your case with a single node cluster it should be quite easy.

Do:

systemctl stop pve-cluster
systemctl stop corosync # just to be sure
pmxcfs -l
rm /etc/pve/corosync.conf
rm /etc/corosync/*
killall pmxcfs
systemctl start pve-cluster

This stops the cluster filesystem and restarts it in local mode, then removers the cluster (corosync) configuration, kills the local mode cluster filesystem and restart it in normal mode again. Some more information about this can be found in our reference documentation: http://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_separate_node_without_reinstall

Do that only if you have a single node cluster. If you had configured other nodes in this cluster don't do that for now and please post the output of journalctl I posted above.