Recent content by sterzy

  1. sterzy

    Error when launching prune command with proxmox-backup-client but work with dry-run option

    opened a bug for this btw: https://bugzilla.proxmox.com/show_bug.cgi?id=6282
  2. sterzy

    Error when launching prune command with proxmox-backup-client but work with dry-run option

    no, that shouldn't make a difference. upid files are created when a task spawns, the api will still spawn a prune task. you can really only try to shorten that file name. and yes `-` seems to get encoded, if you manage to remove those it might help.
  3. sterzy

    Error when launching prune command with proxmox-backup-client but work with dry-run option

    ok well iirc correctly the name of the snapshot is encoded in the upid name, so a) there error message leaks the name unless you also altered it and b) it seems you are using something fairly long here, could you change that to something shorter? alternatively, you can use a shorter user or...
  4. sterzy

    Error when launching prune command with proxmox-backup-client but work with dry-run option

    seems like the temporary upid file here is too long for this to work, you could try to run the prune command with the user directly instead of the token, that would shorten the file name. this is just a workaround though, we'll need to look into creating a proper solution here. ist there a...
  5. sterzy

    Issue after power loss

    Yes, but the error message in question is about memory management (pfn = page frame number) so an issue with RAM is more likely here imo.
  6. sterzy

    Issue after power loss

    Sounds like it given the multiple power outages, but without proper diagnostics it's hard to tell for certain.
  7. sterzy

    Issue after power loss

    You should do a memtest to see if your memory is still working properly.
  8. sterzy

    Important piece is missing from backup

    Well, the roadmap mentions this specifically: The idea being, that this is different from the host backups you can create with proxmox-backup-client already. So yeah, restoring a cluster config and integrating backup and restore on the PVE side will likely be part of this project.
  9. sterzy

    Important piece is missing from backup

    It is on our roadmap already [1]. :) [1]: https://pbs.proxmox.com/wiki/index.php/Roadmap
  10. sterzy

    certificate expiry

    Well there is the self-generated web ui certificate, but those aren't automatically trusted as they are self-signed anyway. So most things in the stack rely on the fingerprints of certificates rather then expiry dates. Ther are also the apt key's but they are valid for ten years or so for each...
  11. sterzy

    Die Frage ist jetzt wer ist schuld, das die E-Mail nicht zugestellt werden konnte?

    Das klingt so, als hättee die IP auf der das PMG läuft keine Reputation die genug für t-online.de ist. Sprich der Mailserver von t-online.de geht davon aus, dass es sich bei dem PMG um ein nicht vertrauenswürdiges System handelt und verweigert die Annahme von Mails. Eventuell kann eine...
  12. sterzy

    NVME Drive Serial "unknown"

    looking through the code superficially, nothing obvious comes up, beside this. however, i'm not an expert on how these serial numbers are supposed to be used, so i don't want to say anything definitive about whether this is an issue on the OEMs side or not. even if that's a faulty...
  13. sterzy

    Update & Risk Management Best Practices? How to ensure real HA between Clusters

    yes mirroring the debian repositories is also possible, the setup wizzard even has options to simplify setting that up. not directly no, apt will simply use the latest packages it finds. however, you can use different medias that you sync with specific snapshots to approximate that [2]. [2]...
  14. sterzy

    Update & Risk Management Best Practices? How to ensure real HA between Clusters

    one option would be to laverage POM and it's snapshots [1]. you could simply take a snapshot, update your dev cluster from it and then once you consider that stable enough use the same snapshot to update your production cluster. [1]: https://pom.proxmox.com/
  15. sterzy

    NVME Drive Serial "unknown"

    hm yeah, this seems to be an exception to an unwritten rule kind of situation. anyway, i send a patch that should fix this [1]. [1]: https://lore.proxmox.com/pve-devel/20250312083819.15379-1-s.sterz@proxmox.com/T/#u