Proxmox + SyS (OVH) Game - Connection drop

[FlorinMarian]

Hi, guys!
I've rented an Sys Game dedicated server and It happens few times every day to have network disconnects for every IP addresses (at least tested for failover IP-addresses).
Did anyone encountered this kind of situation ?
It happens since about 1 month ago, I dont remember if I've updated proxmox or anything simmilar to know if it's caused by any update or any change.
Any idea how to debug this?
Thank you!

 

[Pierre-Yves]

Did you open a ticket at OVH Support ?
Maybe it's a netword card physical trouble or just the network cable that is not firmly engaged in its port ...
Is there any info in syslog logs ?
Regards

 

[FlorinMarian]

Here is my dmesg output: https://hazi.ro/dmesg.txt

Any hint if there's something wrong?
Thank you!

 

[Pierre-Yves]

Lots of hard reset of the e1000 network card ...

[615030.679729] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
                  TDH                  <1>
                  TDT                  <e4>
                  next_to_use          <e4>
                  next_to_clean        <0>
                buffer_info[next_to_clean]:
                  time_stamp           <10928f64f>
                  next_to_watch        <1>
                  jiffies              <10928ff18>
                  next_to_watch.status <0>
                MAC Status             <80083>
                PHY Status             <796d>
                PHY 1000BASE-T Status  <3800>
                PHY Extended Status    <3000>
                PCI Status             <10>
[615030.839510] e1000e 0000:00:19.0 eno1: Reset adapter unexpectedly

Maybe contact OVH Support for evaluation from their side ...
Seems the same as this one :
https://serverfault.com/questions/6...pter-unexpectedly-detected-hardware-unit-hang

 

[FlorinMarian]

I've requested assitance from OVH and they changed network connector without any effect on my server.
I've also applied

ethtool -K eno1 gso off gro off tso off

after reboot and this solved my problem.
How to make that command persistent after reboot?
Thank you!

 

[Pierre-Yves]

Maybe you can put it in a shell script :

nano networkcard.sh

and put into it

ethtool -K eno1 gso off gro off tso off

Save and make it runnable

chmod 777 networkcard.sh

Then add it in the root crontab (crontab -e when you're root) with "@reboot" for frequency
Like :

@reboot root  /root/networkcard.sh