Search results

no problem ... root@proxmox:~# qm config 103 agent: 1 boot: c bootdisk: scsi0 cores: 2 description: delete desc ide2: none,media=cdrom memory: 6144 name: TSD net0: virtio=A2:5A:05:AC:24:4A,bridge=vmbr0 numa: 0 ostype: win10 protection: 1 scsi0...

root@proxmox:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve) pve-manager: 6.2-11 (running version: 6.2-11/22fb4983) pve-kernel-5.4: 6.2-5 pve-kernel-helper: 6.2-5 pve-kernel-5.4.55-1-pve: 5.4.55-1 pve-kernel-5.4.44-2-pve: 5.4.44-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync...

After today upgrade root@proxmox:~# pveversion pve-manager/6.2-11/22fb4983 (running kernel: 5.4.55-1-pve) root@proxmox:~# qm start 103 Use of uninitialized value in string ne at /usr/share/perl5/PVE/QemuServer.pm line 1653. root@proxmox:~# qm list VMID NAME STATUS...

I create new cronjob-file in /etc/pve/ and link to /etc/cron.d/ (on every host in cluster)

https://pbs.proxmox.com/wiki/index.php/Roadmap

Question about GC - in this situation (broken fs) GC stop check with ERROR and restart on next minute - my PBS VM slowdown (GC work all time, failed and start again). Maybe config options for restart/notrestart failed GC and email to admins?

I know, but i think fs error on heave load in this case. My test environment - unisocket Xeon E3, 16 Gb RAM, 13 VMs (1 Windows Server + 12 Linux VMs) PBS setup as VM + datastor disk place (as vm image) on NFS share (small Synology NAS) + backup every 10 min :cool:

no, chuck can be missing by different reason, there no question. Question about how to fix GC, which stop after this error

When i forget backup ...110/2020-07-26T19:10:58Z - error exist on other backup with this chuck My fix Find first not affected backup (use verify) and remove all next affected backup index, restart GC and full backup for vm (run automatically on backup job, don`t use dirty-bitmap) Verify slow...

Garbage collect failed with this error again and again TASK ERROR: unable to access chunk 2d3470d651e623c96fcdc0c41b0974736561c69125da3435ec34aa77cbb58406, required by "/backup/pbs/vm/110/2020-07-26T19:10:58Z/drive-scsi0.img.fidx" - update atime failed for chunk...

Again fail with Too many open files after two days I think there leak file descriptor ....

Create new crontab job by hand (as example use disabled backup job from interface PVE) */30 * * * * root vzdump 102 11003 ....... example for half-hour vzdumps

again shutdown and errors from task logging add LimitNOFILE=10240:524288 in /etc/systemd/system/multi-user.target.wants/proxmox-backup-proxy.service and go to test...

Hello On second PBS (replicate from main PBS) i got next error (two times for last day) and web interface is gone for start again need restarting service

I get some problem with offline KVM migration with last update problem code here ... in file /usr/share/perl5/PVE/QemuMigrate.pm with this add check migration failed with next message pveversion -v

Going "Datacenter->Groups" and create group "Admins" next in tab "Permissions" create group permission for path "/" and group "Admins" with roles "Administrator" in tab "Users" create user and select group Admins.

On latest ubuntu you must use upstart config file in /etc/init/ directory ...