Update:
It seems the problem in my case was that the join process was interrupted somehow.
I powered off the new node and removed it using pvecm delnode <nodename>
After that I reinstalled PVE on it, re-configured it and joined the cluster again.
This time the join worked.
After this I had to...
Good morning,
Short Update:
I found two issues yet.
1) NTP was not in sync on the new host
2) the new node dropped it's network configuration (both KNET rings offline).
Found it out by restarting corosync on the new node and running: grep corosync /var/log/syslog on the node
After it...
Good morning,
I am experiencing the same issue (local certificate does not exist) but have not found the issue yet.
Can anyone give a hint on this?
Best regards,
Mike
I tried online migration again, the journal just says:
Nov 22 13:48:51 node0 qm[7294]: <root@pam> starting task UPID:node0:00001C7F:00021F5F:5DD7D933:qmigrate:107:root@pam:
Nov 22 13:48:52 node0 pmxcfs[2575]: [status] notice: received log
Nov 22 13:48:53 node0 pmxcfs[2575]: [status] notice...
Thank you, the hint with the sysadmin package repos was gold.
The non-subscription sources list was missing.
Now it looks like this:
proxmox-ve: 6.0-2 (running kernel: 5.0.21-5-pve)
pve-manager: 6.0-15 (running version: 6.0-15/52b91481)
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11...
Yes. Here is the full interfaces file of one node -- they are all set up the same way:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please...
I did pveupdate and pveupgrade.
For testing, I removed the "migration: " line from /etc/pve/datacenter.cfg and live migration works now -- but using the slow interface.
It seems there is something wrong with my migration network configuration.
For migration I use the network 10.182.40.96/27
All...
Hi,
I have set up a cluster with three nodes, dedicated corosync network (two rings) and dedicated migration network.
When I login to the cluster nodes, I can reach (ping/ssh) each other using the migration network IP address.
All nodes have one single IP inside the migration network...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.