Proxmox VE 8.0 released!
- Thread starter martin
- Start date
no, but for my curiousity it happens only in one out of two s740. have some more oft these and will do further testing. they have differnt bios. maybe there is a relation...
many users have reported bugs with current r8169 driver. (seem to works with dkms, so it's really a driver bug.) Need to wait than proxmox dev backporting it.
i need to withdraw my findings. it's NOT being caused by system/kernel/driver issue but it was fritzbox port accidentally be in green mode 100mbit instead of gbit (cable was plugged to the wrong port). that seems to lead to weird behaviour in packet priority handling.
Hello!!
I've followed the guide to update to 8.0, but it has failed. These are the warnings:
I don't know what to do, know…
I've followed the guide to update to 8.0, but it has failed. These are the warnings:
Code:
Job for pvestatd.service failed.
See "systemctl status pvestatd.service" and "journalctl -xeu pvestatd.service" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Processing triggers for debianutils (5.7-0.4) ...
Processing triggers for libc-bin (2.36-9) ...
Processing triggers for proxmox-backup-file-restore (3.0.1-1) ...
Updating file-restore initramfs...
12101 blocks
Processing triggers for ca-certificates (20230311) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Processing triggers for pve-ha-manager (4.0.2) ...
Errors were encountered while processing:
pve-manager
proxmox-ve
Removing subscription nag from UI...
E: Sub-process /usr/bin/dpkg returned an error code (1)I don't know what to do, know…
Hello!! I'm newbie with this kind of stuff... I don't know what this means this, I apologize...
Best regards!!
Best regards!!
Hello, this is the journalctl output:
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@mrbyte:~# journalctl -xe
It's only a part, I wouldn't like to spam the thread with log messages..
Best regards!!
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@mrbyte:~# journalctl -xe
Code:
Jul 02 15:32:00 mrbyte pvestatd[1043]: ipcc_send_rec[4] failed: Connection refused
Jul 02 15:32:00 mrbyte pvestatd[1043]: status update error: Connection refused
Jul 02 15:32:00 mrbyte pveproxy[1947823]: worker exit
Jul 02 15:32:00 mrbyte pveproxy[1073]: worker 1947823 finished
Jul 02 15:32:00 mrbyte pveproxy[1073]: starting 1 worker(s)
Jul 02 15:32:00 mrbyte pveproxy[1073]: worker 1947828 started
Jul 02 15:32:00 mrbyte pveproxy[1947828]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Jul 02 15:32:00 mrbyte pveproxy[1947824]: worker exit
Jul 02 15:32:00 mrbyte pveproxy[1947825]: worker exit
Jul 02 15:32:00 mrbyte pveproxy[1073]: worker 1947824 finished
Jul 02 15:32:00 mrbyte pveproxy[1073]: starting 1 worker(s)
Jul 02 15:32:00 mrbyte pveproxy[1073]: worker 1947829 started
Jul 02 15:32:00 mrbyte pveproxy[1073]: worker 1947825 finished
Jul 02 15:32:00 mrbyte pveproxy[1073]: starting 1 worker(s)
Jul 02 15:32:00 mrbyte pveproxy[1073]: worker 1947830 started
Jul 02 15:32:00 mrbyte pveproxy[1947829]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Jul 02 15:32:00 mrbyte pveproxy[1947830]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Jul 02 15:32:01 mrbyte cron[1918606]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jul 02 15:32:02 mrbyte pve-firewall[1036]: status update error: Connection refused
Jul 02 15:32:02 mrbyte pvescheduler[1947831]: replication: Connection refused
Jul 02 15:32:02 mrbyte pvescheduler[1947832]: jobs: cfs-lock 'file-jobs_cfg' error: no quorum!It's only a part, I wouldn't like to spam the thread with log messages..
Best regards!!
Maybe buy a subscription with support tickets and ask the Proxmox staff very politely to fix
Removing subscription nag from UI... for you so it does not break the upgrade? At least that's how I interpret it...Hello, thank you very much for your response.
As far I can remember, when I installed Proxmox months ago, I followed one of the thousands blogposts where explain how to remove the popup regarding subscription on login. Do you think that this broke my update?
Thank you very much.
Hi,
Thanks a lot for this procedure. it saved me a lot of time.
I had network disconnection issues. And now my system is working fine.
Thanks again for your help.
Hi!
I'm testing proxmox-pve8, i found the following:
"pve-kernel-6.2.16-3-pve"
"mdadm - v4.2 - 2021-12-30 - Debian 4.2-5"
Results:
At first, I thought it is a systemd bug, but further digging I found it is some kernel bug ( mdadm + udev ).
Linux software-raid (mdadm) is totally broken:
- Promxox host is not possible to shutdown/restart due the "MD loop messages", only power-cut.
Same error (solution was kernel upgrade):
https://forums.rockylinux.org/t/rocky-9-1-system-with-md-devices-never-shuts-down/8534
I'm testing proxmox-pve8, i found the following:
"pve-kernel-6.2.16-3-pve"
"mdadm - v4.2 - 2021-12-30 - Debian 4.2-5"
Results:
At first, I thought it is a systemd bug, but further digging I found it is some kernel bug ( mdadm + udev ).
Linux software-raid (mdadm) is totally broken:
- Promxox host is not possible to shutdown/restart due the "MD loop messages", only power-cut.
Same error (solution was kernel upgrade):
https://forums.rockylinux.org/t/rocky-9-1-system-with-md-devices-never-shuts-down/8534
Another user hit by the r8169 driver issue, I think
Had the issue with an upgraded system; though it went away when it wasn't part of a cluster.
Did a full delete and install, still had the issue.
Took the drive out of the chassis and put it in an older computer, it worked for about 12 hours and then the bug came back.
Had the issue with an upgraded system; though it went away when it wasn't part of a cluster.
Did a full delete and install, still had the issue.
Took the drive out of the chassis and put it in an older computer, it worked for about 12 hours and then the bug came back.
I have tried, it doesn't work. And as far as I can tell Nvidia doesn't plan on supporting 6.x kernels anytime soon.
Hi,
another user did it with success by downloading the packages first: https://forum.proxmox.com/threads/download-pve8-packages-and-continue-upgrade-offline.129804/
Please help a new proxmox user.
Can I have a cluster with VE7.4 and VE8?
I have not done any cluster before but I read the available documentation and it seems doable.
Why am asking this? because I thought of the following given that uptime is critical for me.
I have an VE 7.4 that runs a dozen machines and I want to upgrade to 8.
Let create a cluster with a spare laptop I have available (it has 1tb nvme and 1tb external ssd so more space than I really need).
This new laptop will have VE 8 then migrate all the vz/vm to this laptop,
If everything goes well and without issues
Shutdown the old nuc with the 7.4, format it, install the new version 8
(Nuc has a 512gb nvme and a 512gb ssd)
Join again the cluster and migrate back all the machines from the laptop to the nuc.
If everything goes well and without issues remove the laptop
and have a cluster of only one VE
(In the near future I will buy a 2nd nuc and have a piece of mind)
Am I missing something?
Is there a smarter faster more efficient way?
Any help greatly appreciated
Can I have a cluster with VE7.4 and VE8?
I have not done any cluster before but I read the available documentation and it seems doable.
Why am asking this? because I thought of the following given that uptime is critical for me.
I have an VE 7.4 that runs a dozen machines and I want to upgrade to 8.
Let create a cluster with a spare laptop I have available (it has 1tb nvme and 1tb external ssd so more space than I really need).
This new laptop will have VE 8 then migrate all the vz/vm to this laptop,
If everything goes well and without issues
Shutdown the old nuc with the 7.4, format it, install the new version 8
(Nuc has a 512gb nvme and a 512gb ssd)
Join again the cluster and migrate back all the machines from the laptop to the nuc.
If everything goes well and without issues remove the laptop
and have a cluster of only one VE
(In the near future I will buy a 2nd nuc and have a piece of mind)
Am I missing something?
Is there a smarter faster more efficient way?
Any help greatly appreciated