Hi Chryzo
Bit of an interesting one, my curiosity got the better of me. Thanks for posting all that information by the way, was insightful. After having a look into your switch I stumbled upon a few things. Your 462 Mbit/s result caught my eye...
This site is not affiliated with Proxmox (see also the notice in the bottom):
I would strongly suggest to take the ISO from our CDN (as you did):
https://enterprise.proxmox.com/iso/
Interesting thread. We experienced some issues with one cluster beeing upgraded from
7.0.14-17-pve -> 7.0.14-24-pve
One out of 6 cluster members with pve+ceph started experiencing smaller issues at first and major issues after about 1-2 days...
postscreen complaining speaks to the test with VBscript not adhering to the SMTP protocol - see https://www.postfix.org/POSTSCREEN_README.html
-> test with another tool
Hi all,
FYI: Proxmox Offline Mirror 0.8.0 is now available on the pve-test repository at the time of writing. It includes a bigger set of features and improvements that accumulated over the course of this year: new ways to manage snapshots...
Please share the logs from when you got the Protocol error - also consider testing with tools like swaks (or actually sending a mail) - we had a few tools that don't follow SMTP standards on the wire and got similar results, and, speaking from...
Thanks for the update !
Saw that and replied there as well - let's keep the discussion there - https://bugzilla.proxmox.com/show_bug.cgi?id=8172 - as writing the same questions and answers in 2 places does not help
Thanks!
could you please share:
* all log messages from the journal around the time the bridge was set to promisc on
* your network configuration (/etc/network/interfaces) - you can mask individual address if you need to - but try to consistently replace...
fwiw, our problem on the BCM57508 has been largely fixed and/or dormant with 7.0.14-22 and now 7.0.14-23, I don't see any instances of "bnxt_en" in our logs for the last 5 days or so since our last boot, which is a good sign.
-Dave
Das sollte ein temporäres Problem gewesen sein siehe:
https://bugzilla.proxmox.com/show_bug.cgi?id=8158
Bitte Bescheid geben, falls der 404 fehler immer noch passiert - Danke!
Now this host is running 7.0.14-23, seems that the power cycle before booting 7.0.14-22 was the trick. I checked NIC FW settings and tried to boot the new kernel again. The host is member of a 5 node cluster, the other four nodes runs -23 after...
If the firmware was stable under previous kernel versions (7.0.14-19 or earlier), then I'd suggest just try the kernel for 7.0.14-23.
If it didn't work properly with 7.0.14-19 or earlier, then try upgrading firmware.
Also, ensure that RDMA is...
as this thread has been going for a while and we did have at least 2 issues described here - could you please share the logs that show what's failing
(and the affected components and fw versions)
Thanks!
managed to reproduce the issue on a VM (instead of playing around with the naming of the block-devices and numbering, I added a second disk to a single-disk rpool (causing the device-name to change from /dev/sda3 to /dev/sda3_/dev/sdb3) - this...
I updated all 3 nodes to the new released -22 kernel and removed the workaround. they all booted as they should and nics working as intended.
my problem is solved.
Feedback on kernel 7.0.14-22-pve
We experienced instability with previous kernel releases on our Proxmox cluster, particularly after upgrading from 7.0.14-16-pve.
Today we tested 7.0.14-22-pve on one node. After approximately 30 minutes of...