Search results

Obviously, Snarky McSnarkbutt? Of course I looked in the forums. Just because I didn't find it doesn't mean I didn't look. Thanks for the link. I was hoping there was something built into the system, not some github scripting hack, but that's good to know.

I backup my guests regularly, but after my little glitch this week, I was wondering (and I've searched) - is there any way to backup the host/node configuration?

@fabian Thanks. I just want to change out the ring0_addr with the new separate network hostnames (move syn from 192.168.100.0/24 to 192.168.102.0/24)... which I will try again later today. Each node shows the second NIC up, and I just checked that omping works with the hostnames, so I think I...

OK, I think I've got it. That last status was what I needed. I'm not sure why it was showing such a newer version, but I set all 4 to the same config on the next highest version and restarted and they connected up. I'm going to work my way through restarting them all to be sure, then tomorrow...

So, I'm seeing this in the logs, which is confusing, because when I look at the corosync.conf files they all say 6. Does this mean if I update all 4 of my nodes with version 9 they might re-sync OK? Jul 11 22:50:14 svr-01 corosync[16928]: [TOTEM ] A new membership (192.168.102.11:260) was...

So... would it be easier to move the guest VM with (from this article) "mv /etc/pve/nodes/node1/qemu-server/100.conf /etc/pve/nodes/node2/" and just delete the node from the cluster, and rejoin?

Ok, following that article, I have node1 back up and can get into the web UI, but it's still isolated... so what's the easy way to get it back into the quorum? It's running the same corosync file as the other 3... I can ssh into the other nodes from node1, and it can ping the corosync NIC on...

I see that on node1 for some reason my /etc/pve directory is empty. I'm trying to follow this advice to get my corosync working, as all of the node1 config seems to have been lost.

I can't seem to get the web interface to come up now on node 1. Both interfaces are up, and I can ping both. PING 192.168.100.11 (192.168.100.11): 56 data bytes 64 bytes from 192.168.100.11: icmp_seq=0 ttl=63 time=0.476 ms 64 bytes from 192.168.100.11: icmp_seq=1 ttl=63 time=0.398 ms ---...

OK, I did get the other 3 back... even though I reverted corosync.conf, they were still trying to use the new interface (which I had unplugged to try to simplify the situation).

should I delete the cluster and recreate it at this point?

I need some help pretty badly. I was following along with this excellent write-up to create a second network for my corosyncing, and I thought it was going pretty well, but now I have all 4 of my nodes completely isolated somehow. I've attached the old and new corosync.conf files, and I've...

Fair enough, I already started looking at that path. I did see a decent walkthough of someone doing this on YouTube, setting up the new network on a new interface, but I didn't see them add any routing rule, which I think this is required, right? I need to brush up on dual-homing...

Also occasionally get this, which causes HA to not be useful. Will try turning off Snooping on the UBNT switch to see if that has a positive effect. "error with cfs lock 'file-replication_cfg': no quorum!"

So, I've read this thread, and the multicast notes and I'm still seeing occasional retransmits. I have a 4 node cluster, all on the same VLAN (and they are the only machines on this VLAN). They all have 10G copper ports onto the sam Ubiquiti USW-XG-16 switch, connected to USG-XG 10G router...

Thank you, Lord, for delivering me!... I would likely not have thought of this, but got me over the hump as well...

That seems to be working, 52% through the move currently.

Ok, I think I figured it out, I created a raw disk instead of qcow, and that seems to have worked... I need to play with it a bit more, but is that the right path to be on? Also, I created a second drive, but could I create a raw drive for the image as well? Thanks.

Note that I've done some testing, and it seems it will let me create a VM with a disk image up to about 400G, but if I try 450G or greater I get the error. The share is 48TB of space with over 75% available.

Let me see.... I'm using Dell BROADCOM 57810S Intel X520-T Dual Port