Recent content by taenzerme

I can confirm it does happen with SCSI Virtio devices, too, and neither do I think it's related to QNAP/Synology. NFS share on FreeNAS showed the same symptoms, unfortunately. Strange thing is: Some Vms (all Debian) do snapshots just fine and some (Debian, too) end up with a corrupted...

I remember on a single node it might be different: 1. Change IP assigned to vmbr0 (Configuration - Network) 2. Edit /etc/pve/cluster.cfg 3. Reboot.

Kevin, welcome! Did you edit all three files: /etc/network/interfaces /etc/hosts /etc/pve/corosync.conf and updated the IP in there AND (important!) updated the version in /etc/pve/corosync.conf? Then do a reboot.

@afrugone ... and I just took 3 snapshots of a Debian VM on NFS w/ qcow2 without any problems. I can't reproduce it in general, that's why I'm asking.

Hi all, Hi David, have you found the reason for the problem? We experienced the same problem with qcow2 on NFS (Synology storages) - but not always. I cloned some VMs and took snapshots without any problems. Yet other Vms crashed and corrupted the filesystem immediately. Best Sebastian

Thanks for the help. Everything worked perfectly. I scp'ed the files to the new hosts after stopping the vms and started all on the new hosts then. Downtime < 30 seconds.

No lxc used at all, so not an issue for me. Do I simply copy the .conf files into the folders in /etc/pve/nodes/? Does PVE recognize them immediately or do I have to restart the new cluster?

Thanks Wolfgang!

Alwin, thanks for the quick response. Storage will be the same, no change here. With "vmid.conf" files you mean the files located in /etc/pve/nodes/xxxxx/qemu-server?

Hello all, I need to "hijack" this thread as I need to change my current 3 node clusters ip addresses, too. Is it really sufficient to update the ips in these files only: /etc/network/interfaces /etc/hosts /etc/pve/corosync.conf Do I have to "update" the version in the totem section? Is...

Hello all, we're running an existing cluster with 3 nodes on 4.4. Current nodes have identical hardware and running vms in production. No local storage, everything on Synology HA NFS. We'd like to add 4 new nodes with different hardware (better in terms of RAM and CPU). The new nodes are...

We found the culprit. On the second virtual firewall (pfSense) pfBlockerNg (an iptables based blocking package) was installed but somehow was broken by the update of pfSense to 2.3.4. I removed the package completely and the connection problems are gone. Just in case some experiences something...

We have been able to narrow it down to some kind of routing problem at least but have not found a solution yet. SSH and SFTP work just fine when using the public IP and connecting to the server externally through NAT. Connecting to the internal IP via VPN results in the aforementioned problem...

Hallo zusammen, wir sind eine kleine Agentur in Bonn und betreiben einen Cluster in einer Colocation. Ich suche einen IT'ler/Admin, der uns vor Ort in unserem Proxmox-Cluster bei der Konfiguration hilft. Wir haben u.a. einige Probleme mit Routing-Themen und bräuchten hier mal fachmännische...

I checked the arp entries on every host. To be honest, I have nothing. It's just SFTP upload/connections failing. Everything else works just fine. All hosts (Debian 8) got the latest updates recently. After that this problem appeared. Any known bugs in OpenSSH lately?