Search results

please post: - pveversion -v - cat /etc/pve/storage.cfg - cat /etc/pve/priv/ceph/ceph-metal.conf - cat /etc/ceph/ceph.conf please censor any sensitive data such as auth keys

okay, so this must be a different issue then! stopping the sync job does work here, FWIW. does the slow down happen at specific groups/snapshots?

it is slated for 19.2.4 upstream, not sure if we a backport on our end before that is planned..

sehr viel hat sich in dem betreffenden code zwischen 6.15 und 6.16 nicht getan.. vielleicht mal ein issue auf https://github.com/acpica/acpica/ aufmachen mit details zur hardware, log messages und betroffenen kernel versionen?

can the two can the two PVE systems talk to eachother? anything visible on the source PVE system (task log, journal)?

could you try booting both ends with the 6.14 kernel? there is a known regression that seems to affect some PBS setups and the 6.17 kernels: https://forum.proxmox.com/threads/super-slow-timeout-and-vm-stuck-while-backing-up-after-updated-to-pve-9-1-1-and-pbs-4-0-20.176444/

das sind mehr oder weniger vanilla upstream == kernel.org kernel. ich schau mal kurz ob sich mit den infos schon was eingrenzen laesst!

the processes inside the container are still unconfined as expected, whereas without that config line they are confined by the container profile: without unconfined (PID 1/systemd of the container): $ cat /proc/135279/attr/current lxc-3336_</var/lib/lxc>//&:lxc-3336_<-var-lib-lxc>:unconfined...

cloning the disk does not care about its contents at all.. is this a physical disk? or iSCSI? or ? please provide more data! could you also post "lvmconfig --typeconfig full | grep -e thin -e zero" and "pveversion -v", thanks!

API endpoints being root only is the default if nothing else is specified. seems like those two "index" endpoints are lacking the permissions attribute, which should be fixed. but like @gyptazy said, the information is already available via other endpoints as well!

could you post `proxmox-backup-manager versions --verbose` for both sides, and the sync task log?

es gibt aktuell einen bug im 6.17er kernel der manche PBS setups betrifft und aehnliche symptome hat: https://forum.proxmox.com/threads/super-slow-timeout-and-vm-stuck-while-backing-up-after-updated-to-pve-9-1-1-and-pbs-4-0-20.176444/page-9#post-823736 falls du auf PBS seite schon auf 4.1 mit...

we will fix it. but if you provide the full chain, then you don't need a fingerprint. if you use a fingerprint, you don't need the full chain.

that is tracked in https://bugzilla.proxmox.com/show_bug.cgi?id=6195

falls du kein ZFS verwendest, koenntest du das ganze mit einem stock 6.17 kernel von https://kernel.ubuntu.com/mainline/v6.17/amd64/ reproduzieren und dann einen bug report im kernel bugzilla aufmachen? falls du es dir antun willst/kannst gerne auch gleich die versionen davor zurueckgehen bis es...

that depends what kind of actions you want to do over PDM. you can give it audit access only, then it will only be able to see things but not change them. if you want to start/stop/.. guests, you need to give it power management privileges on those guests. for migration, you need to give it...

could you please post: - VM config - migration task log - VM start task log on the target node (if one exists) - journalctl for both source and target node covering the full duration of the attempted migration and 2mins before and after

this is a bug in1.0.0, please update to 1.0.1 (via no-subscription). @FloRe could you try restarting "pdm-daily-update-service"? if it still doesn't work afterwards, please open an enterprise support ticket (you can provide sensitive config data there)

do you meet the requirements for PDM enterprise repo access? https://pdm.proxmox.com/docs/faq.html#is-there-a-dedicated-subscription-for-the-proxmox-datacenter-manager

eventuell hilft auch ein system firmware update, falls es eins gibt..