Search results

You can build yourself the packages, which is a bit clumsy but worked for me. I could send you the .deb files if you trust me, but I would also propose that Proxmox should integrate this upstream.

Firmware on the SAS Controller is up-to-date, tapelib as well. Next I will replace Controller and SAS cable, but i have the feeling this might not be the issue..

May I bump this please? I just replaced my SL3, and the problem persists.

This is exactly what seems weird to me: root@<hostname>:/etc/proxmox-backup# grep yearly prune.cfg |wc -l 0 the complete file: root@<hostname>:/etc/proxmox-backup# cat prune.cfg prune: s-292bacf9-6ca5 keep-daily 30 keep-monthly 6 keep-weekly 8 schedule sat 18:15 store px11...

Hi, I need some clarification about the pruning behaviour of the PBS Server. I usually let the PBS Server do all the pruning to keep permission as restrictive as possible. Essentielly Datastore.Backup is the only Role I need to assign the User. I have a Datastore with 14 daily, 8 weekly and 6...

Is there any ETA when this will make it into a release?

Yeah, i also work around with it through iscsiadm -m node -o delete [..] but it's really really annoying. I know that it#s basically the iscsi vendors wrong implementation, but previously proxmox behaved in a way that it was easy to work around. It would really be good to get a feedback of a...

No worries..

I think this is not related to what's discussed in this Thread.

yeah, but proxmox is not exactly designed for rolling back things. I already thought about just replacing the perl modules manually, but still this is not exactly nice :D

I have community subscriptions but this shouldn't make a difference. Changes in the last Proxmox releases have just broken Multipath support, I don't see why I should need a more expensive subscription. Might be that iSCSI is still in use, but at least Proxmox is treating it legacy'ish? It's...

This urgently needs to get some attention by Proxmox devs. Multipath is basically broken. Yes, I know that iSCSI ist legacy tech, and I avoid it where I can, but still a lot of customers of me, especially those coming from VMWare often bring iSCSI Clusters.

checktime: 1716975297 key: pve1c-<redacted> level: c nextduedate: 2025-05-28 productname: Proxmox VE Community Subscription 1 CPU/year regdate: 2024-05-28 00:00:00 serverid: <redacted> sockets: 1 status: active url: https://www.proxmox.com/en/proxmox-virtual-environment/pricing I have the...

Hi, I have a problem at a customers site: The keys are entered and deemed as "Status: active", but when doing an apt-get update I get: root@px1n1# apt update Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 https://repos.influxdata.com/debian stable InRelease...

No, 6.5 doesn't have the freeze issue.

Any word from the Proxmox Team on this? I am stuck somehow..

@ALFi thanks for that in-depth insights.

Please keep us posted. Over here we had a complette shutdown of the whole cluster after the Update, so all VMs have been "born" on 6.8..

Yeah, i will just reset the Config once this goes upstream. Any estimate?

I am really a little bit surprised that they put this one in the enterprise repos. I thought they were supposed to be tested for extra stability :(