apt

  1. M

    [SOLVED] dpkg error code (1): Too many Errors while upgrading to PVE 7

    Hi everyone, I recently 'reactivated' my old server and booted up into proxmox. I then wanted to upgrade to the newest version, so I added the needed depositories and followed the steps on the documentation. However, after some time, the process got stuck while running dpkg (I don't have the...
  2. E

    [SOLVED] APT Error "The key in the keyring /etc/apt/trusted.gpg are ignored as the file has unsupported filetype" while trying to update to 7.2/3

    Thats all... i got this error while trying to update my pve, doing 'apt-get update', already in 7.1v. Im a "newbie" so tell me what do you need to see more info, ill be waiting for anwsers. Thanks
  3. K

    [SOLVED] Failing kernel upgrade

    I tried running some updates on my server like I do a lot but for some reason this time it completely broke my apt. The latest 5.15 kernel just won't install and I've tried everything that I could find online to fix it. Only thing left that I can do is delete old kernels that are still installed...
  4. Z

    [SOLVED] Is apt autoremove safe

    Yes it is a really basic question - however I have some a small anxiety with autoremove. Yes I have tested on a test platform and that works perfectly, however is there anything that anyone would suggest just incase as a precautionary step? EDIT: Sorry, this is wrong thread, should be under...
  5. B

    pve-qemu-kvm_6.1.1-2_amd64.deb error

    SOLVED by #2. Standard CE PVE install (3 months old - currently v7.1-10) - This morning my usual apt upgrade failed with below snippet. dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/pve-qemu-kvm_6.1.1-2_amd64.deb' (size=26425464) member 'data.tar': lzma error...
  6. J

    python3-ceph-common repo installed and can not be removed

    I converted from no-subscription to a community license but now I have a configuration issue. python3-ceph-common is now orphaned in my apt repo and I can not remove it because of many dependancies. Does anyone else have this issue or a suggestion for fixing it? Jason
  7. B

    download.proxmox.com certificate issue

    hello, can you explain, why PVE 7.1-4 can't apt into http repos? if i set https repos like: deb https://download.proxmox.com/debian/pve bullseye pve-no-subscription it requires authorization, which i can't provide. from another side, if i set http repo, apt gives me this answer: Err:1...
  8. R

    Upgrading from 6 to 7, can't run apt update (NO_PUBKEY errors)

    Since I upgraded from 6 to 7 I can no longer run 'apt update'. I have tried all the steps from the upgrade guide but can't get the error fixed. Any idea how I can fix the error? Here are some data from the Proxmox server: result of apt update: Hit:1 https://download.docker.com/linux/debian...
  9. W

    APT not working due to certificate singing

    Hello everyone, I have recently installed proxmox and installed some VMs. When I try to update proxmox or any Linux VM, APT refuses to download or install any packages due to certificate signing I tried many solutions such as adding enterprise key and removing adding [trusted=yes] to the...
  10. H

    [SOLVED] apt blocked inside VXLAN

    Hi, I'm trying to setup and few vms and containers inside a VXLAN with a gateway to my local network and to the internet. Everything is working except for package updates (I've tried ubuntu, debian and centos). Every VM and container can communicate with each other inside the VLAN. Each VM and...
  11. B

    Weird permission issues with APT in a priviledged LXC container?

    Hi guys! I'm pretty new to Proxmox, but I feel like I've been doing pretty fine. However, I've run into this really weird issue where I cannot use APT to install some packages in my LXC container. I also had some issues earlier with Docker, but I fixed those by turning on nesting. However, now...
  12. P

    [SOLVED] My install has destroyed Perl and prossibly Python

    I checked on my server today and could not access the web GUI which sparked concern. I SSHed in and tried to run sudo pveproxy restart but was greeted with some error similar to this (this specific error was pulled from the syslog) I checked out the file that looked to be the issue...
  13. B

    dpkg: warning: files list file for package

    When I use apt, it will prompt the following information for example apt install lrzsz root@pve:~# apt-get install lrzsz Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: minicom The following NEW packages will be installed...
  14. Y

    How to prevent automatic apt upgrade during the first boot with cloud init ?

    Hello, I've noticed there is an automatic process for upgrading packages during the first boot after cloud init Installation (Debian or Ubuntu for example). Do you know any simple command or the best way to prevent or cancel this process ? Regards YAGA
  15. L

    Probleme mit base-files nach Neustart

    Liebe Community, nach knapp 150 Tagen habe ich meinen Proxmox-Host neugestartet. Zuvor gab es keine Probleme mit den Befehlen apt update und apt upgrade. Nach dem Neustart ließen sich keine Pakete mehr installieren und das Host-System nicht mehr updaten: root@vhost:~# apt update OK:1...
  16. J

    update-grub hanging

    I'm unable to apply updates on my Proxmox server. Currently running: Linux pve 5.0.21-1-pve #1 SMP PVE 5.0.21-2 (Wed, 28 Aug 2019 15:12:18 +0200) x86_64 GNU/Linux Attempts to apply updates fail as follow: root@pve:/boot/grub# apt update Hit:1 http://download.proxmox.com/debian buster InRelease...
  17. D

    [SOLVED] Enterprise Repo Only Works for 1 Run

    I have two clusters, one with 7 nodes and one with 12 nodes. Every host in both clusters has this problem and all 19 hosts have a community edition ProxMox license/subscription attached to them. The first apt update will always fail like below. However, once I run `pvesubscription update`...
  18. G

    PVE 4.4 to 5.x upgrade problem

    I am upgrading our cluster, node by node from PVE 4.4 to 5 following the wiki: https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0 Several nodes upgraded perfectly, however on one node I get the following errors: # apt-get dist-upgrade Reading package lists... Done Building dependency tree...
  19. Z

    [SOLVED] Installation completely broken

    Hi! I was using proxmox normally until i did a reboot and after that the installation seems completely broken. The first sympton was the pve-manager, that wasn't listening on 8006 port. To summarize, that's the situation right now: $ apt update $ apt upgrade Reading package lists... Done...
  20. grin

    [SOLVED] update from jessie fail: gnutls_handshake() failed: Public key signature verification has failed.

    I'm opening this issue here to actually document the solution. Upgrading from jessie to stretch, or actually from older to newer may result a non-working https repo which fail the certificate verification. The problem occurs when there was either no way to perform a dist-upgrade first, or...