Search results

it's unchecked by default already And as i said erlier backing up log contains strange info about disabled... excluding mount point... Where excluding is disabled and what for? "excluding volume mount point mp0 ('/var/www/files.local') from backup (disabled)"

Files are ignored due to the option vzdump 101 --exclude-path '/var/www/files**' --compress zstd --dumpdir /backups/backup_vm --mode snapshot But my harm is restored mount point and its volume. I don't need that volume to be restored.

Hi, guys! I'm really in stuck with manual https://pve.proxmox.com/pve-docs/vzdump.1.html It says "By default additional mount points besides the Root Disk mount point are not included in backups." But vzdump log says "excluding volume mount point mp0 ('/var/www/files.local') from backup...

Hi. guys. I need Your advice because i'm not experienced with ProxMox. Here You are df -h: rpool 1.6T 128K 1.6T 1% /rpool rpool/ROOT 1.6T 128K 1.6T 1% /rpool/ROOT rpool/data 1.6T 128K 1.6T 1% /rpool/data...

The matter iptables -t nat -A POSTROUTING -s 10.1.1.0/24 -o vmbr0 -j MASQUERADE was in /etc/rc.local and it failed to start normally after reboot. I don't know if exist a way lxc-containers having internal IP access inet using PVE host routing, but we use that approach.

PVE Host already has: cat /proc/sys/net/ipv4/ip_forward returns 1 /etc/sysctl.conf contains net.ipv4.ip_forward=1 I'm in stuck... What's about container itself, cat /proc/sys/net/ipv4/ip_forward returns 1 /etc/sysctl.conf contains commented # net.ipv4.ip_forward=1 But as far as i...

Well, it's real time temporary changing, right? Should i place that somewhere yet for fixing it after reboot?

Would You explain a steps? I'm alone and linux-admin is not accessible ((

Yes, lxc's containers pigs gateway 10.1.1.112 PVE host's config is ip r of PVE host is default via xx.xxx.23.65 dev vmbr0 onlink 10.1.1.0/24 dev vmbr1 proto kernel scope link src 10.1.1.112 10.8.0.0/24 via 10.8.0.2 dev tun0 10.8.0.2 dev tun0 proto kernel scope link src 10.8.0.1...

Changing IP changes nothing.

By the way syslog activity continues May 3 14:09:38 app kernel: [149423.207104] device veth106i0 left promiscuous mode May 3 14:09:38 app kernel: [149423.442296] audit: type=1400 audit(1620032978.603:50): apparmor="STATUS" operation="profile_remove" profile= May 3 14:18:37 app kernel...

uname-a Linux app 5.4.106-1-pve #1 SMP PVE 5.4.106-1 (Fri, 19 Mar 2021 11:08:47 +0100) x86_64 GNU/Linux cat /etc/issue Debian GNU/Linux 10 Need a time to answer about IP. It's productive container.

May 3 13:57:00 app kernel: [148664.916265] vmbr0: port 3(veth106i0) entered blocking state May 3 13:57:00 app kernel: [148664.916315] device veth106i0 entered promiscuous mode ip r of PVE host is default via xx.xxx.23.65 dev vmbr0 onlink 10.1.1.0/24 dev vmbr1 proto kernel scope link src...

Exactly ((( lxc machine can't get inet connection after upgrading to 6.4.4 anymore. Would You advice how to figure out it? Appreciate for help. ip r default via 10.1.1.112 dev eth0 onlink 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.102 pct config 102 arch: amd64 cores: 2 features...

I don't think ProxMox understand the matter of using buffers inside container. For my case it's Oracle DB and it can't be freed without harm. It would be great to have an option for adjusting it in ProxMox GUI. Thnak You.

Hi, guys. Here You are a Summary of PVE host from ProxMox web RAM usage 56.27% (35.28 GiB of 62.70 GiB) Here You are an top results KiB Mem : 65748940 total, 6626628 free, 36904272 used, 22218040 buff/cache I don't undestand what is the sense in Summary, that doesn't show real situation...