Issue join cluster

W

willymonkas

New Member
Oct 20, 2022
7
1
3
Hello everybody,

I followed the Proxmox guide to setup a cluster on scaleway (cloud provider).

https://www.scaleway.com/en/docs/tu...e=5&pk_campaign=051219TutoK8s&pk_kwd=Facebook

When i want to create a private network VLAN, i have this message :

command 'ifreload -a' failed: exit code 1

My proxmox VE is on 7.2-11v and i updated/upgraded + i installed ifupdown2

message on shell

root@sd1:/etc/network# ifreload -a
error: cycle found involving iface vlan0 (indegree 1)

Can someone help me please !!
 
Last edited:
could you provide the network interfaces file?
 
fabian said:
could you provide the network interfaces file?
Click to expand...
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
address XX.XX.XX.XX/24
gateway XX.XX.XX.XX
bridge-ports enp1s0
bridge-stp off
bridge-fd 0

auto vlan0
iface vlan0 inet static
address 192.168.1.10/24
vlan-raw-device vlan0
 
Code: 
auto vlan0
iface vlan0 inet static
address 192.168.1.10/24
vlan-raw-device vlan0

that can't work, as it would create a vlan0 device pointing to itself as raw device.. the raw device must be something else (it's also not how it's described in the documentation you linked to!)
 
fabian said:
Code: 
auto vlan0
iface vlan0 inet static
address 192.168.1.10/24
vlan-raw-device vlan0

that can't work, as it would create a vlan0 device pointing to itself as raw device.. the raw device must be something else (it's also not how it's described in the documentation you linked to!)
Click to expand...
It works thx a lot but now i have an other issue haha xD,

"Connection error 596: tls_process_server_certificate: certificate verify failed"
 

Attachments

  • 57118035-C2FC-4242-A2E6-DBAD8BB84BF8.jpeg
    57118035-C2FC-4242-A2E6-DBAD8BB84BF8.jpeg
    133.8 KB · Views: 7
well, that looks to me like one node can't talk to the other one via TLS, which is required for proxying requests from one node to another. did the join work without any warnings/errors?
 
fabian said:
well, that looks to me like one node can't talk to the other one via TLS, which is required for proxying requests from one node to another. did the join work without any warnings/errors?
Click to expand...
No warnings/errors

root@sd1:/etc/pve# cat corosync.conf
logging {
debug: off
to_syslog: yes
}

nodelist {
node {
name: sd1
nodeid: 1
quorum_votes: 1
ring0_addr: 192.168.1.100
}
node {
name: sd2
nodeid: 2
quorum_votes: 1
ring0_addr: 192.168.1.101
}
}

quorum {
provider: corosync_votequorum
}

totem {
cluster_name: PAR13
config_version: 2
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
 
can you connect to both nodes in the browser (directly to their hostname/IP)? what does the certificate info panel say for both?
 
fabian said:
can you connect to both nodes in the browser (directly to their hostname/IP)? what does the certificate info panel say for both?
Click to expand...
I can't reach my second node (added to the cluster) via browser.

- Journal begins at Thu 2022-10-20 11:04:19 CEST, ends at Thu 2022-10-20 14:53:40 CEST. --
Oct 20 14:37:17 sd2 systemd[1]: Starting The Proxmox VE cluster filesystem...
Oct 20 14:37:17 sd2 pmxcfs[650]: [quorum] crit: quorum_initialize failed: 2
Oct 20 14:37:17 sd2 pmxcfs[650]: [quorum] crit: can't initialize service
Oct 20 14:37:17 sd2 pmxcfs[650]: [confdb] crit: cmap_initialize failed: 2
Oct 20 14:37:17 sd2 pmxcfs[650]: [confdb] crit: can't initialize service
Oct 20 14:37:17 sd2 pmxcfs[650]: [dcdb] crit: cpg_initialize failed: 2
Oct 20 14:37:17 sd2 pmxcfs[650]: [dcdb] crit: can't initialize service
Oct 20 14:37:17 sd2 pmxcfs[650]: [status] crit: cpg_initialize failed: 2
Oct 20 14:37:17 sd2 pmxcfs[650]: [status] crit: can't initialize service
Oct 20 14:37:18 sd2 systemd[1]: Started The Proxmox VE cluster filesystem.
Oct 20 14:37:18 sd2 systemd[1]: Starting Corosync Cluster Engine...
Oct 20 14:37:18 sd2 corosync[752]: [MAIN ] Corosync Cluster Engine 3.1.5 starting up
Oct 20 14:37:18 sd2 corosync[752]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf vq>
Oct 20 14:37:18 sd2 corosync[752]: [TOTEM ] Initializing transport (Kronosnet).
Oct 20 14:37:19 sd2 corosync[752]: [TOTEM ] totemknet initialized
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kr>
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync configuration map access [0]
Oct 20 14:37:19 sd2 corosync[752]: [QB ] server name: cmap
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync configuration service [1]
Oct 20 14:37:19 sd2 corosync[752]: [QB ] server name: cfg
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync cluster closed process group service v1>
Oct 20 14:37:19 sd2 corosync[752]: [QB ] server name: cpg
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync profile loading service [4]
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
Oct 20 14:37:19 sd2 corosync[752]: [WD ] Watchdog not enabled by configuration
Oct 20 14:37:19 sd2 corosync[752]: [WD ] resource load_15min missing a recovery key.
Oct 20 14:37:19 sd2 corosync[752]: [WD ] resource memory_used missing a recovery key.
Oct 20 14:37:19 sd2 corosync[752]: [WD ] no resources configured.
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync watchdog service [7]
Oct 20 14:37:19 sd2 corosync[752]: [QUORUM] Using quorum provider corosync_votequorum
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
Oct 20 14:37:19 sd2 corosync[752]: [QB ] server name: votequorum
Oct 20 14:37:19 sd2 corosync[752]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Oct 20 14:37:19 sd2 corosync[752]: [QB ] server name: quorum
Oct 20 14:37:19 sd2 corosync[752]: [TOTEM ] Configuring link 0
Oct 20 14:37:19 sd2 corosync[752]: [TOTEM ] Configured link number 0: local addr: 192.168.1.101, port=5405
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 0)
Oct 20 14:37:19 sd2 systemd[1]: Started Corosync Cluster Engine.
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 1 has no active links
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 1 has no active links
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 1 has no active links
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 0)
Oct 20 14:37:19 sd2 corosync[752]: [KNET ] host: host: 2 has no active links
Oct 20 14:37:19 sd2 corosync[752]: [QUORUM] Sync members[1]: 2
Oct 20 14:37:19 sd2 corosync[752]: [QUORUM] Sync joined[1]: 2
Oct 20 14:37:19 sd2 corosync[752]: [TOTEM ] A new membership (2.a) was formed. Members joined: 2
Oct 20 14:37:19 sd2 corosync[752]: [QUORUM] Members[1]: 2
Oct 20 14:37:19 sd2 corosync[752]: [MAIN ] Completed service synchronization, ready to provide service.
Oct 20 14:37:23 sd2 pmxcfs[650]: [status] notice: update cluster info (cluster name PAR13, version = 2)
Oct 20 14:37:23 sd2 pmxcfs[650]: [dcdb] notice: members: 2/650
Oct 20 14:37:23 sd2 pmxcfs[650]: [dcdb] notice: all data is up to date
Oct 20 14:37:23 sd2 pmxcfs[650]: [status] notice: members: 2/650
Oct 20 14:37:23 sd2 pmxcfs[650]: [status] notice: all data is up to date
 
can you try pvecm updatecerts -f on the node with the non-working GUI?
 
scratch that - what does pvecm status report on both nodes? that looks like the cluster is not working at all..
 
You can try delete the cert in all nodes e update certs again. Unfortunately the forum delete my reference, I don't understood...
 
It was deleted by another moderator as it contained rather dangerous invocations of deleting the root SSH key, which may break some communication like migration traffic.

Clusters are finicky, and a deep understanding of the cluster stack (corosync, kronosnet & pmxcfs) and it's integration into higher level Proxmox VE are often a requirement to give an approach to resolve an issue safely, which normally requires finding out specifics about a setup. Further, most more general advices should be covered in our reference docs: https://pve.proxmox.com/pve-docs/chapter-pvecm.html

We really appreciate any user that wants to try to help others here, but I think that linking to general "one fits all" solutions, suggesting they are a general band-aid, can often be rather unhelpful compared to trying to find out what the actual underlying issue in a specific case is.
 
  • Like
Reactions: Neobin and thiago.limax64
fabian said:
scratch that - what does pvecm status report on both nodes? that looks like the cluster is not working at all..
Click to expand...
you haven't provided this info yet, please do so ^
 
t.lamprecht said:
It was deleted by another moderator as it contained rather dangerous invocations of deleting the root SSH key, which may break some communication like migration traffic.

Clusters are finicky, and a deep understanding of the cluster stack (corosync, kronosnet & pmxcfs) and it's integration into higher level Proxmox VE are often a requirement to give an approach to resolve an issue safely, which normally requires finding out specifics about a setup. Further, most more general advices should be covered in our reference docs: https://pve.proxmox.com/pve-docs/chapter-pvecm.html

We really appreciate any user that wants to try to help others here, but I think that linking to general "one fits all" solutions, suggesting they are a general band-aid, can often be rather unhelpful compared to trying to find out what the actual underlying issue in a specific case is.
Click to expand...
Okay, this procedure was assertive for me but naturally I knew what I was doing and I know a lot about public and private keys in linux. I understand your concern, as not everyone here is an expert. Thanks for the feedback my friend :)
I'm new here and I'm surprised by the high level of interaction you guys have, thank you very much for that.
 
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