II accidentally clicked and created the cluster, causing all virtual machines to fail to start.

M

meng

New Member
Jul 5, 2019
4
0
1
32
I accidentally clicked and created the cluster, causing all the virtual machines to start up. Is there any way to get them to boot normally? I only have one node now, can I restore the virtual machine without deleting the cluster? Thanks
 
Is this a standalone node?
It should be fine after creating it's own "cluster".

What error do you get when trying to start a vm?
 
mbosma said:
Is this a standalone node?
It should be fine after creating it's own "cluster".

What error do you get when trying to start a vm?
Click to expand...

it says that: cluster not ready - no quorum? (500)

when i click clone or start
all the same
 
If you have only one server in a cluster and want to run services execute:

pvecm expected 1

But later remember to fix it, if you add more servers to the cluster.
 
pvecm expected 1

"Cannot initialize CMAP service",

pvecm status
Cannot initialize CMAP service


pvecm add 192.168.7.240 -ring0_addr 192.168.7.240
detected the following error(s):
* authentication key '/etc/corosync/authkey' already exists
* cluster config '/etc/pve/corosync.conf' already exists
* this host already contains virtual guests
Check if node may join a cluster failed!


omping 192.168.7.240
192.168.7.240 : waiting for response msg
192.168.7.240 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.7.240 : unicast, seq=1, size=69 bytes, dist=0, time=0.033ms
192.168.7.240 : multicast, seq=1, size=69 bytes, dist=0, time=0.045ms
192.168.7.240 : unicast, seq=2, size=69 bytes, dist=0, time=0.030ms
192.168.7.240 : multicast, seq=2, size=69 bytes, dist=0, time=0.036ms



root@admin:~# systemctl restart pve-cluster.service
root@admin:~# systemctl restart pvedaemon.service
root@admin:~# systemctl restart pveproxy.service
root@admin:~# systemctl restart corosync.service
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.




root@admin:~# systemctl restart corosync.service
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
root@admin:~# service corosync status
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-07-05 17:31:28 CST; 21s ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Process: 6246 ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS (code=exited, status=20)
Main PID: 6246 (code=exited, status=20)
CPU: 53ms

jul 05 17:31:28 admin corosync[6246]: info [WD ] no resources configured.
Jul 05 17:31:28 admin corosync[6246]: notice [SERV ] Service engine loaded: corosync watchdog service [7
Jul 05 17:31:28 admin corosync[6246]: notice [QUORUM] Using quorum provider corosync_votequorum
Jul 05 17:31:28 admin corosync[6246]: crit [QUORUM] Quorum provider: corosync_votequorum failed to init
Jul 05 17:31:28 admin corosync[6246]: error [SERV ] Service engine 'corosync_quorum' failed to load for
Jul 05 17:31:28 admin corosync[6246]: error [MAIN ] Corosync Cluster Engine exiting with status 20 at s
Jul 05 17:31:28 admin systemd[1]: corosync.service: Main process exited, code=exited, status=20/n/a
Jul 05 17:31:28 admin systemd[1]: Failed to start Corosync Cluster Engine.
Jul 05 17:31:28 admin systemd[1]: corosync.service: Unit entered failed state.
Jul 05 17:31:28 admin systemd[1]: corosync.service: Failed with result 'exit-code'.

root@admin:~# service cocosync start
Failed to start cocosync.service: Unit cocosync.service not found.
root@admin:~# service corosync start
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
root@admin:~# service corosync status
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-07-05 17:32:52 CST; 12s ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Process: 6432 ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS (code=exited, status=20)
Main PID: 6432 (code=exited, status=20)
CPU: 53ms
Jul 05 17:32:52 admin corosync[6432]: info [WD ] no resources configured.
Jul 05 17:32:52 admin corosync[6432]: notice [SERV ] Service engine loaded: corosync watchdog service [7
Jul 05 17:32:52 admin corosync[6432]: notice [QUORUM] Using quorum provider corosync_votequorum
Jul 05 17:32:52 admin corosync[6432]: crit [QUORUM] Quorum provider: corosync_votequorum failed to init
Jul 05 17:32:52 admin corosync[6432]: error [SERV ] Service engine 'corosync_quorum' failed to load for
Jul 05 17:32:52 admin corosync[6432]: error [MAIN ] Corosync Cluster Engine exiting with status 20 at s
Jul 05 17:32:52 admin systemd[1]: corosync.service: Main process exited, code=exited, status=20/n/a
Jul 05 17:32:52 admin systemd[1]: Failed to start Corosync Cluster Engine.
Jul 05 17:32:52 admin systemd[1]: corosync.service: Unit entered failed state.
Jul 05 17:32:52 admin systemd[1]: corosync.service: Failed with result 'exit-code'.


root@admin:~# journalctl -xe
Jul 05 18:10:13 admin corosync[9540]: error [MAIN ] Corosync Cluster Engine exiting with status 20 at s
Jul 05 18:10:13 admin corosync[9540]: [SERV ] Service engine loaded: corosync configuration map access [
Jul 05 18:10:13 admin corosync[9540]: [QB ] server name: cmap
Jul 05 18:10:13 admin corosync[9540]: [SERV ] Service engine loaded: corosync configuration service [1]
Jul 05 18:10:13 admin corosync[9540]: [QB ] server name: cfg
Jul 05 18:10:13 admin corosync[9540]: [SERV ] Service engine loaded: corosync cluster closed process gro
Jul 05 18:10:13 admin corosync[9540]: [QB ] server name: cpg
Jul 05 18:10:13 admin corosync[9540]: [SERV ] Service engine loaded: corosync profile loading service [4
Jul 05 18:10:13 admin corosync[9540]: [SERV ] Service engine loaded: corosync resource monitoring servic
Jul 05 18:10:13 admin corosync[9540]: [WD ] Watchdog not enabled by configuration
Jul 05 18:10:13 admin corosync[9540]: [WD ] resource load_15min missing a recovery key.
Jul 05 18:10:13 admin corosync[9540]: [WD ] resource memory_used missing a recovery key.
Jul 05 18:10:13 admin corosync[9540]: [WD ] no resources configured.
Jul 05 18:10:13 admin corosync[9540]: [SERV ] Service engine loaded: corosync watchdog service [7]
Jul 05 18:10:13 admin corosync[9540]: [QUORUM] Using quorum provider corosync_votequorum
Jul 05 18:10:13 admin corosync[9540]: [QUORUM] Quorum provider: corosync_votequorum failed to initialize.
Jul 05 18:10:13 admin corosync[9540]: [SERV ] Service engine 'corosync_quorum' failed to load for reason
Jul 05 18:10:13 admin corosync[9540]: [MAIN ] Corosync Cluster Engine exiting with status 20 at service.
Jul 05 18:10:13 admin systemd[1]: corosync.service: Main process exited, code=exited, status=20/n/a
Jul 05 18:10:13 admin systemd[1]: Failed to start Corosync Cluster Engine.
-- Subject: Unit corosync.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit corosync.service has failed.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back