Solved Weird issue after upgrade from 12.0-release to 12.1-release

M

Max212

Hi,

I've encountered a weird issue after upgrading FreeBSD from 12.0-RELEASE to 12.1-RELEASE.
After the upgrading three servers, all three experience same symptoms. Installed services (DNS, Samba, Emby, FTP etc) all work very sluggish or not at all. When I say sluggish or not at all, it means like initially I get some response and after that it doesn't work any more.
I can normally SSH to servers, but when I run dmesg or try to run cat /var/log/messages it takes a really long time to show the content and at some point it just stops and SSH connection drops.

No firewall is running on these servers. I can reach outside world normally, I can reinstall ports normally. I can saturate WAN link without the issue.
If I run above commands via console, everything is working fine. All servers are virtual on ESXi 6.something.

I've run tcpdump and I can see a lot of retransmitions and delays in packet sending.

I have few servers that are still on 12.0-RELEASE and they work fine without the issue.

Did someone encounter this kind of issue or do you have any idea where to look?

Thank you!
 
I've solved the issue. I've upgraded hypervisor ESXi from 6.0 to 6.5 and everything started to work normally.
 
I am experiencing the same issue with ESXi 6.0 and FreeBSD 12.1 but I can not upgrade to ESXi 6.5. Is there any other way to solve this? 12.0 was working very well without any issues like this.
 
Lefteris said:
I am experiencing the same issue with ESXi 6.0 and FreeBSD 12.1 but I can not upgrade to ESXi 6.5. Is there any other way to solve this? 12.0 was working very well without any issues like this.
Click to expand...
There seems to be a bug/issue introduced with the network driver of vmxnet3 in FreeBSD v12.1. I switched the VM ESXi 6.0 to network adapter E1000 and it started to work again without issues.
 
ESXi upgrade is not possible for me so to the best of my knowledge so far there are only 3 solutions to this problem, either switch to E1000, downgrade back to 12.0 or fix the newly introduced bug/issue in 12.1. The best one of course would be to fix the newly introduced issue.
 
Lefteris said:
ESXi upgrade is not possible for me so to the best of my knowledge so far there are only 3 solutions to this problem, either switch to E1000, downgrade back to 12.0 or fix the newly introduced bug/issue in 12.1. The best one of course would be to fix the newly introduced issue.
Click to expand...

Did you try the how-to guide that i've linked? It works like a charm.
 
You must log in or register to reply here.
Back
Top