status unknown

linhu

New Member
Aug 19, 2023
27
0
1
Hi i have a testsetup with 2 servers and 2 testvm's.
What meeens status unknown and how can i resolv this?

The scenario was a server goes offline, after i have removed this server from the cluster all was fine.
But the next was the server comes online again, added to the cluster and now this:

prox1 and 2 are in a cluster

root@prox1:~# pvecm status
Cluster information
-------------------
Name: linuxhus1
Config Version: 2
Transport: knet
Secure auth: on

Quorum information
------------------
Date: Thu Aug 24 16:11:31 2023
Quorum provider: corosync_votequorum
Nodes: 2
Node ID: 0x00000002
Ring ID: 1.23
Quorate: Yes

Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 2
Quorum: 2
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.1.151
0x00000002 1 192.168.1.150 (local)
root@prox1:~#


Bildschirmfoto 2023-08-24 um 16.05.03.png
 
Last edited:
ok have setup a qdevice, but its still unknown.
the nodes are online but the storage is unknown
Bildschirmfoto 2023-08-24 um 16.55.59.png
 
Last edited:
Aug 24 16:54:06 prox1 pve-guests[1101]: mount error: received interrupt
Aug 24 16:52:41 prox1 pmxcfs[825]: [status] crit: can't initialize service
Aug 24 16:52:41 prox1 pmxcfs[825]: [status] crit: cpg_initialize failed: 2
Aug 24 16:52:41 prox1 pmxcfs[825]: [dcdb] crit: can't initialize service
Aug 24 16:52:41 prox1 pmxcfs[825]: [dcdb] crit: cpg_initialize failed: 2
Aug 24 16:52:41 prox1 pmxcfs[825]: [confdb] crit: can't initialize service
Aug 24 16:52:41 prox1 pmxcfs[825]: [confdb] crit: cmap_initialize failed: 2
Aug 24 16:52:41 prox1 pmxcfs[825]: [quorum] crit: can't initialize service
Aug 24 16:52:41 prox1 pmxcfs[825]: [quorum] crit: quorum_initialize failed: 2
-- Boot cac268d3825f413198e6db1dfdbbf28d --
Aug 24 16:51:26 prox1 kernel: watchdog: watchdog0: watchdog did not stop!
Aug 24 16:51:25 prox1 pmxcfs[2635]: [confdb] crit: cmap_finalize failed: 9
Aug 24 16:51:25 prox1 pmxcfs[2635]: [confdb] crit: cmap_track_delete version failed: 9
Aug 24 16:51:25 prox1 pmxcfs[2635]: [confdb] crit: cmap_track_delete nodelist failed: 9
Aug 24 16:51:25 prox1 pmxcfs[2635]: [quorum] crit: quorum_finalize failed: 9
Aug 24 16:51:24 prox1 pmxcfs[2635]: [status] crit: can't initialize service
Aug 24 16:51:24 prox1 pmxcfs[2635]: [status] crit: cpg_initialize failed: 2
Aug 24 16:51:24 prox1 pmxcfs[2635]: [dcdb] crit: can't initialize service
Aug 24 16:51:24 prox1 pmxcfs[2635]: [dcdb] crit: cpg_initialize failed: 2
 
Did you try restarting the corosync and pve-cluster services? If the storage does not come back up in 2 minutes you could restart the pvestatd service and see if the situation improves.
 
the nodes are back but no storrage
Aug 24 17:40:08 prox1 pmxcfs[13496]: [status] crit: can't initialize service
Aug 24 17:40:08 prox1 pmxcfs[13496]: [status] crit: cpg_initialize failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [dcdb] crit: can't initialize service
Aug 24 17:40:08 prox1 pmxcfs[13496]: [dcdb] crit: cpg_initialize failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [confdb] crit: can't initialize service
Aug 24 17:40:08 prox1 pmxcfs[13496]: [confdb] crit: cmap_initialize failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [quorum] crit: can't initialize service
Aug 24 17:40:08 prox1 pmxcfs[13496]: [quorum] crit: quorum_initialize failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [status] crit: cpg_leave failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [status] crit: cpg_dispatch failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [dcdb] crit: cpg_leave failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [dcdb] crit: cpg_dispatch failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [quorum] crit: quorum_dispatch failed: 2
Aug 24 17:40:08 prox1 pmxcfs[13496]: [confdb] crit: cmap_dispatch failed: 2
Aug 24 17:40:08 prox1 corosync-qdevice[13488]: Lost connection with heuristics worker
Aug 24 17:35:08 prox1 pmxcfs[825]: [confdb] crit: cmap_finalize failed: 9
Aug 24 17:35:08 prox1 pmxcfs[825]: [confdb] crit: cmap_track_delete version failed: 9
Aug 24 17:35:08 prox1 pmxcfs[825]: [confdb] crit: cmap_track_delete nodelist failed: 9
Aug 24 17:35:08 prox1 pmxcfs[825]: [quorum] crit: quorum_finalize failed: 9
Aug 24 17:35:06 prox1 pmxcfs[825]: [status] crit: can't initialize service
Aug 24 17:35:06 prox1 pmxcfs[825]: [status] crit: cpg_initialize failed: 2

Aug 24 17:41:10 prox2 pmxcfs[12156]: [status] crit: can't initialize service
Aug 24 17:41:10 prox2 pmxcfs[12156]: [status] crit: cpg_initialize failed: 2
Aug 24 17:41:10 prox2 pmxcfs[12156]: [dcdb] crit: can't initialize service
Aug 24 17:41:10 prox2 pmxcfs[12156]: [dcdb] crit: cpg_initialize failed: 2
Aug 24 17:41:10 prox2 pmxcfs[12156]: [confdb] crit: can't initialize service
Aug 24 17:41:10 prox2 pmxcfs[12156]: [confdb] crit: cmap_initialize failed: 2
Aug 24 17:41:10 prox2 pmxcfs[12156]: [quorum] crit: can't initialize service
Aug 24 17:41:10 prox2 pmxcfs[12156]: [quorum] crit: quorum_initialize failed: 2
Aug 24 17:41:09 prox2 pmxcfs[12156]: [status] crit: cpg_leave failed: 2
Aug 24 17:41:09 prox2 pmxcfs[12156]: [status] crit: cpg_dispatch failed: 2
Aug 24 17:41:09 prox2 pmxcfs[12156]: [dcdb] crit: cpg_leave failed: 2
Aug 24 17:41:09 prox2 pmxcfs[12156]: [dcdb] crit: cpg_dispatch failed: 2
Aug 24 17:41:09 prox2 pmxcfs[12156]: [quorum] crit: quorum_dispatch failed: 2
Aug 24 17:41:09 prox2 pmxcfs[12156]: [confdb] crit: cmap_dispatch failed: 2
Aug 24 17:41:09 prox2 corosync-qdevice[12241]: Lost connection with heuristics worker
Aug 24 17:36:25 prox2 pmxcfs[12156]: [status] crit: can't initialize service
Aug 24 17:36:25 prox2 pmxcfs[12156]: [status] crit: cpg_initialize failed: 2
Aug 24 17:36:25 prox2 pmxcfs[12156]: [dcdb] crit: can't initialize service
Aug 24 17:36:25 prox2 pmxcfs[12156]: [dcdb] crit: cpg_initialize failed: 2
Aug 24 17:36:25 prox2 pmxcfs[12156]: [confdb] crit: can't initialize service
Aug 24 17:36:25 prox2 pmxcfs[12156]: [confdb] crit: cmap_initialize failed: 2
Aug 24 17:36:25 prox2 pmxcfs[12156]: [quorum] crit: can't initialize service
Aug 24 17:36:25 prox2 pmxcfs[12156]: [quorum] crit: quorum_initialize failed: 2
 

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!

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!