Search results

what version of pdm and pve do you use ?

Hi, im Web UI gitbt's den punkt 'remove' unter tape backup -> inventory. Da das tape nicht mehr vorhanden ist wird man wohl das 'force' flag aktivieren müssen um es zu entfernen. Hoffe das hilft!

what exactly do you mean? the patch to configure read threads for tape backup jobs are in since 3.3.5, you may have to adapt your backup jobs though

this looks weird and maybe unrelated, can you post the versions of the pdm and pve here? what user are you logged into with at the pdm ?

the question is why is there a token with that name already? is there something/someone that is using that token? if you really want to clear it, there are 3 possibilities: * you go to the pve ui and delete the token -> every user of that token will not be able to connect anymore * use a...

you can't really "clean" the task logs, since they're not meant to be deleted, rather than simply display the results that exist as soon as the task logs are outside the given timeframe (48h according to your screenshot) they will not be shown there anymore

you can of course open a feature request for this, but no promises that it'll be done (or when) one of the problems in implementing this is that the task logs are saved on the local filesystem on each node, so not easily accessible from the other nodes. And we usually don't do api calls that...

sent a patch now: https://lore.proxmox.com/pve-devel/20251119092634.763388-1-d.csapak@proxmox.com/T/#u

hi, i guess this is an ECC key? in that case the minimum size we check against is 224 not 2048, but the log line has the 2048 bit hardcoded ;) i'll send a patch as it's confusing

i think you misunderstood me: the list is still sorted by name, but the individual entries are wrongly rendered (vmid before name) anyway, thanks for reporting, i sent a patch that should fix it: https://lore.proxmox.com/pve-devel/20251117131945.2148025-1-d.csapak@proxmox.com/T/#u

it's still sorted by name: 108 Arch-Budgie comes before 102 Arch-Cinnamon but the rendering is wrong (vmid before name). I'll look into it

no currently migrations (be it intra or cross cluster) will not use the network to the pdm, but either * the normal cluster migration network (intra cluster migration) * the path the source cluster would take to the ip/name the pdm knows of the target cluster (so the source will resolve the...

You can also opt to only given the Datacenter Manager a token with limited access rights, e.g. audit only. PDM will not be able to *do* anything, but you can still monitor it and get quick access with a link.

the PVEAuthCookie has to be a regular pve ticket for users, not the vncticket. the vncticket has to be a parameter to the vncwebsocket api call (AFAIR)

currently, the websocket connection to the pve api also requires a valid user cookie to be set, and not a token (not sure how exactly you handle authentication in your client/proxy) but this will change soon (since we also need token access for consoles on pdm) see...

proxmox ve (and all current proxmox products) are 100% open source and free, you only ever pay for support, so listing xcp-ng as 'free' (where you have to compile stuff yourself, which is not the case for our products) and not our's is misleading. so adding a '1) free' as a cost would only be...

do you have any sdn configured? can you post the output of pvesh get /nodes/<nodename>/network --type any_bridge --output-format json-pretty of the affected pve remote ? (replace <nodename> with the actual one please ;) )

hi, how does your network setup/config on the pve side look like?

yes, it's not really random, but how exactly it's chosen is currently just an implementation detail, so not guaranteed in your case though, after 4 weeks, there is only one tape left to choose, and from that point on, always the oldest media-set will be outside the retention period

hmm with a 5 week rotation it's probably not possible since the calendar events are calendar based, and things like 'every x weeks' is not really possible maybe there is another way: * have an allocation policy of e.g. everyday at monday 09:00 * have retention policy of 27days (4 weeks minus...