Greypal
-
Content count
50 -
Joined
-
Last visited
Posts posted by Greypal
-
-
Since there might be some demand i can provide a set of urls showing main server online players/bots:
i implemented this after labrats service vanished, since some of my bot features requires them.
http://elmirror.el-fd.org/online_players.htm just a copy of the original, enhanced by a baseurl pointing to game.eternal-lands.com
http://elmirror.el-fd.org/online_bots.txt single line with space separated botnames
http://elmirror.el-fd.org/online_players.txt single line with space separated playernames
http://elmirror.el-fd.org/online.txt contains two lines with space separated names, beginning of line is "Players: " or "Bots: "
atm the update frequency is 10 minutes, if radu agrees i will increase the pace up to 30 or 15 seconds
All files are derived from only one transmission from the game server
It is also no problem to provide a mirrored online list for the PK server as well when radu agrees and provides me an url.
I am also able to provide continouos service when doing server maintenance, in that case the ip address may change, so please dont use static host entries.
If there is some need in having other lists derived from the raw data, contact me.
-
CET
[11:09:43] Resync with the server...
[11:10:30] <4:03>: Disconnected from server!: []
traceroute to game.eternal-lands.com (213.152.3.5), 30 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 1 ms 1 ms 1 ms
2 87.186.224.30 (87.186.224.30) 20 ms 20 ms 20 ms
3 87.190.166.162 (87.190.166.162) 38 ms 37 ms 35 ms
4 f-eb7-i.F.DE.NET.DTAG.DE (62.154.16.182) 22 ms 20 ms 20 ms
5 62.156.138.250 (62.156.138.250) 21 ms 21 ms 21 ms
6 pos0-6-5-0.auvtr1.Aubervilliers.opentransit.net (193.251.242.125) 30 ms 30 ms 30 ms
7 * * *
8 * * *
9 * * *
10 * * *
seems only to be a problem of "deutsche telekom"(dtag.de), since check from other ISP networks do not show problems
meanwhile the connection came back
Thu Jan 21 11:29:16 CET 2010: TCP OK - 9.034 second response time on port 2000
but went away again
Thu Jan 21 11:50:29 CET 2010: CRITICAL - Socket timeout after 10 seconds
finally problem ended so far
Thu Jan 21 12:26:43 CET 2010: TCP OK - 9.033 second response time on port 2000
-
got several shots in several stages
from notebook after second connection prob
traceroute to game.eternal-lands.com (213.152.3.5), 30 hops max, 40 byte packets
1 * * *
2 192.168.2.1 (192.168.2.1) 1.097 ms 1.023 ms 1.129 ms
3 87.186.224.30 (87.186.224.30) 19.719 ms 20.068 ms 19.581 ms
4 87.190.166.166 (87.190.166.166) 20.880 ms 20.370 ms 20.104 ms
5 f-eb7-i.F.DE.NET.DTAG.DE (62.154.16.182) 19.939 ms 19.750 ms 19.704 ms
6 62.156.138.250 (62.156.138.250) 20.687 ms 20.388 ms 20.419 ms
7 xe-1-0-2-0.ffttr2.Frankfurt.opentransit.net (193.251.129.37) 116.269 ms 112.756 ms 108.756 ms
8 xe-3-0-0-0.auvtr2.Aubervilliers.opentransit.net (193.251.128.154) 33.667 ms 33.778 ms xe-3-0-2-0.auvtr2.Aubervilliers.opentransit.net (193.251.128.210) 33.627 ms
9 te2-1.parse1.Paris.opentransit.net (193.251.128.226) 30.465 ms 30.022 ms te2-1.parse3.Paris.opentransit.net (193.251.129.9) 34.014 ms
10 te2-3.parse7.Paris.opentransit.net (193.251.129.206) 33.882 ms te4-4.parse7.Paris.opentransit.net (193.251.129.202) 33.696 ms 33.592 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
from root server saw some loop
traceroute to game.eternal-lands.com (213.152.3.5), 30 hops max, 40 byte packets
1 static.88-198-39-97.clients.your-server.de (88.198.39.97) 0.337 ms 0.319 ms 0.325 ms
2 hos-tr2.juniper1.rz6.hetzner.de (213.239.229.129) 1.016 ms 0.750 ms 0.153 ms
3 hos-bb1.juniper2.ffm.hetzner.de (213.239.240.226) 3.406 ms 3.387 ms 3.406 ms
4 decix2-hetzner.aixit.net (83.141.1.49) 3.528 ms 3.494 ms 3.483 ms
5 as8218.interxion.kleyrex.net (193.189.82.86) 3.490 ms 3.505 ms 3.543 ms
6 xe1-0-0.tcr1.rb.par.as8218.eu (83.167.63.248) 43.630 ms 40.000 ms 33.317 ms
7 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.259 ms 16.169 ms 16.200 ms
8 ge7-0-4.tcr1.rb.par.as8218.eu (83.167.56.182) 36.186 ms 32.192 ms 31.910 ms
9 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.665 ms 16.456 ms 16.183 ms
10 ge7-0-4.tcr1.rb.par.as8218.eu (83.167.56.182) 24.017 ms 22.008 ms 21.312 ms
11 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.244 ms 16.228 ms 16.278 ms
12 ge7-0-4.tcr1.rb.par.as8218.eu (83.167.56.182) 21.199 ms 21.352 ms 21.202 ms
13 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.437 ms 16.455 ms 16.196 ms
14 * * *
15 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.224 ms 16.351 ms 16.376 ms
16 * * *
17 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.425 ms 16.362 ms 16.336 ms
18 * * *
19 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.509 ms 16.515 ms 16.513 ms
20 ge7-0-4.tcr1.rb.par.as8218.eu (83.167.56.182) 23.856 ms 24.238 ms 23.418 ms
21 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 17.318 ms 17.599 ms 17.669 ms
22 * * *
23 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 19.821 ms 18.305 ms 18.036 ms
24 * * *
25 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 18.329 ms 18.783 ms 17.812 ms
26 * * *
27 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 18.753 ms 18.067 ms 18.435 ms
28 ge7-0-4.tcr1.rb.par.as8218.eu (83.167.56.182) 21.375 ms 22.071 ms 21.370 ms
29 ge1-0-23.esr1.rb.par.as8218.eu (83.167.56.183) 16.403 ms 16.479 ms 16.444 ms
30 ge7-0-4.tcr1.rb.par.as8218.eu (83.167.56.182) 21.500 ms 21.422 ms 21.387 ms
and that turned into
traceroute to game.eternal-lands.com (213.152.3.5), 30 hops max, 40 byte packets
1 static.88-198-39-97.clients.your-server.de (88.198.39.97) 0.508 ms 0.329 ms 0.331 ms
2 hos-tr2.juniper1.rz6.hetzner.de (213.239.229.129) 1.018 ms 1.116 ms 0.148 ms
3 hos-bb1.juniper2.ffm.hetzner.de (213.239.240.226) 3.659 ms 3.719 ms 3.487 ms
4 decix2-hetzner.aixit.net (83.141.1.49) 3.589 ms 3.482 ms 3.521 ms
5 as8218.interxion.kleyrex.net (193.189.82.86) 3.507 ms 3.522 ms 3.629 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
...
28 * * *
29 * * *
30 * * *
-
uh, forgot the second root server to get the check log from there
Tue Nov 10 00:24:57 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 10 00:26:01 CET 2009: TCP OK - 9.023 second response time on port 2000
Fri Nov 13 12:27:56 CET 2009: CRITICAL - Socket timeout after 10 seconds
Fri Nov 13 12:27:59 CET 2009: TCP OK - 3.025 second response time on port 2000
Fri Nov 13 21:17:44 CET 2009: CRITICAL - Socket timeout after 10 seconds
Fri Nov 13 21:17:44 CET 2009: TCP OK - 0.029 second response time on port 2000
Sat Nov 14 03:33:59 CET 2009: Connection refused *game update*
Sat Nov 14 03:52:20 CET 2009: TCP OK - 0.020 second response time on port 2000
Sat Nov 14 07:35:23 CET 2009: CRITICAL - Socket timeout after 10 seconds
Sat Nov 14 07:35:32 CET 2009: TCP OK - 9.021 second response time on port 2000
Sat Nov 14 15:51:42 CET 2009: CRITICAL - Socket timeout after 10 seconds
Sat Nov 14 15:52:01 CET 2009: TCP OK - 9.026 second response time on port 2000
compared with the other server less problems, but still corelations
also those results with longer response times ...
the check has a timeout of 10 seconds to exit with "CRITICAL"
when the status is critical the next check starts immediately, if the status is OK there is a sleep 30 between the checks
i use the check_tcp plugin from the nagios monitoring system
-
in addition here also the monitoring logs from my root-server for the last ~8 days
Fri Nov 6 14:45:33 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Fri Nov 6 14:45:33 CET 2009: TCP OK - 0.029 second response time on port 2000
Fri Nov 6 15:00:35 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Fri Nov 6 15:00:55 CET 2009: TCP OK - 0.033 second response time on port 2000
Fri Nov 6 15:15:57 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Fri Nov 6 15:15:57 CET 2009: TCP OK - 0.037 second response time on port 2000
Fri Nov 6 15:55:32 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Fri Nov 6 15:56:07 CET 2009: TCP OK - 0.147 second response time on port 2000
Fri Nov 6 16:10:09 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Fri Nov 6 16:10:09 CET 2009: TCP OK - 0.032 second response time on port 2000
Sat Nov 7 13:30:29 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Sat Nov 7 13:30:50 CET 2009: TCP OK - 0.120 second response time on port 2000
Sun Nov 8 09:18:03 CET 2009: CRITICAL - Socket timeout after 10 seconds
Sun Nov 8 09:18:03 CET 2009: TCP OK - 0.025 second response time on port 2000
Sun Nov 8 16:05:58 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Sun Nov 8 16:06:08 CET 2009: TCP OK - 0.025 second response time on port 2000
Sun Nov 8 23:00:31 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Sun Nov 8 23:00:51 CET 2009: TCP OK - 0.032 second response time on port 2000
Mon Nov 9 00:01:04 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 00:01:05 CET 2009: TCP OK - 0.027 second response time on port 2000
Mon Nov 9 10:11:03 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 10:11:13 CET 2009: TCP OK - 0.026 second response time on port 2000
Mon Nov 9 10:41:05 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 10:41:05 CET 2009: TCP OK - 0.026 second response time on port 2000
Mon Nov 9 11:00:57 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 11:00:57 CET 2009: TCP OK - 0.025 second response time on port 2000
Mon Nov 9 11:02:37 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 11:02:52 CET 2009: TCP OK - 0.025 second response time on port 2000
Mon Nov 9 11:17:24 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 11:17:49 CET 2009: TCP OK - 0.025 second response time on port 2000
Mon Nov 9 11:27:46 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 11:27:46 CET 2009: TCP OK - 0.030 second response time on port 2000
Mon Nov 9 12:10:51 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 12:10:51 CET 2009: TCP OK - 0.026 second response time on port 2000
Mon Nov 9 12:22:06 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Nov 9 12:22:06 CET 2009: TCP OK - 0.031 second response time on port 2000
Tue Nov 10 00:24:46 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 10 00:26:00 CET 2009: TCP OK - 3.031 second response time on port 2000
Sat Nov 14 01:09:45 CET 2009: CRITICAL - Socket timeout after 10 seconds
Sat Nov 14 01:09:45 CET 2009: TCP OK - 0.058 second response time on port 2000
Sat Nov 14 03:34:05 CET 2009: Connection refused * game update *
Sat Nov 14 03:52:20 CET 2009: TCP OK - 0.068 second response time on port 2000
Sat Nov 14 11:35:13 CET 2009: CRITICAL - Socket timeout after 10 seconds
Sat Nov 14 11:35:22 CET 2009: TCP OK - 9.038 second response time on port 2000
Sat Nov 14 15:51:47 CET 2009: CRITICAL - Socket timeout after 10 seconds
Sat Nov 14 15:51:56 CET 2009: TCP OK - 9.025 second response time on port 2000
so the problem at 15:51 had more impact on my home-isp than on my root server
but it shows, that socket timeouts happen more or less frequently :/
-
all times in CET
[15:51:41] Resync with the server...
[15:51:56] Resync with the server...
[15:51:56] #Message from God: Greypal was eaten by a Grue (lagged out)!
[15:51:56] Disconnected from server!
[15:51:56] Press Alt-x to close the game
[15:52:23] Connecting to Server...
[15:52:23] Hi, and welcome to Eternal Lands
got some traceroute when today's connection had some issues, the traceroutes were taken between [15:51:56] and [15:52:23]
the first is after first disconnect when connection came back for some seconds
traceroute to game.eternal-lands.com (213.152.3.5), 30 hops max, 40 byte packets
1 * * * internal-firewall, does not show up in traceroutes
2 192.168.2.1 (192.168.2.1) 1.184 ms 0.947 ms 1.511 ms dsl-router@home
3 87.186.224.30 (87.186.224.30) 19.938 ms 19.954 ms 19.896 ms
4 87.190.166.162 (87.190.166.162) 21.571 ms 20.225 ms 19.902 ms
5 f-eb7-i.F.DE.NET.DTAG.DE (62.154.16.182) 20.531 ms 20.367 ms 20.349 ms
6 62.156.138.250 (62.156.138.250) 20.939 ms 21.181 ms 20.150 ms
7 tengige0-13-0-1.auvtr1.Aubervilliers.opentransit.net (193.251.132.77) 34.080 ms 33.841 ms 33.337 ms
8 xe-7-1-0-0.auvtr2.Aubervilliers.opentransit.net (193.251.132.81) 30.053 ms 30.207 ms 29.470 ms
9 te3-1.parse1.Paris.opentransit.net (193.251.128.230) 33.386 ms 33.791 ms te2-1.parse3.Paris.opentransit.net (193.251.129.9) 30.056 ms
10 te4-4.parse7.Paris.opentransit.net (193.251.129.202) 33.841 ms te4-1.parse7.Paris.opentransit.net (193.251.129.230) 33.565 ms 33.770 ms
11 * * *
12 xe1-2-0.tcr1.rb.par.as8218.eu (83.167.56.178) 36.570 ms xe3-0-0.tcr1.rb.par.as8218.eu (83.167.56.174) 36.991 ms xe1-2-0.tcr1.rb.par.as8218.eu (83.167.56.178) 37.780 ms
13 83.167.56.183 (83.167.56.183) 37.709 ms * 39.793 ms
14 game.eternal-lands.com (213.152.3.5) 37.430 ms 37.194 ms 37.642 ms
after a few seconds connection problem happened again
traceroute to game.eternal-lands.com (213.152.3.5), 30 hops max, 40 byte packets
1 * * *
2 192.168.2.1 (192.168.2.1) 0.874 ms 0.826 ms 1.445 ms
3 87.186.224.30 (87.186.224.30) 19.514 ms 20.111 ms 19.974 ms
4 87.190.166.162 (87.190.166.162) 21.078 ms 20.139 ms 19.866 ms
5 * * *
6 62.156.138.250 (62.156.138.250) 20.752 ms 20.314 ms 20.201 ms
7 tengige0-13-0-1.auvtr1.Aubervilliers.opentransit.net (193.251.132.77) 34.804 ms 33.956 ms 33.782 ms
8 xe-7-1-0-0.auvtr2.Aubervilliers.opentransit.net (193.251.132.81) 29.914 ms 29.715 ms 29.786 ms
9 te3-1.parse1.Paris.opentransit.net (193.251.128.230) 33.269 ms 33.234 ms te2-1.parse3.Paris.opentransit.net (193.251.129.9) 29.811 ms
10 te4-4.parse7.Paris.opentransit.net (193.251.129.202) 33.485 ms te4-1.parse7.Paris.opentransit.net (193.251.129.230) 33.545 ms 34.020 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
then again after a few seconds problems went away
traceroute to game.eternal-lands.com (213.152.3.5), 30 hops max, 40 byte packets
1 * * *
2 192.168.2.1 (192.168.2.1) 1.401 ms 1.091 ms 1.040 ms
3 87.186.224.30 (87.186.224.30) 19.742 ms 20.154 ms 19.640 ms
4 87.190.166.162 (87.190.166.162) 20.727 ms 20.315 ms 20.003 ms
5 * * *
6 62.156.138.250 (62.156.138.250) 20.947 ms 20.979 ms 20.405 ms
7 tengige0-13-0-1.auvtr1.Aubervilliers.opentransit.net (193.251.132.77) 34.460 ms 34.642 ms 33.773 ms
8 xe-7-1-0-0.auvtr2.Aubervilliers.opentransit.net (193.251.132.81) 29.833 ms 29.886 ms 29.479 ms
9 te3-1.parse1.Paris.opentransit.net (193.251.128.230) 33.548 ms 33.661 ms te2-1.parse3.Paris.opentransit.net (193.251.129.9) 30.879 ms
10 te4-4.parse7.Paris.opentransit.net (193.251.129.202) 34.027 ms te4-1.parse7.Paris.opentransit.net (193.251.129.230) 33.786 ms 33.434 ms
11 * * *
12 xe1-2-0.tcr1.rb.par.as8218.eu (83.167.56.178) 36.755 ms xe3-0-0.tcr1.rb.par.as8218.eu (83.167.56.174) 36.367 ms xe1-2-0.tcr1.rb.par.as8218.eu (83.167.56.178) 36.380 ms
13 83.167.56.183 (83.167.56.183) 40.425 ms * 37.033 ms
14 game.eternal-lands.com (213.152.3.5) 37.152 ms 36.465 ms 36.984 ms
-
Have no current traceroute ouput, but have check output from 12. Oct until today which shows that there are also problems resolving the hostname
as well as "connection time outs".
here log from my "server2"
Mon Oct 12 19:23:08 CEST 2009: TCP OK - 5.026 second response time on port 2000
Mon Oct 12 19:40:33 CEST 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Oct 12 19:40:43 CEST 2009: TCP OK - 5.021 second response time on port 2000
Mon Oct 12 19:42:09 CEST 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Mon Oct 12 19:42:33 CEST 2009: TCP OK - 5.021 second response time on port 2000
Thu Oct 15 01:13:39 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Thu Oct 15 01:14:22 CEST 2009: TCP OK - 3.021 second response time on port 2000
Thu Oct 15 01:15:32 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Thu Oct 15 01:15:43 CEST 2009: TCP OK - 0.024 second response time on port 2000
Fri Oct 16 16:27:08 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Fri Oct 16 16:28:41 CEST 2009: TCP OK - 3.025 second response time on port 2000
Fri Oct 16 16:35:07 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Fri Oct 16 16:36:36 CEST 2009: TCP OK - 9.025 second response time on port 2000
Fri Oct 16 16:43:57 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Fri Oct 16 16:44:50 CEST 2009: TCP OK - 3.019 second response time on port 2000
Fri Oct 16 16:45:30 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Fri Oct 16 16:45:43 CEST 2009: TCP OK - 3.019 second response time on port 2000
Fri Oct 16 16:46:23 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Fri Oct 16 16:54:03 CEST 2009: TCP OK - 9.025 second response time on port 2000
Sun Oct 25 04:18:03 CET 2009: Connection refused
Sun Oct 25 04:24:59 CET 2009: TCP OK - 0.026 second response time on port 2000
Thu Oct 29 08:22:00 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Thu Oct 29 08:24:48 CET 2009: TCP OK - 0.026 second response time on port 2000
Thu Oct 29 08:28:50 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Thu Oct 29 08:30:10 CET 2009: TCP OK - 5.020 second response time on port 2000
Thu Oct 29 08:34:56 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Thu Oct 29 08:36:48 CET 2009: TCP OK - 0.021 second response time on port 2000
Thu Oct 29 08:41:15 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Thu Oct 29 08:43:07 CET 2009: TCP OK - 0.045 second response time on port 2000
Thu Oct 29 08:48:24 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Thu Oct 29 08:51:22 CET 2009: TCP OK - 5.026 second response time on port 2000
Fri Oct 30 15:07:58 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Fri Oct 30 15:08:12 CET 2009: TCP OK - 0.021 second response time on port 2000
Sat Oct 31 18:41:30 CET 2009: CRITICAL - Socket timeout after 10 seconds
Sat Oct 31 18:41:40 CET 2009: TCP OK - 5.028 second response time on port 2000
Sun Nov 1 03:29:03 CET 2009: Connection refusedond response time on port 2000
Sun Nov 1 03:36:11 CET 2009: TCP OK - 0.020 second response time on port 2000
Tue Nov 3 02:23:56 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 02:31:46 CET 2009: TCP OK - 9.019 second response time on port 2000
Tue Nov 3 04:27:44 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 04:28:03 CET 2009: TCP OK - 9.024 second response time on port 2000
Tue Nov 3 09:22:19 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 09:22:32 CET 2009: TCP OK - 3.025 second response time on port 2000
Tue Nov 3 12:12:35 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 12:12:44 CET 2009: TCP OK - 9.018 second response time on port 2000
Tue Nov 3 14:59:11 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 14:59:20 CET 2009: TCP OK - 9.019 second response time on port 2000
Tue Nov 3 15:32:45 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 15:32:48 CET 2009: TCP OK - 3.026 second response time on port 2000
Tue Nov 3 15:33:28 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 15:35:17 CET 2009: TCP OK - 9.019 second response time on port 2000
Tue Nov 3 19:06:54 CET 2009: TCP OK - 0.020 second response time on port 2000
and now log from server1, but only started when there were problems last night:
Tue Nov 3 02:34:56 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 02:38:00 CET 2009: TCP OK - 3.031 second response time on port 2000
Tue Nov 3 04:34:00 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 04:34:19 CET 2009: TCP OK - 9.031 second response time on port 2000
Tue Nov 3 07:05:00 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 07:05:00 CET 2009: TCP OK - 0.046 second response time on port 2000
Tue Nov 3 09:28:22 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 09:28:45 CET 2009: TCP OK - 3.025 second response time on port 2000
Tue Nov 3 11:00:27 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 11:00:42 CET 2009: TCP OK - 0.032 second response time on port 2000
Tue Nov 3 12:18:50 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 12:18:50 CET 2009: TCP OK - 0.038 second response time on port 2000
Tue Nov 3 12:54:28 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 12:54:53 CET 2009: TCP OK - 0.026 second response time on port 2000
Tue Nov 3 13:09:55 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 13:10:30 CET 2009: TCP OK - 0.144 second response time on port 2000
Tue Nov 3 13:23:51 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 13:24:56 CET 2009: TCP OK - 0.031 second response time on port 2000
Tue Nov 3 15:38:53 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 15:38:58 CET 2009: TCP OK - 5.036 second response time on port 2000
Tue Nov 3 15:39:38 CET 2009: CRITICAL - Socket timeout after 10 seconds
Tue Nov 3 15:41:29 CET 2009: TCP OK - 0.025 second response time on port 2000
Tue Nov 3 16:11:02 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 16:11:02 CET 2009: TCP OK - 0.035 second response time on port 2000
Tue Nov 3 16:19:53 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 16:19:53 CET 2009: TCP OK - 0.027 second response time on port 2000
Tue Nov 3 16:28:34 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 16:28:34 CET 2009: TCP OK - 0.030 second response time on port 2000
Tue Nov 3 17:19:11 CET 2009: TCP CRITICAL - Invalid hostname, address or socket: game.eternal-lands.com
Tue Nov 3 17:20:51 CET 2009: TCP OK - 0.026 second response time on port 2000
unfortunately the servers are not in sync with the time, the difference is ~6 minutes
both servers are located at the same hoster but in different data-centers
will post also traceroute-logs when available
-
Tue Aug 18 03:47:46 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Tue Aug 18 03:49:32 CEST 2009: TCP OK - 6.029 second response time on port 2000|time=6.029464s;;;0.000000;10.000000
Tue Aug 18 03:54:23 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Tue Aug 18 03:56:53 CEST 2009: TCP OK - 9.036 second response time on port 2000|time=9.035572s;;;0.000000;10.000000
Tue Aug 18 03:57:53 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Tue Aug 18 03:58:19 CEST 2009: TCP OK - 6.030 second response time on port 2000|time=6.029607s;;;0.000000;10.000000
Tue Aug 18 04:01:30 CEST 2009: CRITICAL - Socket timeout after 10 seconds
Tue Aug 18 04:04:54 CEST 2009: TCP OK - 6.039 second response time on port 2000|time=6.038915s;;;0.000000;10.000000
So after more than 2.5 hours the game server is again reachable from several german providers/hosters
During the last phase the routes got lost again several times for some minutes, now seem to stay stable.
since it is now 4:10 am have fun, i need to take a nap
c u
-
state changed on one server which had the latest loss of route, being able to connect again
on the other routes i see less dead nodes in the trace
-
hmmm, server reachable from poland, checked from a site @ warszaw.
Still all german ISP' i have access to have problems with ending routes in france.
-
at least 3 big german carriers have atm problems the routes to game server end somewhere in france.
During the first 5-10 minutes i succeeded to connect at least from 1 of 3 via telnet to port 2000
t-home started to have problems at 01:23 CET
-
I noticed the same with several wearable items which increase HP, but after mapchange the healthbar is shown correct, also within the stats window the HP are shown correct all the time,
so the server sends a additional 5 HP damage-event when removing such items, even if it is no "hit".
Items checked
Dragonblade
CoL
MoL
-
I will volunteer programming the bot, may ask several people for translations into their native language.
Hosting the bot is also provided by me.
-
My counter says roughly 61k yew were harvested with the same saw
-
i dealt with that code now for a couple of hours and still fixing stuff.
the problem with the cast are that there is code to check if enough essences are in the inventory, but the code wont work when the bot does not have any of the required essences.
for(i = 0; i < 36; i++) {
..if(!strncmp(inv.name, "Health Essence", 14)) {
....// this line would never be reached if there are no health essences at all, because the compare wont found something if it is not here
....if(inv.quantity < 40)
......send_raw_text("#gm %cI am running low on health ess. Please bring some soon!", 127+c_red1);
....else if (inv.quantity < 20)
......send_raw_text("#gm %cI am almost out of health ess. Please bring some quick!", 127+c_red2);
....else if (inv.quantity == 0)
......send_raw_text("#gm %cI am OUT of health ess and can not restore! Please bring some NOW!!", 127+c_red3);
..}
}
that is the problem with all those constructs they will not notice when the required item is not in inv at all, will provide improvements/diffs for that
the construct should look like
fit=0; // preset founditem to 0
for(i = 0; i < 36; i++) {
..if(!strncmp(inv.name, "Health Essence", 14)) {
....fit=inv.quantity; // set the found item variable with the quantity in inv
..}
}
// changed also the order of check, in the old version only "<40" was true for all cases, cause it was checked first
if (fit == 0)
..send_raw_text("#gm %cI am OUT of health ess and can not restore! Please bring some NOW!!", 127+c_red3);
else if (fit < 20)
..send_raw_text("#gm %cI am almost out of health ess. Please bring some quick!", 127+c_red2);
else if(fit < 40)
..send_raw_text("#gm %cI am running low on health ess. Please bring some soon!", 127+c_red1);
will also add the found code changes to my copy
will eventually turn all those code in a generic function, cause it is used very often
-
it is not rounded up, it uses the "ground" or "int" function. so 20.8 = 20
-
if u read a price list, didn't you expect that this is the price, and not something rounded?
a normal player doesnt get the idea that this is a fractional price.
Regards
-
After found this article
http://www.eternal-lands.com/forum/index.php?showtopic=42786
where radu stated:
No negative perks are allowed after the botization.
Only perk allowed is MM.
does this mean that every character is not allowed to have negative perks or other perks than MM when being botified?
The question in the article was if it is possible to get a/some negative perks after botification.
I already took some perks on characters designated to be bots, cause this problem is not stated in the bot-rules.
What should i do now? #reset?
Regards
-
It seems so, but this rounding problem only happens on flowers with 0.42gc price, all others are not affected of rounding problems, tried selling impatiens (0.33gc), red rose (0.25gc) always 100 items and got 33gc and 25gc.
and depending on the amount you sell, the rounding error is between ~1 and ~5 percent, which seems quite high.
-
Noticed that when selling 500 blue lupine to VotD flower shop i get 208gc instead of expected 210gc
which is 0.416gc instead of 0.42gc as stated by the npc
Regards
Additional sellings give
100 blue lupine = 41gc instead of 42
200 blue lupine = 83gc (84)
300 blue lupine = 125gc (126)
400 blue lupine = 166gc (168)
50 blue lupine = 20gc (21)
-
hi there,
i think most of the invasions only attract high level players due to the fact that there will be only "slightly stronger" monsters always around, so u will meet cycs, troll and such stuff in WS,
for lower levels even invasions gargs and gobs may be heavy stuff on the common safe maps
so my suggestion would be to have invasions with creatures normally around in these areas, maybe the next higher level creature after the highest monster on this map.
this will also be on common maps cause trouble to a lot of low levels, cause fighting a grizzly isnt a thing for everyone
this may then also attract players normally fleeing inhouse when a invasion is announced
Just my opinions
-
titanium in evtr mine
-
Video card: Quadro NVS 140M/PCI/SSE2
Vendor ID: NVIDIA Corporation
OpenGL Version: 2.1.2 NVIDIA 169.07
no probs so far
-
do not know where learners bot server is located, but those bots grue a lot
at least reported by our bot maintainer at 00:45 CET
Animal Removal Stone, Auction
in Marketplace
Posted · Report reply
Starting price: 500kgc
BIN: 535kgc
Increments: 5k or higher
Auction ends 48 hours after last bid
Good Luck