aaron's latest activity

  • aaron
    I recommend to stick with the soft watchdog. It works well and you avoid any issues due to questionable quality of OOBM hardware and software ;)
  • aaron
    Hast du ein paar Minuten gewartet, nachdem du den Key applied hast? Es braucht die paar Augenblicke bis die neuen Infos an alle Updateserver gepusht wurde. Am besten meldest du dich beim uns im Support https://my.proxmox.com Da können wir uns im...
  • aaron
    aaron replied to the thread PBS hinter Apache2 Reverse Proxy.
    Ich kann nicht mit einer direkten Antwort helfen, aber kann Apache als rpoxy websockets, bzw deine config?? Denn dass connection:upgrade ist der Schritt eine websocket Verbindung aufzubauen.
  • aaron
    aaron replied to the thread Ceph constantly adding PG.
    Interesting. Most likely caused by some changes in the space usage of the pool. Even though the ceph osd pool autoscale-status output posted is useless as it is not formatted as code, I suspect that there is not target_ratio configured for the...
  • aaron
    aaron replied to the thread Ceph constantly adding PG.
    This looks a lot like the autoscaler doing its thing. Was there any config change before all of this? Check the <NODE> → Ceph → Pool menu to see what is configured there. Possible reasons could be that one of the "target_*" options was set. Or...
  • aaron
    aaron replied to the thread Native shared storage.
    If there is no vendor specific storage plugin, you can always use the generic approach: https://pve.proxmox.com/wiki/Multipath
  • aaron
    aaron replied to the thread maps.
    is your Backup Server up to date? Then in the release notes of the Datacenter Manager: https://pdm.proxmox.com/docs/roadmap.html#release-history
  • aaron
    aaron replied to the thread DRS ( Auto-scale of the resource).
    https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_crs_load_balancer available as a full load balancer since Proxmox VE 9.2
  • aaron
    aaron replied to the thread repo certificate mismatch?.
    download.proxmox.com should be accessed via http, not https. Which is reserve to enterprise.proxmox.com as you see in the certs details. The packages themselves are signed via GPG and verified with the key present on the host via the package...