Proxmox VE 6.4 available

Tokamak

New Member
Apr 28, 2021
8
0
1
55
on a hunch - you did not configure the correct repositories - see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories
In my source.list the German version server has been configured during installation

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

# security updates
deb http://security.debian.org buster/updates main contrib
But even after changing it to http://ftp.debian.org and apt clean && apt update there is still nothing to update
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
5,196
684
118
But even after changing it to http://ftp.debian.org and apt clean && apt update there is still nothing to update
as described in the reference documentation I linked: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories

you need to configure a proxmox VE repository (e.g. in /etc/apt/sources.list.d/pve.list) - if you have a subscription the pve-enterprise repo:
Code:
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
if you don't have a subscription use the line for pve-no-subscription
 
  • Like
Reactions: Tokamak and Moayad

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,954
910
163
South Tyrol/Italy
shop.maurer-it.com

ph0x

Active Member
Jul 5, 2020
749
128
43
/dev/null
File restore is some crazy ass feature, thank you very much!
Since you switched from GB to GiB gauges with RAM, would you mind doing the same with disk usage? ;)
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,954
910
163
South Tyrol/Italy
shop.maurer-it.com
Since you switched from GB to GiB gauges with RAM, would you mind doing the same with disk usage? ;)
Hmm, personally I'd not mind doing that, but as dev I'm a bit hesitant do to that for disks, as most vendors use GB (base 10) units on data sheets, so switching there from GB to GiB may seem to some like "Proxmox VE ate my space", as GiB is always lower - e.g., most 1 TB disks are ~ 931 GiB. I keep it in mind though.
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,954
910
163
South Tyrol/Italy
shop.maurer-it.com
is there any risk of upgrading the zfs version? My host ended up getting destroyed from the last upgrade.
Package upgrade is as safe as then, but yes, one should avoid enabling new zpool features when using GRUB to boot from a ZFS root pool. Also, from reading the thread it does not seem that your host got destroyed but that boot got temporarily broken - which was recoverable, you just decided to not do so as you had recent backups anyway. Surely, still a big hassle/PITA, but there was nothing destroyed by simply upgrading, and also no data destroyed by the zpool upgrade directly. I'm stating that just for the case that someone else reads this when experiencing a similar situation, so that they do not think something got destroyed permanently, such setups can be recovered, as my colleagues and other community member helped to do in the linked thread.

hope for any help or comments since Proxmox devs don't seem to care to include courtesy risk notifications before doing things that can break.
But the package update itself did not broke anything, and that is what we rolled out. The problematic zpool upgrade was not done by us, so please do not make it sound like that. If you're unsure how changes to the ZFS pool you boot from play out you can always ask here, as quite a few have done and were saved from such situations.

Note, we take this very seriously, the plan to boot ZFS installations on legacy BIOS systems not directly from ZFS but using the ESP as jump partition to boot GRUB from where finally enacted for the Proxmox VE 6.4 ISO. There we setup GRUB and kernel/initrd on the ESP vfat and let GRUB boot it from there, while the actual ZFS is booted from the real OpenZFS module in the Kernel.

Further, we'll look into extending communication of changes for upgrades where some admin actions, resulting from such an upgrade, may result into issues in certain setups.
 
  • Like
Reactions: DavidAQ and flames

czechsys

Active Member
Nov 18, 2015
236
14
38
as described in the reference documentation I linked: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories

you need to configure a proxmox VE repository (e.g. in /etc/apt/sources.list.d/pve.list) - if you have a subscription the pve-enterprise repo:
Code:
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
if you don't have a subscription use the line for pve-no-subscription
Why you don't use no-sub repo as default finally and remove all such questions once for all?
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,954
910
163
South Tyrol/Italy
shop.maurer-it.com

JeroenLWD

Member
Aug 24, 2016
3
0
21
37
At the moment only filesystems directly on partitions are supported, but we plan on supporting common setups like LVM, ZFS and mdraid in the future.
Lvm support would be very nice, any idea when that is approximately in the planning
 

j.io

Member
Mar 16, 2021
37
3
8
34

ph0x

Active Member
Jul 5, 2020
749
128
43
/dev/null
Hmm, personally I'd not mind doing that, but as dev I'm a bit hesitant do to that for disks, as most vendors use GB (base 10) units on data sheets, so switching there from GB to GiB may seem to some like "Proxmox VE ate my space", as GiB is always lower - e.g., most 1 TB disks are ~ 931 GiB. I keep it in mind though.
I already assumed that this is the reason.
However, in the text area on the top GiB are used, bringing in the difference between text and gauge, which was a reason to change it for the RAM gauge.
Since GB are more common in the storage world, I would then suggest to also use GB in the text area.
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,954
910
163
South Tyrol/Italy
shop.maurer-it.com
However, in the text area on the top GiB are used, bringing in the difference between text and gauge, which was a reason to change it for the RAM gauge.
Since GB are more common in the storage world, I would then suggest to also use GB in the text area.
Good point and true.
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
3,954
910
163
South Tyrol/Italy
shop.maurer-it.com
I couldn't get it to list files on XFS filesystems, on plain partitions.
Should work now with the proxmox-backup-file-restore 1.1.5-3, when XFS is mounted during backup it may refuse to mount on another system by default, so we had to configure specific mount options to tell it that's OK in the file-restore VM.
 
  • Like
Reactions: danielb

kamzata

Active Member
Jan 21, 2011
148
4
38
Venezia - Italy

Port 8006 doesn't answer anymore after upgrade.


Just upgrade to pve-manager/6.4-4/337d6701 (running kernel: 5.4.106-1-pve) from previous release (Enterprise repository) and I'm not more able to connect to the Web Interface on port 8006. I tried to restart the whole server but nothing to do. I also checked journal -b but I cannot see any error related.

What's happened?
 
Last edited:

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
5,196
684
118
Just upgrade to pve-manager/6.4-4/337d6701 (running kernel: 5.4.106-1-pve) from previous release (subscription repository) and I'm not more able to connect to the Web Interface on port 8006. I tried to restart the whole server but nothing to do. I also checked journal -b but I cannot see any error related.

What's happened?
check the journal for messages from pveproxy after a reboot (`journalctl -b -u pveproxy`) - check `ss -tlnp|grep 8006` - if this does not solve the issue please open a new thread with the information from the journal and ss
 

kamzata

Active Member
Jan 21, 2011
148
4
38
Venezia - Italy
check the journal for messages from pveproxy after a reboot (`journalctl -b -u pveproxy`) - check `ss -tlnp|grep 8006` - if this does not solve the issue please open a new thread with the information from the journal and ss
Bash:
$ journalctl -b -u pveproxy
-- Logs begin at Thu 2021-04-29 16:34:25 CEST, end at Thu 2021-04-29 17:49:01 CEST. --
Apr 29 16:34:44 srv001 systemd[1]: Starting PVE API Proxy Server...
Apr 29 16:34:45 srv001 pveproxy[2361]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
Apr 29 16:34:45 srv001 pveproxy[2367]: starting server
Apr 29 16:34:45 srv001 pveproxy[2367]: starting 3 worker(s)
Apr 29 16:34:45 srv001 pveproxy[2367]: worker 2368 started
Apr 29 16:34:45 srv001 pveproxy[2367]: worker 2369 started
Apr 29 16:34:45 srv001 pveproxy[2367]: worker 2370 started
Apr 29 16:34:45 srv001 systemd[1]: Started PVE API Proxy Server.

Bash:
$ ss -tlnp|grep 8006
LISTEN    0         128                   [::]:8006                [::]:*        users:(("pveproxy worker",pid=2370,fd=6),("pveproxy worker",pid=2369,fd=6),("pveproxy worker",pid=2368,fd=6),("pveproxy",pid=2367,fd=6))
 

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!