Search results

I see in the logs: network config disabled by system_cfg

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?

Does the sync command run in lxc run on a node or in a container?

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.

# 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...

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...

The archive was restored, but did not start:

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...

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!:)

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

The container was placed from a template. Tell me, how you can find a big sparse file using Linux utilities.

Do you rebuilding the container helped? I have the same problem.

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:

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?

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?

With the loss of nfs storage, the loadavg has grown on all nodes cluster, some nodes have rebooted. Why? Why does a high loadavg rebooted the node?

How to determine if a container is locked? I want to check all containers and identify locked.

Is it possible to execute a command in a container before backups? Сan be using vzdump hook (--script)? I want to execute 2 commands: pct exec $3 -- psql -c \"CHECKPOINT;\"" pct exec $3 -- sync before backups. or for this vzdump hook (--script) is not suitable?

I know that :) got so: #!/bin/bash vmid=$3 if [ "$1" == "backup-start" ]; then echo $vmid >> /root/vzdump-test.log fi

I do not understand PERL, but example vzdump-hook-script.pl in this language. in the example my $phase = shift; my $vmid = shift; How to get vmid in bash?