Are you running 2 DHCP servers?
What were the repeating messages?
Your log doesn't reflect your statement. The log shows it was sleep for a little under 2 hours, but you describe a 2 day outage.
Perhaps there's some details missing?
Are you running 2 DHCP servers?
What were the repeating messages?
Your log doesn't reflect your statement. The log shows it was sleep for a little under 2 hours, but you describe a 2 day outage.
Perhaps there's some details missing?
No, only this server.
And apologies, I wasn’t clear. I logged into the server on Sunday around 8am and then had to leave immediately on a trip, hence only posting today. The logs are correct.
Oh, it’s a Broadcom NIC?
The last time I tried a Broadcom NIC (BCM27810S) was with a Windows machine, and the NIC driver tended to get completely wedged if I tried to disable the device. With it on Thunderbolt, it was even weirder: if I unplugged it, the no-longer-connected NIC and its parent PCIe port still appeared in device manager.
It wouldn’t surprise me if Broadcom NICs had similar weird behaviors in Linux. I wonder if your Broadcom NIC is overheating or something?
We’ve never had any problems with Broadcom NICs - we use 5719 cards. They’ve been bulletproof in the servers we’ve used them in.
That’s not to say that this NIC isn’t the issue. I’ve got a couple of things I want to try first, but if this continues I will swap out the NIC, and if that doesn’t work I may have to fallback to v24.10.6 as the 24.10 series never gave us this issue.