@Lone_Wolf
Understood.
No particular reason for the lts. I just started it that way. It's a production server, so my motto is the less the merrier.
Maybe I will give it a shot in some maintenance interval.
@rsmarples
Noted and loved the "appease".
Thank you both, be well.
]]>Other header options really change the code path so it's not so easy, but thankfully the LTS kernels have caught up to those headers now.
]]>Arch devs and dhcpcd developer don't appear to agree on how to solve this.
Switching to linux kernel would solve the issue completely, do you have specifc reasons for using linux-lts ?
(contrary to popular view linux-lts gets roughly the same amount of updates as linux )
systemctl status dhcpcd reports the following:
dhcpcd[394]: if_sendnetlink: NETLINK_GET_STRICT_CHK: Protocol not available
journalctl reports the same with no other issues.
I traced the latter and only found this https://bbs.archlinux.org/viewtopic.php?id=250855
Yet communication with the server is excellent and there are no hickups of any sort.
I tried switching from dhcpcd to dhclient or networkmanager but then (using any one of the two) nginx complains with this:
"ssl_stapling" ignored, host not found in OCSP responder "ocsp.int-x3.letsencrypt.org" in the certificate "/etc/letsencrypt/live/mydomain.mydomain/fullchain.pem"
No matter how much I searched to find something understandable (for my limited knowledge), did not work out.
I am afraid I don't have the knowledge to understand the meaning of these messages, let alone their importance.
The only thing I know is that using dhcpcd (which gives me that report), my server runs as I expect it to.
So, my questions are. Should I pursue a solution of one over the other? Or both?
Or nothing? Because if it works don't fix it.
Thanks in advance for any replies.
]]>