View unanswered posts | View active topics It is currently Mon Oct 23, 2017 7:17 pm

Forum rules


This is an international forum. PLEASE speak ENGLISH! If you have problems with english, please try to post in english and repeat the post in your motherlanguage.

Visit the How To Section before posting here!



Reply to topic  [ 4 posts ] 
No route to et.hirntot.org 
Author Message
Private

Joined: Thu Oct 22, 2009 5:55 pm
Posts: 16
Location: Nuremberg
Reply with quote
Hello,

today your ET1 server (and your website) had a severe and long outage at approx. 9:30 pm which lastet about 1 hour. ET2, ET3 and TS were not affected.
ET1 server was only reachable for a few seconds or minutes from time to time during this period. The game server instance continued to run because it switched to the next maps in time. So it was not a problem of your server, but a severe problem of your hoster's router in front of your server. Here are some traceroute logs to provide some evidence.

The DNS resolution worked in all cases: it returned the proper IP adrdess.
Code:
ping et.hirntot.org
PING et.hirntot.org (193.192.59.186) 56(84) bytes of data.
^C
--- et.hirntot.org ping statistics ---
26 packets transmitted, 0 received, 100% packet loss, time 25191ms



First, a good route to et.hirntot.org from the day before (and after the outage):
Code:
traceroute et.hirntot.org
traceroute to et.hirntot.org (193.192.59.186), 30 hops max, 60 byte packets
 1  <removed by me>  0.484 ms  0.628 ms  0.757 ms
 2  <removed by me>  13.951 ms  14.393 ms  16.424 ms
 3  <removed by me>  19.171 ms  19.329 ms  19.862 ms
 4  92.79.212.101 (92.79.212.101)  22.516 ms  22.561 ms  25.778 ms
 5  92.79.213.130 (92.79.213.130)  28.947 ms  32.368 ms  32.370 ms
 6  decix.link11.de (80.81.192.218)  31.266 ms  26.595 ms  27.121 ms
 7  link11.ociris.com (80.95.152.210)  28.321 ms  25.300 ms  21.323 ms
 8  193.192.59.186 (193.192.59.186)  28.725 ms  25.183 ms  26.023 ms


Now, the bad route when et.hirntot.org was not reachable: It wrongly pointed to 193.192.58.45!!! Why?
Code:
traceroute et.hirntot.org
traceroute to et.hirntot.org (193.192.59.186), 30 hops max, 60 byte packets
 1  <removed by me>  0.474 ms  1.708 ms  2.191 ms
 2  <removed by me>  16.111 ms  16.120 ms  17.144 ms
 3  <removed by me>  21.919 ms  21.936 ms  27.476 ms
 4  92.79.212.101 (92.79.212.101)  24.544 ms  24.547 ms  28.147 ms
 5  92.79.213.130 (92.79.213.130)  33.052 ms  33.054 ms  33.295 ms
 6  decix.link11.de (80.81.192.218)  66.895 ms  68.875 ms  58.587 ms
 7  link11.ociris.com (80.95.152.210)  28.907 ms  18.428 ms  19.459 ms
 8  193.192.58.45 (193.192.58.45)  25.591 ms  26.265 ms  27.405 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
<aborted here>


Now, still a bad route, but the server was reachable for some time: Note the additional hop!
Code:
traceroute et.hirntot.org
traceroute to et.hirntot.org (193.192.59.186), 30 hops max, 60 byte packets
 1  <removed by me>  0.389 ms  0.537 ms  0.999 ms
 2  <removed by me>  14.791 ms  15.105 ms  17.300 ms
 3  <removed by me>  21.003 ms  21.463 ms  21.861 ms
 4  92.79.212.101 (92.79.212.101)  22.180 ms  26.490 ms  26.535 ms
 5  92.79.213.130 (92.79.213.130)  29.946 ms  30.145 ms  34.022 ms
 6  decix.link11.de (80.81.192.218)  31.971 ms  25.070 ms  25.446 ms
 7  link11.ociris.com (80.95.152.210)  27.376 ms  19.288 ms  20.415 ms
 8  * * *
 9  193.192.59.186 (193.192.59.186)  26.035 ms  27.676 ms  28.754 ms


After the outage, the route was fine again: 8 hops as expected.
Code:
traceroute et.hirntot.org
traceroute to et.hirntot.org (193.192.59.186), 30 hops max, 60 byte packets
 1  <removed by me>  0.484 ms  0.628 ms  0.757 ms
 2  <removed by me>  13.951 ms  14.393 ms  16.424 ms
 3  <removed by me>  19.171 ms  19.329 ms  19.862 ms
 4  92.79.212.101 (92.79.212.101)  22.516 ms  22.561 ms  25.778 ms
 5  92.79.213.130 (92.79.213.130)  28.947 ms  32.368 ms  32.370 ms
 6  decix.link11.de (80.81.192.218)  31.266 ms  26.595 ms  27.121 ms
 7  link11.ociris.com (80.95.152.210)  28.321 ms  25.300 ms  21.323 ms
 8  193.192.59.186 (193.192.59.186)  28.725 ms  25.183 ms  26.023 ms


This is some solid evidence that the routing tables of "link11.ociris.com" were screwed up. You should file this as a problem with your hoster!
Perhaps, this could also explain the lag issue which happens quite regularly.

Unclear is why your other servers(?) were not affected? Do you have more physical root servers or just one?

Cheers,
Phobos


Thu Mar 20, 2014 12:08 am
Profile
Captain
Captain
User avatar

Joined: Thu Oct 30, 2008 6:32 pm
Posts: 1073
Reply with quote
hello phobos,

thanks a lot for testing/reporting, realy appreciate it!
some of our geeks will have a look at it soon!

cheers

ps: regarding your question, afaik we have 1 root with 4 cores/1 for each server

_________________
// the addiction sleeps..


Thu Mar 20, 2014 11:23 am
Profile WWW
Captain
Captain
User avatar

Joined: Tue Nov 11, 2008 7:17 pm
Posts: 1162
Location: Germany
Reply with quote
I did address this matter to our provider.

_________________
ImageImageImage


Sat Mar 22, 2014 1:13 pm
Profile
Lieutnant
Lieutnant
User avatar

Joined: Fri Oct 31, 2008 5:53 pm
Posts: 811
Reply with quote
We got 4 IPs on one network device. Two of them had a typo in the broadcast address. This could have caused trouble. I fixed it. Thanks for your detailed analyse!

Lets hope it gets better now.

_________________
Planung ersetzt nur den Zufall durch Irrtum


Sun Mar 23, 2014 5:42 am
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 4 posts ] 

Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software for PTF.