apt-get update doesn't work

indyimaging

Member
Jul 8, 2014
11
0
21
when I try to update with apt-get update I get this error:

E: GPG error: http://security.debian.org wheezy/updates Release: The following signatures were invalid: NODATA 1 NODATA 2

I have verified sources.list and read many articals on GPG keys but can't locate the problem


# cat /etc/apt/sources.list
deb http://http.us.debian.org/debian wheezy main contrib
# deb http://http.de.debian.org/debian wheezy main contrib


# PVE pve-no-subscription repository provided by proxmox.com, NOT recommended for production use
deb http://download.proxmox.com/debian wheezy pve-no-subscription


# security updates
deb http://security.debian.org/ wheezy/updates main contrib




# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
 
Do you have updated the key?
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com <key>
 
I have seen some talk abou this but wouldn't know what <key> to use. Some people with problems like this have errors stating what the <key> is. This is a listing of my keys on that machine:

# apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/9887F95A 2008-10-28
uid Proxmox Release Key <proxmox-release@proxmox.com>
sub 2048g/A87A1B00 2008-10-28


pub 1024D/F18AD6BB 2007-04-18 [expires: 2018-05-04]
uid Antoine Martin <antoine@nagafix.co.uk>
uid [jpeg image of size 4992]
sub 2048g/6E23E963 2007-04-18 [expires: 2018-05-04]


/etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg
------------------------------------------------------------
pub 4096R/473041FA 2010-08-27 [expires: 2018-03-05]
uid Debian Archive Automatic Signing Key (6.0/squeeze) <ftpmaster@debian.org>


/etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg
---------------------------------------------------------
pub 4096R/B98321F9 2010-08-07 [expires: 2017-08-05]
uid Squeeze Stable Release Key <debian-release@lists.debian.org>


/etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg
-----------------------------------------------------------
pub 4096R/46925553 2012-04-27 [expires: 2020-04-25]
uid Debian Archive Automatic Signing Key (7.0/wheezy) <ftpmaster@debian.org>


/etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg
--------------------------------------------------------
pub 4096R/65FFB764 2012-05-08 [expires: 2019-05-07]
uid Wheezy Stable Release Key <debian-release@lists.debian.org>


/etc/apt/trusted.gpg.d//zfsonlinux.gpg
--------------------------------------
pub 1024D/DC0FCB63 2002-01-25
uid Darik Horn <dajhorn@vanadac.com>
uid Darik Horn <darik@bfree.on.ca>
uid Darik Horn <dajhorn@uwaterloo.ca>
sub 2048g/5FDE5931 2002-01-25


pub 2048R/F14AB620 2013-03-21
uid ZFS on Linux <zfs@zfsonlinux.org>
sub 2048R/99685629 2013-03-21


pub 1024D/E88FB510 2005-07-20
uid Ned A. Bass <bass6@llnl.gov>
sub 1024g/EC26AADE 2005-07-20


pub 4096R/F3A23B19 2012-11-03
uid Darik Horn <dajhorn@vanadac.com>
sub 4096R/541B2002 2012-11-03


pub 1024D/A71C1E00 1999-04-25
uid Turbo Fredriksson (Primary email address) <turbo@bayour.com>
uid Turbo Fredriksson (Debian GNU/Linux) <turbo@debian.org>
uid Turbo Fredriksson (Maine Coon Breeding) <turbo@dagdrivarn.se>
uid [jpeg image of size 5344]
uid Turbo Fredriksson (Main Address) <turbo@bayour.com>
sub 1024g/A3E7EAA9 1999-04-25
 
No, with this command you update your GPG key. So the error message should gone away. You haven't postet the real output (E: GPG error: http://security.debian.org wheezy/updates Release: The following signatures were invalid: NODATA 1 NODATA 2) So i only have fillt in something like "key" ;)

add here your IDs in from the errrormessage:

Example:
Code:
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 0C5A2783
 
I hate to say that it was a firewall issue. I have multiple internet providers and switched to a different gateway and then it started working. A needed port must have been blocked in the other one. Thanks fireon.

It did break my zfsonlinux installation, and I had to remove and re-install that and then import the zfs volume, but all is healthy again.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!