Change cluster node IP in Proxmox Rumi, March 4, 2020 To update the present cluster host proxmox following files need to be updated: /etc/network/interfaces /etc/hosts /etc/pve/corosync.conf (only on one node necessary) However, corosync.conf needs special way to edit the file! Edit corosync.conf Editing the corosync.conf file is not always very straightforward. There are two on each cluster node, one in /etc/pve/corosync.conf and the other in /etc/corosync/corosync.conf. Editing the one in our cluster file system will propagate the changes to the local one, but not vice versa. The configuration will get updated automatically as soon as the file changes. This means changes which can be integrated in a running corosync will take effect immediately. So you should always make a copy and edit that instead, to avoid triggering some unwanted changes by an in-between safe. cp /etc/pve/corosync.conf /etc/pve/corosync.conf.new Then open the config file with your favorite editor, nano and vim.tiny are preinstalled on any Proxmox VE node for example. Always increment the config_version number on configuration changes, omitting this can lead to problems. After making the necessary changes create another copy of the current working configuration file. This serves as a backup if the new configuration fails to apply or makes problems in other ways. cp /etc/pve/corosync.conf /etc/pve/corosync.conf.bak Then move the new configuration file over the old one: mv /etc/pve/corosync.conf.new /etc/pve/corosync.conf You may check with the commands systemctl status corosync journalctl -b -u corosync If the change could be applied automatically. If not you may have to restart the corosync service via: systemctl restart corosync Src: https://forum.proxmox.com/threads/change-cluster-nodes-ip-addresses.33406/ https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_configuration Related Administrations Configurations (Linux) Proxmox Proxmox
Create Jellyfin CDN using Nginx March 20, 2024March 23, 2024 user www-data; worker_processes auto; pid /run/nginx.pid; include /etc/nginx/modules-enabled/*.conf; events { worker_connections 768; # multi_accept on; } http { ## # Basic Settings ## sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048; # server_tokens off; # server_names_hash_bucket_size 64; # server_name_in_redirect off; include /etc/nginx/mime.types; default_type application/octet-stream; ## # SSL Settings… Read More
Add a New Disk Larger Than 2TB to An Existing Linux December 13, 2019December 11, 2020 I am using fdisk and parted utilities to do this configuration. First list the current partition details using fdisk command as shown. # fdisk -l List Linux Partition Table For the purpose of this article, I am attaching a hard disk of 20GB capacity, which can be followed for disk larger than 2TB as well. Once… Read More
SSH to use two-factor authentication using Google Authenticator on Debian or Ubuntu Server November 19, 2023 A computer running Ubuntu 16.04 LTS or above A phone running Android or iOS A configured SSH connection You should understand the danger of stolen passwords. You don’t need to know what two-factor authentication is and how it works. 🙂 Installing and configuring required packages Start a terminal session and… Read More
This was so helpful! I unfortunately tried to change a nodes IP, but probably didn’t do it in the right order. Ended up having to change the file on the other nodes config file that were still working, and then on the one that wasn’t shut down the corosync service, change the local service file(the one under the corosync folder). I also matched the version ids after the change not sure if that helped. Then I restarted the corosync service, which seemed to make it compare the local one with the one on the cluster since the pve file didn’t match. Reply