assuming that you run a linux realy, have a look at the interface with ethtool
sudo ethtool eth0
and look if it is in full of half duplex mode. If it is in halfduplex mode that will probably be the cause of the errors. you could try setting it to full duplex mode with e. g. 100 mbit/s with the following command:
sudo ethtool -s eth0 speed 100 duplex full autoneg off
this might crash your network connection, so be prepared for a remote reboot of the machine (or use IPMI if available).
On 19.03.2017 11:55, patacca wrote:
Hi everyone, I am running an exit node[1] with nocix (previously known as datashack) and everything worked pretty well until the beginning of March when they moved the physical location of my dedicated server: since then I am registering a lot of eth0 errors[2] and, as atlas is showing, a lot of downtime. Note also that previously I've run the server for like a year without any single eth error! I've already contacted them asking to check the cables and they replied everything it's ok but I am starting to think that *it must be* some kind of hardware issue. I'd like to debug the issue furthermore to excude any software related problem but I don't know what to do, has anybody got a hint?
Thanks, patacca
[1] https://atlas.torproject.org/#details/2B72D043164D5036BC1087613830E2ED5C6069... [2] http://pastebin.com/7ZYXmTGE _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays