Proxmox VE Enterprise repos: why/needed?

proxbear

New Member
Apr 25, 2020
20
1
3
46
Hello,

I'm quite new to ProxMox and of course didn't read anything, just installed the whole thing and had hard time to bring everything running, after switching from FreeNAS :) .

Now, after a few quite critical almost-showstoppers (like corrupted VMs, cutting me off with bond-config, cron.d vs. crontab -e headaches etc.), I'm starting to realize more stuff slowly: there is a subscription model and there are some not-Debian sources available.

Question: why are there the Proxmox-VE sources (as mentioned under https://pve.proxmox.com/wiki/Package_Repositories) available? Are those needed? Currently, I don't seem to have configured those:

Code:
root@prox:~# cat /etc/apt/sources.list
deb http://ftp.ch.debian.org/debian buster main contrib

deb http://ftp.ch.debian.org/debian buster-updates main contrib

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

- and -

Code:
root@prox:~# ls -f /etc/apt/sources.list.d/
.  ..

I.e. I have no "pve-no-subscription" entries I could see anywhere.

What I'm missing? Do I need those sources? What will be better when having them with the subscription?

I'm running it privately at home, i.e. no HA cluster / more nodes / anything like that. All I need is a pretty stable solid ZFS / Hypervisor platform.

Thank you,
Andrej
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,927
892
163
South Tyrol/Italy
shop.maurer-it.com
What I'm missing? Do I need those sources? What will be better when having them with the subscription?

See https://forum.proxmox.com/threads/p...ptions-and-why-everybody-should-buy-one.9244/
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_enterprise_repo

You get a more stable experience, and depending on the subscription level you get also enterprise support.
Additionally to that, you support the development, feature and bug fixing of the Products like "Proxmox VE" or "Proxmox Mail Gateway", which is normally also in the interest of users.

are some not-Debian sources available.

Proxmox VE bases on Debian, to provide a known experience and the whole additional world of Debian packages.
But all for Proxmox VE and thus virtualization, containers, clustering and the whole management stack is shipped through repositories from our infrastructure: download.proxmox.com

You should get the most stable one available and have one configured, pve-enterprise is enabled by default for enterprise class production systems. If you cannot or do not want to afford a subscription to accessing it it's naturally fine too, just configure the pve-no-subscription or if you run a test system the pvetest repository.
 

proxbear

New Member
Apr 25, 2020
20
1
3
46
Thank you; one more question: currently, I see no pve-specific sources: is something missing from the Proxmox functionality? E.g. is there something in the paid/unpaid pve-repos, which is currently not covered by the package-sources I already listed here?
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,927
892
163
South Tyrol/Italy
shop.maurer-it.com
Thank you; one more question: currently, I see no pve-specific sources: is something missing from the Proxmox functionality? E.g. is there something in the paid/unpaid pve-repos, which is currently not covered by the package-sources I already listed here?

Yes you are missing out on important updates, fixing bugs and bringing new features, ... But, note that our Enterprise repository doesn't has extra features not available in the non-subscription ones. The packages there are just more stable, a new package will always go through: Our internal test repo -> public pvetest -> public pve-no-subscription -> pve-enterprise.

So please add a Proxmox VE repository you have access to from https://pve.proxmox.com/wiki/Package_Repositories , i.e., add the repository line to either /etc/apt/sources.list or to a /etc/apt/sources.list.d/NAME.list file (NAME can be anything, just has to end with .list),

The Package Repository wiki article always shows the whole sources list, Debian + Proxmox VE ones, so you can also just select that from the desired repository and use it for /etc/apt/sources.list as a whole.
 
  • Like
Reactions: Stoiko Ivanov

proxbear

New Member
Apr 25, 2020
20
1
3
46
Ok, so I've tested it - and it sucked somehow :(.. It had a problem with "samba-common-bin" package, what I've tried to ignore..

I've added the no-subscription pve repo to the sources, made apt update/upgrade, rebooted: now I can't connect CIFS from the UI.

Remembering the "samba-common-bin" problem, I've tried to fix it:

Code:
root@prox:~# apt install samba-common-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
samba-common-bin is already the newest version (2:4.9.5+dfsg-5+deb10u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up samba-common-bin (2:4.9.5+dfsg-5+deb10u1) ...
Checking smb.conf with testparm
WARNING: Ignoring invalid value '' for parameter 'min protocol'
Load smb config files from /etc/samba/smb.conf
WARNING: Ignoring invalid value '' for parameter 'min protocol'
Error loading services.
dpkg: error processing package samba-common-bin (--configure):
 installed samba-common-bin package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 samba-common-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)

So I've tried to force a reinstall, no luck:

Code:
apt reinstall samba-common-bin
E: Internal Error, No file name for samba-common-bin:amd64

Please, how can I fix it? I see nowhere any useful log entries. Why is he trying to locate the non-existing "samba-common-bin:amd64"?

Please help :eek:
 

proxbear

New Member
Apr 25, 2020
20
1
3
46
I've solved it at the end myself: the error can be seen when executing the post-installation script manually, like this:
Code:
/var/lib/dpkg/info/samba-common-bin.postinst --configure

And in my case it was a misconfiguration in /etc/samba/smb.conf :)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!