apt-get update error with valid subscription

chemi

New Member
Apr 29, 2014
2
0
1
Dear all.

Last Sunday I bought a valid subscription for one of our 3.0 proxmox servers. I had to first install proxmox 3.2 using pve-no-suscription as the system was not able to talk to an https server using apt-get. In any case, the apt-get dist-upgrade went ok and the installation updated my /etc/apt/sources.list.d/pve-enterprise.list to contain:
deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

The point is that the cron is failing to get updates (also the apt-get update in the command line). The output of the apt-get update command is as follows:

Get:1 http://ftp.es.debian.org wheezy Release.gpg [1,672 B]
Get:2 http://ftp.es.debian.org wheezy Release [168 kB]
Hit http://security.debian.org wheezy/updates Release.gpg
Get:3 http://ftp.es.debian.org wheezy/main amd64 Packages [5,843 kB]
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit https://enterprise.proxmox.com wheezy Release.gpg
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit https://enterprise.proxmox.com wheezy Release
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
Get:4 http://ftp.es.debian.org wheezy/contrib amd64 Packages [42.0 kB]
Get:5 http://ftp.es.debian.org wheezy/contrib Translation-en [34.8 kB]
Get:6 http://ftp.es.debian.org wheezy/main Translation-en [3,848 kB]
Fetched 9,938 kB in 2s (3,671 kB/s)
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/Release Unable to find expected entry 'pve-enterprise/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.

The problem seems to be in fetching the pve-enterprise packages.

The point is we have another proxmox 3.2 with a valid subscription that shows no error message on apt-get update with the same content in the pve-enterprise.list file.

I would like to avoid having to reinstall the proxmox VE from the beginning.

Any suggestion?
 
using the enterprise repo on 3.0 does not work, as this feature was introduced in 3.1.

the recommended way is to upgrade from 3.0 to 3.1 (using the pve repository), then you can use the enterprise repo.

but its also working like you did. check your sources.list again, if you can´t figure it out just open a support ticket via https://my.proxmox.com

just to note, direct help to get subscription key problems fixed to get access to the enterprise repo are always without any costs.
 
using the enterprise repo on 3.0 does not work, as this feature was introduced in 3.1.

the recommended way is to upgrade from 3.0 to 3.1 (using the pve repository), then you can use the enterprise repo.

but its also working like you did. check your sources.list again, if you can´t figure it out just open a support ticket via https://my.proxmox.com

just to note, direct help to get subscription key problems fixed to get access to the enterprise repo are always without any costs.

Dear Tom.

Thanks for your reply.

I have the following in my /etc/apt/sources.list:
deb http://ftp.es.debian.org/debian wheezy main contrib

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


In /etc/apt/sources.list.d/pve-enterprise.list:
deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

The content of both files is the same than in the working machine.
In fact, the pveversion -v command output is OK (isn't it?):
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-3 (running version: 3.2-3/38bfef76)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-17-pve: 2.6.32-83
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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-2
libpve-common-perl: 3.0-17
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

Following your advice, I'll open a ticket in my.proxmox.com

Thanks again and best wishes.
 

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!