Search results

I've never tried it on VMware since Proxmox is meant to serve similar purposes and act as a host itself. But I understand you need to experiment with the Proxmox stack somewhere and you might not want to invest time and money in setting up hardware. You should be able to create a secondary...

Hi Alain, Yes, I ended up recreating cluster with /etc/hosts on both nodes as below: 127.0.0.1 localhost.localdomain localhost 192.168.100.1 node1.matrixscience.co.uk node1 192.168.100.2 node2.matrixscience.co.uk node2 My /etc/network/interfaces haven't changes and look exactly as in my...

I've edited: /etc/corosync/corosync.conf /etc/pve/corosync.conf and replaced bond0 (192.168.8.x) addresses with bond1 (192.168.100.x) followed by reboot of both nodes. This doesn't seem to be enough. /etc/pve/.members is still pointing to the old (bond0) addresses and it looks it's not...

Hi all, I have 2 identical nodes on the latest 5.3 version. I'm using storage replication based on a shared zfs pool. IPv4 only network, 2 VLANs but only one is involved in Proxmox routing. Each node has 4 Ethernet ports so I've decided to create 2 bonds: 1. Going to the nearest switch they...

I now have 3 VMs and 1 container set up as per message #4 and #9 above. All VMs suffer from split brain - they can happily boot on either node but run separate data sets which for some reason fail to merge. Interestingly my only container maintains data consistency. Even though it's been moved...

The defunct VM is still up preventing DHCP clients from getting any address assigned: Client side (Win10 Pro): Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with the network address 0x0800272ECE35. The following error occurred: 0x79. Your...

It's also worth mentioning that as a result of the above procedure VM3 ended up in a defunct state. Root partition is mounted read only. Mount / mtab report: /dev/sda1 on / type ext4 (ro,relatime,errors=remount-ro,data=ordered) Nothing can be written to /var/log etc. It has also been assigned...

Hello again Dominic, Right, so I've decided to give it a fresh start: 1. Created Debian 9 VM3 on node1. A single disk on my-zfs-pool created earlier. 2. Logged into VM1 and made a change I can easily track (touch `date "+%Y%m%d%H%M%S"` in /var/tmp/) 3. Set up a replication job to node2 with...

Thanks again Dominic. Again I've tried a failed primary host scenario by unplugging network cable. I've followed steps in the error handling section. Forced quorum, copied config file, started VM, looks ok. I can now see that the replication has been reversed (target changed from node2 to...

Thank you, that's exactly what I was missing. I unplugged network cables from node1 and can now run the same VM (101) on node2 (state from last successfully replication). I've achieved it as below: - pvecm e 1 - created new VM with the same name on node2 with ID 201 - edited...

To be more specific this is my current set up: ---------------------------------------------------------------------------------------------------------------------------------- root@node1:~# zpool status pool: local-zfs-node1 state: ONLINE...

Hi all, I've been trying to set up a 2 node storage replication on the latest 5.3 version for a while to no avail :( I have 2 identical hosts with Proxmox installed on a 1TB virtual disk (split into local and local-LVM). In addition each server has another 4TB virtual disk with no data yet. I...