Recent content by al.semenenko88

  1. pve 6.4 cloud-init doesn't work in ubuntu 22.04

    I see in the logs: network config disabled by system_cfg
  2. pve 6.4 cloud-init doesn't work in ubuntu 22.04

    I have installed cloud-init on kvm debian 11, and it's work. I did the same for Ubuntu 22.04 but it doesn't work And: But the user is not created. And IP didn't change: How to understand what's wrong?
  3. Executing sync in a container sometimes takes a very long time

    Does the sync command run in lxc run on a node or in a container?
  4. 3 Node cluster "permission denied - invalid PVE ticket (401)"

    Your answer helped me too, thanks. ProxMox, so why is this happening? We have a 6.4-6 cluster, the problem has not been resolved yet.
  5. Devuan archive is not restored

    # pct config 110 arch: amd64 cores: 1 hostname: test-devuan memory: 512 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=3A:2D:BC:07:D3:7C,ip=dhcp,tag=555,type=veth ostype: debian rootfs: data:subvol-110-disk-0,size=8G swap: 512 unprivileged: 1 # pct config 110 arch: amd64 cores: 1 hostname...
  6. Devuan archive is not restored

    Perhaps you need a devuan file in the directory /usr/share/lxc/config/. # ls /usr/share/lxc/config/ alpine.common.conf common.conf fedora.userns.conf opensuse.common.conf plamo.userns.conf sparclinux.common.conf ubuntu.lucid.conf alpine.userns.conf common.conf.d...
  7. Devuan archive is not restored

    The archive was restored, but did not start:
  8. Devuan archive is not restored

    proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.65-1-pve: 5.4.65-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 I made lxc from devuan template: # cat...
  9. The backup size is displayed as 391 GB, but the lxc size is 20 GB

    If the container is in the domain AD, then the lastlog is very large and the archive looks large. If you can fix the problem with sparse files, great!:)
  10. The backup size is displayed as 391 GB, but the lxc size is 20 GB

    Thanks, understood! # du -sh /var/log/lastlog 553K /var/log/lastlog # ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 387G May 11 2018 /var/log/lastlog
  11. The backup size is displayed as 391 GB, but the lxc size is 20 GB

    The container was placed from a template. Tell me, how you can find a big sparse file using Linux utilities.
  12. LXC Backup Larger in PBS than in vzdump

    Do you rebuilding the container helped? I have the same problem.
  13. The backup size is displayed as 391 GB, but the lxc size is 20 GB

    Actual container size 20 GB, but its backup 391 GB. 391 GB it is displayed in the web interface, but much less backup is used on the disk. Proxmox VE: Config lxc: Proxmox BS: Partition size for backups (used 93 GB). There is not 1 backup, but more:
  14. With the loss of nfs storage, the LoadAverage has grown on all nodes cluster, some nodes have rebooted. Why?

    Thank you! I don’t use Watchdog, I don’t understand why the reboot happened. Is using the soft option, safe for the backup storage?
  15. Using nfs storage for backups with the soft option

    What is the risk of using the soft option? Risking one backup or all? NFS storage will be connected automatically, or you will need to remount manually? (option soft) What is your advice for a backup storage?


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!