Search results

i'm totally noob on ipv6. But, based on your log of pfsense, is forwad rules applied ?

Mybe check yours servers host logs....

https://forums.debian.net/viewtopic.php?t=156410

zfs = RAID RAID = metadatas zpool get = RAW additionned disk capacity ofd the raid. du & zfs list/get = usable disk capacity ( iin the raid) GUI zpool report = zpool get

You've 2 hardware with the same BUG. Maybe check for BIOS upgrade ? This is smelling a firmware bug. You're using consumers SSDs.... Maybe forget ZFS, and only use lvm on this kind of configuration

Is it a personnal conf? Professional => Never use backing server on Virtual host. Personnal => Yes you can. But you can too install it on physical pve node, they doesn't listen the same port. "how can I grant access to Proxmox to access all those VM's to backup then?" Begun by a try, check...

check your dmesg output for some BUG / seg fault error

drop conf here: - network of 2 haproxy - keepalive

vérifiez les fondamentaux du réseau .... Vous avez besoin d'un routeur qui connaît votre réseau pour y accéder sans mascarade. You need that our external host know routing way for your vm network.

" post-up iptables -t nat -A POSTROUTING -s '10.0.0.0/24' -o enp31s0 -j MASQUERADE post-down iptables -t nat -D POSTROUTING -s '10.0.0.0/24' -o enp31s0 -j MASQUERADE " Try with converting yours iptables rules into a nftables rules. Proxmox doesn't use iptables natively. They...

Hey, Thanks for your dmesg file. Open -it, and search in this key: 1125.098434 At this time boot, you gonna found seg fault error. 2 thinks: - Reboot on previous running kernel. If he boot, go to dmesg, and do the same search with keywords: "segfault" and "BUG". If no entry with them, update...

hum .... this is xaclty that mapped device do ? :'p

OK, hi again, i've not really more idea, but go investiguate... Network thinks: - Is you PVE hosts with problem have maybe a duplicated IP by another VM/hardware on the same network. - Same thinks with MAC @. Firewall/ SecureLogin thinks: - Did you have done any specific changes on FW of...

OK - Sorry, was onjly able to help you diagnose the source problem with aggregation, when this duplicated @ mas error in your log file come. I've not tested with lacp, no switch lv2 to home ^^

sry, haven't more idea @ this moment :/

Did you have installed on yours guests the guest agent ? This is a needed prerequisites for hotpluging. I think you've saw this documentation Proxmox: https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) But, you only have the manipulation for pve 4.5 and older. Check the real...

Don't forguet to update yours masquerading rules for the updated network name. For your routing problem: 1 Deactivate your enp31s0 gateway. Make it on your vmbr1 declaration. 2 Apply configuration 3 Check routing table (ip -c r) 4 modify your iptables rule for masquerade to vmbr1 interface...

OK. The first reason for my question is i found the vm import tool so hard to use, with frequents fails like yours. My solution used in professional environnement (40TBs VMs import from another production site): Take hand via ssh on your(s) vmware datastore. Then, use this tool...

OK :) If you do not plan to use ZFS FS, you're good. Proxmox is extremely flexible for hardware. But technologies like ZFS need professionnal stuf prerequists. Did you have precises questions for your lab ?

Hey, it's smell a binding problem. Which mode are you using for bonding ? On your GUI, -> PVE Host -> System -> System Log: Check if you haven't messages calling duplicated @mac on your bonded interfaces.If so, try to modify your bonding mode on failove mod, apply your configuration, then retry...