Hi
Looking again for advice on how to address this with the corosync comments listed above regarding using IP addresses vs hostnames.
When we add a node we do not specify a hostname. We simply use the pvecm command to add the node as liste. If it is only adding hostnames in corosync.conf it...
HI
I realize that there is no "master". I simply used that term to reference the node that we always start first and always use to add other nodes too.
The only difference this time is that the normal pvecm add command did not work. Instead, I had to use the --use_ssh flag which has never...
Also the syslog in the master node shows this:
Jul 25 10:43:43 prox1 pveproxy[183638]: Could not verify remote node certificate 'DE:A5:17:A9:69:E6:CA:CD:39:0D:27:1A:EB:60:64:23:AA:0D:31:D6:17:24:A1:FA:4F:E9:34:3C:B2:01:BC:1D' with list of pinned certificates, refreshing cache
Jul 25 10:43:58...
The two files are identical in size except for order on the systems. I've attached both the new node prox21 and the one that was used for the cluster add.
I've clustered different versions with both versions 2 to 3 and 3 to 4. The only issues encountered revolved around doing live migrations between servers of different versions. I've never encountered corosync issues like this before.
This is a major issue as it involves that basic question of...
I recently built 8 additional nodes (licensed) to add to our existing (licensed) cluster. When trying to add the new nodes which were built using proxmox 5 i received the following message:
Login succeeded.
Request addition of this node
Remote side is not able to use API for Cluster join...
I spent several days trying to work out a solution to the issue but the bottom line is that the full communication within the pve-cluster was broken. Once an attempt was made to communicate between nodes (after an individual node restart) the node was locked with the others. This indicates to...
Your best option here is to skip the attempt to install via usb. I have servers which do not have dvd/cd drives and ran into the same issue. I tried multiple usb creation efforts of which zero were effective. The only time I've had a usb installer actually work is when i used it on a system...
There is some additional information in the first post here:
https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.4
Regarding if you make the mistake of using the GUI instead of the CLI. That information may be of help but use with caution.
You...
you would probably want to upgrade to 3.4 first to get to a level where higher upgrades are possible.
https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.4
Then you would upgrade to the 4.0 series...
One other noted behavior. I have one node that I can restart at will without any issues. After a fresh reboot. If i stop the pve-cluster and pmxcfs -l, Things work normally on that node. I can start and stop VM's without issue, vnc works as well as the freshly started vm.
If i reboot...
Its not just that node alone or only that service in the cluster. During the daily daemon sweep cron each node attempted restart pveproxy. This failed with the syslog listed below.
I now have no access to any of the gui's on any node.
Mar 24 06:25:01 prox3 systemd[1]: Stopping PVE API Proxy...
I have a cluster that has been running for a few months. We recently purchased the enterprise licenses and began to walk through the upgrade of all 10 servers. i was on server #9 when I ran into an issue following a reboot.
When the server rebooted I noticed the cluster gui (which is running...
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.