chrispage1's latest activity
-
Cchrispage1 replied to the thread LXC Boot and vzdump Failures on Ceph RBD after Upgrade: fsconfig() failed ... Can't lookup blockdev (Exit Code 32).I'm still struggling with issues having updated to 9.2.2 from 9.1.9 TASK ERROR: unable to create CT 135 - command 'mkfs.ext4 -O mmp -E 'root_owner=100000:100000' /dev/rbd-pve/24f246db-267a-4a95-9346-2142944edec8/ceph_data/vm-135-disk-0' failed...
-
Cchrispage1 replied to the thread LXC Boot and vzdump Failures on Ceph RBD after Upgrade: fsconfig() failed ... Can't lookup blockdev (Exit Code 32).Hi Dominik, Thanks for your reply! Sure - happy to supply as much information as I can. So this has only begun since the latest update and reboot and can be replicated across nodes. This cluster has gone all the way from PVE 6 with Ceph 16...
-
-
CNo, nothing like that.
-
Cchrispage1 replied to the thread HA state "error" but I cannot see why.It wasn't a result of any issues like this was it - https://forum.proxmox.com/threads/lxc-boot-and-vzdump-failures-on-ceph-rbd-after-upgrade-fsconfig-failed-cant-lookup-blockdev-exit-code-32.183650/ ? Chris.
-
Cchrispage1 replied to the thread [SOLVED] VM firewall rule having no impact?.Ok, so after a little digging around, my Proxmox Firewall service was reporting the below: May 18 16:17:11 pve02 proxmox-firewall[5138]: error updating firewall rules: cannot execute nftables commands May 18 16:17:16 pve02...
-
Cchrispage1 posted the thread LXC Boot and vzdump Failures on Ceph RBD after Upgrade: fsconfig() failed ... Can't lookup blockdev (Exit Code 32) in Proxmox VE: Installation and configuration.Hi, After all of the CVE's and security disclosures over the past week or two, I thought it'd be useful to upgrade my Proxmox nodes to the latest. I recently updated everything to PVE 9 & Ceph 19 and it has been working without fault for a few...
-
Cchrispage1 replied to the thread [SOLVED] VM firewall rule having no impact?.Thanks, although this is still empty: root@pve02:~# iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination...
-
Cchrispage1 replied to the thread [SOLVED] VM firewall rule having no impact?.So nodes upgraded and rebooted, still seems to be a problem. I've cross checked the configurations across all nodes and Host > Firewall settings are exactly the same. I've run iptables -L and they are all empty.
-
Cchrispage1 replied to the thread [SOLVED] VM firewall rule having no impact?.Thanks for your reply! No, iptables is empty. I have been testing from an online port testing tool - still open at the moment. However, if I migrate it to another node, the port correctly appears closed. This server needs updating anyway so I...
-
Cchrispage1 posted the thread [SOLVED] VM firewall rule having no impact? in Proxmox VE: Networking and Firewall.Hi, I'm having a bit of an odd issue. I have a Windows VM within Proxmox. I don't want port 3389 (TCP) to be open so I am trying to close it using firewall rules. At a DC level: Firewall > Options > Firewall > Yes Firewall > Options > EB...
-
CI 'm not sure that hook can work with live migration, as the arp entry need to be set after source vm stop (the arp entry need to be flushed from source horst) and before the resume of the target vm. This is a thing that we should implemented...
