Search results

My bad, indeed. So it seems it's a known issue. Thank you!

Hello, Since I updated to 8.0.9, I have an issue when it comes to backups. I'm backing up to a Proxmox Backup Server but, even though the backup notify is set to "On failure only", I always get an email, even if there's no error present in the backup process. Any clue what might be the cause...

I was referring to the HA maintenance mode, that it would be great to have access to it via GUI. Thank you anyways for the time spent so far. The HA Maintenance mode really helps when updates are to be performed.

Hello @Azunai333 and thank you for the reply. Ok, that fixes the HA stuff. It's actually pretty great, I just wished this option would be available in the GUI, but I guess that'll come at some point. Any clue about the storage issues?

Hello, I'm running a 3-node PVE 8.0.4 cluster and I have the following error when trying to migrate a VM from one host to another: task started by HA resource agent 2023-11-21 07:18:52 use dedicated network address for sending migration traffic (10.41.199.33) 2023-11-21 07:18:52 starting...

Hello, I'm glad to say that everything works fine. I don't think it was a RAID scrub, as the local test using fio worked perfectly. I have no clue what happened.... Still, thank you for your time! I appreciate it!

other means NAS-01 to NAS-02. So I tried: local -> NAS-01 NAS-01 -> local NAs-01 -> NAS-02 NAS-02 -> NAS-02 The speeds are ~110MB/s iSCSI -> NFS was about the same, 110MB/s But, something even weirder: now it works via iSCSI from NAS-02 -> NAS-01 with 800MB/s. This is after I ran the fio (I...

fio --filename img --size=100GB --direct=1 --rw=randrw --bs=64k --numjobs=4 --name=test-01 returns a write speed of 1.8GB/s constantly. The test ran for about 5 minutes. Anyways, since we're talking RAID5 over 4 SSDs, they should be capable of writing way over 100MB/s - you can get to 100MB/s...

Hello, I have a weird issue: I cannot seem to move past the 1 Gbps mark when migrating VM disks to a Synology NAS. The setup: 3 nodes connected to a 100Gbps Mikrotik switch 2 Synology NASes connected to the same Mikrotik switch using 25Gbps each What I tested so far: PVE Node to Synology NAS...

You can get around it by manually editing the file /etc/pve/firewall/cluster.fw and delete the "dc/" prefix from the IPSets or add the "dc/" prefix to Aliases.. At least that's what I did.

Hello, I was trying to set some firewall rules to stop a VM from talking to other VMs but to allow it to reach the internet. What I did: 1. Enabled the firewall at the datacenter level 2. Enabled the firewall on the VM NIC 3. Enable the firewall on the VM 4. Create an IPSet for non local IPs...

Hello, I just want to say that this is quite a big issue, as i locked myself out due to this.... :( Thank you!

Hello @cbourque, I fixed the issue by using an additional link for the corosync cluster. That way, when the ring0 link fails, the cluster is still able to communicate using ring1 (different fiber, different switch, etc) so the node knows that it's not "isolated". The issue with this is that, if...

This was it, actually. I was expecting fencing to throw a message saying something like "I lost connection to the cluster. Rebooting". Thank you.

Hello, This is a bit weird... The infrastructure is looking like this: 3 x HP Servers (CS01/CS02/CS03) connected via: 2 x 100 Gbps Mikrotik switches in an active - passive config 2 x 10 Gbps Mikrotik switches in an active - passive config Today, while performing regular maintenance work, all...

Well, at least for me, it only happened after giving the snapshot a few hours / days. So when you delete the snapshot, I would guess a consolidation happens, and that freezes the machine. Please try to take a snapshot, give it 1-2 days and then remove it.

I'm sorry for the really late reply. I have the same issue no matter what the storage is. I tried with NFS, local and LVM-iSCSI. When taking the snapshot, I did not take a RAM dump. @tanfoglionet, unfortunately I have no info and never got to the bottom of this...

Hello, I'm running Jenkins inside a VM ran on a Proxmox VE 7.1.8. The issue is that when I delete a snapshot, the VM enters a locked state, which in turn stops it from responding to requests. I don't know if this is the normal behavior and, if it is, why is it running this way? In my opinion, a...

I guess that's the way I'll take. Thank you for your help, mate.

Setting the permissions so that a given user can only access a certain directory fixes my issue. I wanted to have separated data, data from Proxmox VE and data from the app, so a developer / a bug in the app won't delete anything Proxmox VE related and vice-versa. In my opinion, I was expecting...