Recent content by Stoiko Ivanov

You're welcome - glad it worked out so well! Have a nice weekend as well!

the r8169 driver is in-tree - this means it is part of the linux kernel and thus shipped with our kernel package. no need for a dkms package I hope this explains it!

Sorry I misread - the r8168-dkms package really should not be needed anymore - the in-tree r8169 should work with all fitting NICs by now: https://salsa.debian.org/debian/r8168/-/blob/main/debian/README.Debian?ref_type=heads just remove it and try the r8169 driver (of course make sure you can...

try removing the current dkms package - wipe it ... install the new one. I would only do this if you have access to the server physically - or if the r8168 module is not needed for access (meaning if you can reach the server on a NIC, which does not need the out of tree realtek driver...)

It's described a bit further up in the wiki-page you quoted: https://pve.proxmox.com/wiki/Certificate_Management#sysadmin_certs_get_trusted_acme_cert pvenode acme account register account-name mail@example.com I hope this helps...

Check if there is a BIOS/Firmware update for the system - these can help in fixing issues like this one.

not sensibly - the reject here happens during the smtp dialogue - so the mail is never accepted by your system - the sending server needs to deal with this.

for this particular dkms-package we ship a version which contains a fix for it to work with the 6.8 kernel - try installing: r8168-dkms from the proxmox repositories. I hope this helps!

This is currently not part of any installer (the automated installer uses the same backend as the GUI and TUI ones) - so this is something that is better handled after the initial installation (with ansible and similar tools)

Is something else listening on the relevant ports? but it seems more likely related to a permission issue - and nothing in the changelog between those two version indicate that something changed w.r.t. permissions...

yes - the relevant lines from the journal/syslog/mail.log - potentially even the data from the tracking center should be enough ;)

I've seen this error message - and it was always related to something not working with the certificates. (sometimes clients expect a trusted certificate, sometimes a specific one) - I'd suggest to compare the smtp certificate of the new node to the ones from the working ones....

Yes - but unless they have exactly the same traces as yours the issues are usually not related :) new kernels do show various bugs in different pieces of hardware. Upgrading the firmware of components has helped more often than not to make a bug not show up again in my experience - hence the...

hm as far as I can see the issue does not seem related to NFSd? (the traces point to mdraid I/O) In any case - especially with newer hardware - I'd suggest to try upgrading the BIOS (new kernel's sometimes show bugs present in older BIOS versions, that do not show with older kernels) from a...

have you tried using the i40e driver shipped in the 6.8 kernel? - i.e. are there any issues if you just remove the dkms-package? see https://pve.proxmox.com/wiki/Roadmap#8.2-known-issues