pveam update failed - no signature file

LeidenSpain · Dec 21, 2022

Hi,

I had to reinstall proxmox on my home computer, and I find that when I try to update the CT list it doesn't work, I get this error in the log

Code:

2022-12-21 17:01:10 starting update
2022-12-21 17:01:10 start download http://download.proxmox.com/images/aplinfo-pve-7.dat.asc
2022-12-21 17:04:10 download failed: 500 read timeout
2022-12-21 17:04:10 update failed - no signature file '/var/lib/pve-manager/apl-info/pveam-download.proxmox.com.tmp.2450.asc'
2022-12-21 17:04:10 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.asc
2022-12-21 17:04:11 download finished: 200 OK
2022-12-21 17:04:11 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.gz
2022-12-21 17:07:11 download finished: 200 OK
2022-12-21 17:07:11 update failed: unable to unpack '/var/lib/pve-manager/apl-info/pveam-releases.turnkeylinux.org.tmp.2450.gz'
2022-12-21 21:21:16 starting update
2022-12-21 21:21:16 start download http://download.proxmox.com/images/aplinfo-pve-7.dat.asc
2022-12-21 21:24:16 download failed: 500 read timeout
2022-12-21 21:24:16 update failed - no signature file '/var/lib/pve-manager/apl-info/pveam-download.proxmox.com.tmp.44183.asc'
2022-12-21 21:24:16 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.asc
2022-12-21 21:24:17 download finished: 200 OK
2022-12-21 21:24:17 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.gz
2022-12-21 21:27:17 download finished: 200 OK
2022-12-21 21:27:17 update failed: unable to unpack '/var/lib/pve-manager/apl-info/pveam-releases.turnkeylinux.org.tmp.44183.gz'

This is my pveversion

Code:

root@server:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-helper: 7.3-1
pve-kernel-5.15: 7.2-14
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.1-1
proxmox-backup-file-restore: 2.3.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-1
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

I have tried to install proxmox on my laptop, using VirtualBox, and it works perfectly there.

Code:

022-12-21 22:54:47 starting update
2022-12-21 22:54:47 start download http://download.proxmox.com/images/aplinfo-pve-7.dat.asc
2022-12-21 22:54:47 download finished: 200 OK
2022-12-21 22:54:47 start download http://download.proxmox.com/images/aplinfo-pve-7.dat.gz
2022-12-21 22:54:47 download finished: 200 OK
2022-12-21 22:54:47 signature verification: gpgv: Signature made Tue Dec 20 16:04:35 2022 CET
2022-12-21 22:54:47 signature verification: gpgv:                using RSA key 28139A2F830BD68478A1A01FDD4BA3917E23BF59
2022-12-21 22:54:47 signature verification: gpgv: Good signature from "Proxmox Bullseye Release Key <proxmox-release@proxmox.com>"
2022-12-21 22:54:47 update successful
2022-12-21 22:54:47 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.asc
2022-12-21 22:54:48 download finished: 200 OK
2022-12-21 22:54:48 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.gz
2022-12-21 22:54:49 download finished: 200 OK
2022-12-21 22:54:49 signature verification: gpgv: Signature made Fri Dec 16 14:53:59 2022 CET
2022-12-21 22:54:49 signature verification: gpgv:                using RSA key 694CFF26795A29BAE07B4EB585C25E95A16EB94D
2022-12-21 22:54:49 signature verification: gpgv: Good signature from "Turnkey Linux Release Key <release@turnkeylinux.com>"
2022-12-21 22:54:49 update successful

I also have another server in the town house, and if I launch pveam update, it doesn't give me an error

Please can you help me?
I really don't know what's going on, and I don't know what else to look at either because everything seems to be fine (obviously it's not)

Regards,

P.D.:
I've been having this problem since Saturday, so I've already tried about 10 different installations, and the same thing always happens to me on the same machine.
I see that some people after a while have solved themselves, but it is not my case.

fabian · Dec 22, 2022

is there some proxy / man-in-the-middle box / .. on the network path that could interfere? does "curl -v http://download.proxmox.com/images/aplinfo-pve-7.dat.asc" work on the affected host (could you post the output)?

LeidenSpain · Dec 22, 2022

Hi,

As far as I know, there is nothing in between.
My NGINX is a machine in proxmox and I haven't installed it yet.

Code:

root@server:~# curl -v http://download.proxmox.com/images/aplinfo-pve-7.dat.asc
*   Trying 51.91.38.34:80...
* Connected to download.proxmox.com (51.91.38.34) port 80 (#0)
> GET /images/aplinfo-pve-7.dat.asc HTTP/1.1
> Host: download.proxmox.com
> User-Agent: curl/7.74.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx
< Date: Thu, 22 Dec 2022 07:27:17 GMT
< Content-Type: application/octet-stream
< Content-Length: 833
< Last-Modified: Tue, 20 Dec 2022 15:04:39 GMT
< Connection: keep-alive
< ETag: "63a1cf07-341"
< Accept-Ranges: bytes
<
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEKBOaL4ML1oR4oaAf3UujkX4jv1kFAmOhzwMACgkQ3UujkX4j
v1n1uA/+L2b7G73nTyzl07c+Wt9DGklz2HSa2C9KEvO2LAkcCZAfGV+/rIXlswz7
qqLTd43hvSVTjF/RuNjX4xw18k1VGa1LaMawAm58zgJN0TbpgnqyyNMsNxMk9J7w
qKFJNzDTwdga21vIASunIgoW/f/JsKfsgL+MfnehpoqjmT2Z9tyJOi5cqchkz3n6
NIp9oZYVtRFWqmD/K40TPPrzRf6LZsgE7g2MhIYGmSg+8LpjMi80+f6raac8Exy4
Mv/FAOo/exwU4B9x7bNBpcwXDF2q6JdTuQyBtv6f69+LG6O40MhbEazbPV4myWLI
0tcYHTwKFcNfh/+Qrxzf8iFnifyuo3xAnDd2BerfnBFLK3UF8s0stWjk5U1MRyG7
u0YTKC5HinrKjD6h+/HA+9hA/jJtOpl4N2DQTNC049RKSEzyGQ0j7EVn3jb9BQ2n
Ybv+pqEn4G5cZsuqHWgXVQ2KxIS6AqjufDWhxljIBuSa6Y0/q1WNKCkgWecvpHon
a8uglimc/Unj+eWnBIlAqPaF/Q4q+SAotH+vIG+QsoKQpUQTm47MQmcz8Mq2ksll
+Rbff+BU4j29gm0RRVp3F0c0QBfV9ijN7Lsms1eVYkuS8IVvkP3QL7Tk9oc5LPzh
378q5KhXZCxrZjQv8MhECMUAioUqh+IFjbk2DAFTzZ/GQJP2n0U=
=b92B
-----END PGP SIGNATURE-----
* Connection #0 to host download.proxmox.com left intact

fabian · Dec 22, 2022

can you verify there's no proxy configured in /etc/pve/datacenter.cfg ?

LeidenSpain · Dec 22, 2022

Hi,

Only the keyboard configuration:

Code:

keyboard: es

Regards

fabian · Dec 22, 2022

hmm. one last thing to try (this is basically the perl code condensed:

Code:

 perl -e 'use strict; use warnings; use LWP::UserAgent; my $ua = LWP::UserAgent->new; my $req = HTTP::Request->new(GET => "http://download.proxmox.com/images/aplinfo-pve-7.dat.asc"); my $res = $ua->request($req, "/tmp/result"); if ($res->is_success) { print "OK\n"; } else { use Data::Dumper; print Dumper($res), "\n"; };'

it should print just "OK" if it works (downloading the signature file to /tmp/result), and the full response object if not (please copy and post it here in code tags).

LeidenSpain · Dec 22, 2022

Nothing, no OK

Code:

root@server:~#  perl -e 'use strict; use warnings; use LWP::UserAgent; my $ua = LWP::UserAgent->new; my $req = HTTP::Request->new(GET => "http://download.proxmox.com/images/aplinfo-pve-7.dat.asc"); my $res = $ua->request($req, "/tmp/result"); if ($res->is_success) { print "OK\n"; } else { use Data::Dumper; print Dumper($res), "\n"; };'

$VAR1 = bless( {
                 '_headers' => bless( {
                                        'client-date' => 'Thu, 22 Dec 2022 07:56:00 GMT',
                                        'content-type' => 'text/plain',
                                        'client-warning' => 'Internal response',
                                        '::std_case' => {
                                                          'client-date' => 'Client-Date',
                                                          'client-warning' => 'Client-Warning'
                                                        }
                                      }, 'HTTP::Headers' ),
                 '_rc' => 500,
                 '_request' => bless( {
                                        '_uri' => bless( do{\(my $o = 'http://download.proxmox.com/images/aplinfo-pve-7.dat.asc')}, 'URI::http' ),
                                        '_method' => 'GET',
                                        '_headers' => bless( {
                                                               'user-agent' => 'libwww-perl/6.52'
                                                             }, 'HTTP::Headers' ),
                                        '_content' => ''
                                      }, 'HTTP::Request' ),
                 '_content' => 'read timeout at /usr/share/perl5/Net/HTTP/Methods.pm line 268.
',
                 '_msg' => 'read timeout'
               }, 'HTTP::Response' );

fabian · Dec 22, 2022

that's really weird.. it looks like a connection error on your side, even though it works with curl :-/ anything else about the system that is amiss? e.g., journal contents, disk space, ..

LeidenSpain · Dec 22, 2022

It's the same computer I had before, with a 1Tb disk space.

Last week I updated the firmware of my router, and a few years ago, the operator closed ports 80 and 443 for me.

Checked port 80, and if I can access my old server without problems.

I also updated my router firmware last week.
If anything, I'm going to try to mount the operator, to see if it changes something.

LeidenSpain · Dec 22, 2022

Hi team,

Finally I have done what I have mentioned: reconnect the operator's router removing mine, and.....
EVERYTHING HAS BEEN UPDATED WITHOUT PROBLEM

It seems that in the latest version of the firmware they have activated some kind of lock that prevents everything from working correctly.

Really, thank you very much for your help: being able to verify if the problem was on one side or the other has been of great help to me.

What I don't understand is because with the server it gives me an error but with the virtual machine in VirtualBox it works fine.

Regards

LeidenSpain · Dec 22, 2022

Again my router, and again return the problems:

Code:

2022-12-22 22:37:53 starting update
2022-12-22 22:37:53 start download http://download.proxmox.com/images/aplinfo-pve-7.dat.asc
2022-12-22 22:40:54 download failed: 500 read timeout
2022-12-22 22:40:54 update failed - no signature file '/var/lib/pve-manager/apl-info/pveam-download.proxmox.com.tmp.278443.asc'
2022-12-22 22:40:54 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.asc
2022-12-22 22:40:54 download finished: 200 OK
2022-12-22 22:40:54 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.gz
2022-12-22 22:43:55 download finished: 200 OK
2022-12-22 22:43:55 update failed: unable to unpack '/var/lib/pve-manager/apl-info/pveam-releases.turnkeylinux.org.tmp.278443.gz'

Then, the origin of all the problems is clear. But it is a mysterious mystery.

Search

Search

pveam update failed - no signature file

LeidenSpain

New Member

fabian

Proxmox Staff Member

LeidenSpain

New Member

fabian

Proxmox Staff Member

LeidenSpain

New Member

fabian

Proxmox Staff Member

LeidenSpain

New Member

fabian

Proxmox Staff Member

LeidenSpain

New Member

LeidenSpain

New Member

LeidenSpain

New Member