Search results for query: apt upgrade

  1. T

    [SOLVED] PVE 8.4.17 Recover from Crashed Upgrade

    ...systemctl restart pve-cluster (this returns the following error: Failed to get properties: Transport endpoint is not connected) apt clean apt upgrade (it returns me to run the dpkg --configure -a again) So I am stuck in a loop essentially. I have not restarted the system and is vary of...
  2. K

    No web GUI after upgrade from 9.0.11 to 9.1.6

    Hello, I had this issue already when upgrading from 8 to 9. Now it is there again. When I try accessing the GUI I get these errors: Uncaught SyntaxError: missing } after property list proxmoxlib.js:750:2note: { opened at line 42, column 29proxmoxlib.js:42:29 Uncaught TypeError: can't access...
  3. J

    Debian 13 LXC await network timeout

    The workaround "systemctl disable ifupdown-wait-online.service" is working only on older systems (pre-debian-13.1.2). I can see that since 13.1.2 "ifupdown" and "ifupdown2" is installed, on older systems only "ifupdown". The issue is triggered by "apt-daily-upgrade.service".
  4. W

    [SOLVED] Grey question marks at containers, VMs, hosts and storage

    You are right, the docs explicitly recommend apt dist-upgrade in any case. So, to answer your question: Yes, I'm certain I used apt upgrade to install the packages last week, following a habit to only use apt dist-upgrade when it is about a major release upgrade. Probably I have to rethink my...
  5. K

    [SOLVED] Grey question marks at containers, VMs, hosts and storage

    Are you certain, that you used "apt upgrade"? This could have broken some. Always use apt dist-upgrade, otherwise some dependencies could get messed up! See: https://lists.proxmox.com/pipermail/pve-devel/2025-March/068874.html and...
  6. P

    Migration from 8.4 to 9.1 issue: Failed to get cgroup support status

    Hello, I upgraded my VE 8.4 installation to 9.1 using apt dist-upgrade. Before starting I used pve8to9 --full to check if it was all ok: only VM.Monitor warning. After upgraded and reboot, I run pve8to9 --full again, and I received this warning: WARN: Failed to get cgroup support status for CT...
  7. W

    [SOLVED] Grey question marks at containers, VMs, hosts and storage

    ...three HP DL380 Gen 10 hosts. All updates from PVE 6 through 9 always ran flawless, until I updated from 9.0.5 to 9.1.6 via apt update && apt upgrade which made the names of LXC containers and VMs in the web GUI vanish. They as well as hosts and storages show a grey question mark instead...
  8. T

    Running Proxmox for web application server (multiple mysql databases + php)

    ...with 2 votes, the other node 1) where i made a timeshift (rsync'ed hardlinks) backup of the main proxmox host prior to doing 'apt update; apt upgrade' which had weird effects locking me out of Web UI so I rolled back via ssh, and after rebooting i think it was corosync took 1 hour to resync...
  9. fstrankowski

    [SOLVED] Bad display Web UI after upgrade

    Thanks for noticing the small details here :-)
  10. K

    [SOLVED] Bad display Web UI after upgrade

    Perfect :) Like @Impact said, please use apt update && apt dist-upgrade in the future. Please mark this thread as solved by editing the origjnal thread and set the prefix to SOLVED. Cheers ^^
  11. Impact

    [SOLVED] Bad display Web UI after upgrade

    Don't use apt upgrade/apt-get upgrade. Use the GUI, pveupgrade or apt dist-upgrade/apt full-upgrade. Also see docs.
  12. K

    [SOLVED] Bad display Web UI after upgrade

    Yeah, you need to do apt dist-upgrade, apt upgrade is too conservative and does not update all dependencies => Which could lead to such issues. Continue and test again. Send pveversion -v output afterwards. EDIT: Update over webui does perform apt dist-upgrade as well.
  13. B

    [SOLVED] Bad display Web UI after upgrade

    root@PVE-MAISON2:~# pveversion -v proxmox-ve: 9.1.0 (running kernel: 6.14.11-1-pve) pve-manager: 9.0.11 (running version: 9.0.11/3bf5476b8a4699e2) proxmox-kernel-helper: 9.0.4 proxmox-kernel-6.14.11-1-pve-signed: 6.14.11-1 proxmox-kernel-6.14: 6.14.11-1 proxmox-kernel-6.14.8-2-pve-signed...
  14. B

    [SOLVED] Bad display Web UI after upgrade

    root@PVE-MAISON2:~# apt update Hit:1 http://security.debian.org/debian-security trixie-security InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://download.proxmox.com/debian/pve trixie InRelease 9 packages can...
  15. K

    [SOLVED] Bad display Web UI after upgrade

    What happens when you do: apt update apt dist-upgrade Does the install of pve-manager fail? I think apt-upgrade does not update all dependencies.
  16. B

    [SOLVED] Bad display Web UI after upgrade

    ??? i do apt-get update and apt-get upgrade every months !!
  17. R

    Proxmox web UI accessible but shell returns Error 500: close (rename) atomic file....

    Hello, Here is a short feedback regarding this issue. Initial symptoms Web UI accessible Shell access returned: apt upgrade failing with permission errors Error 500: close (rename) atomic file '/var/log/pve/tasks/active' failed: Permission denied journald service failing random...
  18. jsterr

    Graphical Errors on PVE Webui (9.1.6)

    Checkboxes seems to be fixed with new proxmox-widget-toolkit:amd64 (5.1.6, 5.1.7) Start-Date: 2026-02-26 12:03:27 Commandline: apt-get dist-upgrade Upgrade: proxmox-widget-toolkit:amd64 (5.1.6, 5.1.7), corosync:amd64 (3.1.9-pve2, 3.1.10-pve1), libvotequorum8:amd64 (3.1.9-pve2, 3.1.10-pve1)...
  19. S

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    I do want to confirm that downgrading works. Downgrading my PBS server to kernel 6.17.4-2-pve after the upgrade to PBS 4.1.2 with 6.17.9-1-pve let my backups function correctly again. My PVE hosts are running "Virtual Environment 8.4.16". LXC would work but the full VMs would hang on a larger...
  20. B

    cloud-init template für bereitstellung in whmcs

    @LucasKer, Serielle Konsole: Das ist normales Verhalten bei --vga serial0. Die GUI zeigt dann die serielle Konsole statt einer grafischen — da muss man immer erst Enter drücken, damit der Login-Prompt erscheint. Wenn dich das stört, kannst du bei den geklonten VMs (nicht im Template) --vga std...