Search results for query: apt upgrade

Did you reboot the node after the upgrade? Otherwise, can you post your network configuration? cat /etc/network/interfaces cat /etc/network/interfaces.d/sdn ip a Plus the config of a VM that isn't working? qm config <VMID>

I am trying to upgrade the proxmox, but I am getting the error mesage: Starting system upgrade: apt-get dist-upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. But everytime that I run the command 'dpkg --configure -a' the computer simple...

Confirm this problem mounting a rw volume as a ro=1 mp after the most recent apt-get full-upgrade No documentation about the "Enable idmapped mounts" is provided and the syntax given here doesn't work. Starting the container with debug results in lxc-start 108 20260208150732.185 DEBUG utils...

I've ran into the same problem, took me a while trying to figure out what the problem was until I found this thread. Downgrading pve-container to 6.0.18 resolved it for me, thanks. Will hold off updating my proxmox nodes until an updated version of pve-container is available with a fix.

When I click the upgrade button inside updates I get: Starting system upgrade: apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer...

I have attached screenshots of what the repositories look like. When I run apt update && apt dist-upgrade I get: Ign:1 http://security.debian.org buster/updates InRelease Err:2 http://security.debian.org buster/updates Release 404 Not Found [IP: 151.101.194.132 80] Ign:3...

Hello Proxmox community, I have a headless Proxmox server that I just upgraded by running apt dist-upgrade - as usual. One of the upgrades that got installed is the new kernel 6.17.9. After rebooting the system I noticed that it is still running the old kernel 6.17.4-2. I even tried pinning...

I just noticed, that the 6.x repo has been archived, so you have to switch to archive.proxmox.com [0]. After that you can run apt update and apt dist-upgrade and change back to enterprise or download depending on your subscription status. We are currently in the process of updating the...

Did you read through [0]? apt update followed by apt dist-upgrade should do the trick. Remember to make backups before doing anything else. Upgrade Ceph from Nautilus to Octopus before upgrading PVE to 7.x. When upgrading a cluster always do one node at a time. [0]...

no, i do not have a VM/lxc backup and I can not do, because every time I try to do a VM backup I have the same error: Connection failed (Error 500: close (rename) atomic file '/var/log/pve/tasks/active' failed: Permission denied) Please help me

This is exactly what I did. I got a feeling that the installer tries to download an update during installation and then fails, but the error report is far too long and complicated for me to understand. I'm just happy that I don´t have to reinstall my Proxmox server. By the way, for me just...

Hey @Onslow , I should have said, I did upgrade not only on the kernel package, here are the packages that have changed: Start-Date: 2026-02-05 17:10:27 Commandline: apt dist-upgrade -y -qq Install: libzfs7linux:amd64 (2.4.0-pve1, automatic), proxmox-kernel-6.17.9-1-pve-signed:amd64 (6.17.9-1...

Ok I figured it out (or a work around). If you delete the mirror for updates during the installation and then continue as normal, you should be able to login. You'll get an error when you login but edit /etc/apt/sources.list.d/ubuntu.sources and make sure it matches the answer here for Ubuntu...

systemctl edit apt-daily-upgrade.service Then add the following: [Service] ExecStartPre= This prevents it from running the "apt-helper wait-online" command, eliminating the delay and error in the log files.

Running the apt install pve-container=6.0.18 fixed it for me for now but it's a downgrade of the package. So what is the official fix to get the newest container package? I've tried apt dist-upgrade which loaded the newest package but it failed to start my containers so had to revert back to...

we noticed that it started to queue after the updates below Start-Date: 2026-02-03 08:50:06 Commandline: apt upgrade Upgrade: pmg-docs:amd64 (9.0.4, 9.0.5), libmime-tools-perl:amd64 (5.515-1, 5.515-1+pmg1), pmg-api:amd64 (9.0.3, 9.0.4), proxmox-backup-client:amd64 (4.1.1-1, 4.1.2-1)...

I also just got hit and had to revert, hopefully they will fix it in the near future

...use the GUI. It will run all the right commands and clean up for you. otherwise, use the dist-upgrade recommendation. I have inflicted much self pain after accidentally running apt upgrade myself and wondering why the versions for everything were all funky and pve was not behaving as expected.

Also, I just tested and if I have a 9.0 server setup this way and I and I upgrade using apt-get update apt-get upgrade apt update apt dist-upgrade This gets me to 9.1.5 and my servers continue to work fine after this. This seems to only be an issue with a fresh install of 9.1

Don't: https://lists.proxmox.com/pipermail/pve-devel/2025-March/068874.html As for the issue itself: https://bugzilla.proxmox.com/show_bug.cgi?id=7271