Topic
[investigating] Singapore tester: previous tests were great, but I can't even enter the world this time.
Game always freezes at the 'And so it begins' page.
This is what it says:
OMG reload! (unrecognized msg:ClientConnectionProcessor.doConnect INVALID token)
Replies
-
Error #2036
I've tested the game three times before and it worked very smoothly. I've already installed the Flash debugger. -
ping -n 5 c1.glitch.bz
Pinging d1n9e7m6lxef9a.sfo4.cloudfront.net [216.137.37.164] with 32 bytes of data:
Reply from 216.137.37.164: bytes=32 time=200ms TTL=50
Reply from 216.137.37.164: bytes=32 time=222ms TTL=50
Reply from 216.137.37.164: bytes=32 time=243ms TTL=50
Reply from 216.137.37.164: bytes=32 time=264ms TTL=50
Reply from 216.137.37.164: bytes=32 time=286ms TTL=50
Ping statistics for 216.137.37.164:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 286ms, Average = 243ms -
those ping times seem very wrong for cloudfront - it should be picking a pop closer to you. if you have access to a unix/linux/osx box, could be post the output of these commands?
# dig identity.cloudfront.net txt
# dig resolver-identity.cloudfront.net txt
# traceroute c2.glitch.bz -
Hi Bees
This is from my little linux box.
ping@Starling:~$ dig identiy.cloudfront.net txt
; DiG 9.7.0-P1 HEADER DiG 9.7.0-P1 HEADER -
I did another traceroute for c1 (and c2 for good measure)
ping@Starling:~$ traceroute c1.glitch.bz
traceroute to c1.glitch.bz (216.137.37.237), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.509 ms 3.755 ms 4.053 ms
2 bb219-75-6-1.singnet.com.sg (219.75.6.1) 20.936 ms 19.901 ms 19.978 ms
3 202.166.119.9 (202.166.119.9) 20.068 ms 20.188 ms 20.345 ms
4 xe-0-0-0-3000.qt-ar04.singnet.com.sg (202.166.121.129) 20.432 ms 20.581 ms 20.737 ms
5 xe-0-3-0.kirin.singnet.com.sg (202.166.124.241) 23.538 ms 24.218 ms 24.675 ms
6 ae6-0.singha.singnet.com.sg (202.166.120.186) 26.147 ms 8.761 ms 16.201 ms
7 ae5-0.beck.singnet.com.sg (202.166.126.41) 16.855 ms 17.510 ms 18.121 ms
8 203.208.190.129 (203.208.190.129) 18.611 ms 21.754 ms 22.669 ms
9 ge-0-0-0-0.sngtp-dr1.ix.singtel.com (203.208.149.78) 22.769 ms 22.827 ms 22.913 ms
10 203.208.152.205 (203.208.152.205) 25.430 ms xe-1-0-0-0.sngtp-cr1.ix.singtel.com (203.208.183.61) 25.900 ms 203.208.152.205 (203.208.152.205) 26.366 ms
11 so-2-0-1-0.plapx-cr3.ix.singtel.com (203.208.151.94) 231.876 ms so-2-0-2-0.plapx-cr3.ix.singtel.com (203.208.149.30) 215.778 ms 217.373 ms
12 ge-0-0-0-0.plapx-dr1.ix.singtel.com (203.208.149.1) 204.569 ms 198.973 ms ge-4-0-0-0.plapx-dr1.ix.singtel.com (203.208.149.5) 201.611 ms
13 paix01-sfo4.amazon.com (198.32.176.36) 221.713 ms 222.832 ms 223.980 ms
14 72.21.222.194 (72.21.222.194) 211.693 ms 210.923 ms 212.208 ms
15 72.21.222.213 (72.21.222.213) 228.677 ms 229.376 ms 230.377 ms
16 server-216-137-37-237.sfo4.cloudfront.net (216.137.37.237) 217.082 ms 202.195 ms 202.339 ms
ping@Starling:~$ traceroute c2.glitch.bz
traceroute to c2.glitch.bz (216.137.37.180), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 2.311 ms 2.374 ms 4.261 ms
2 bb219-75-6-1.singnet.com.sg (219.75.6.1) 16.897 ms 17.502 ms 18.051 ms
3 202.166.119.9 (202.166.119.9) 18.679 ms 19.116 ms 19.801 ms
4 xe-0-0-0-3000.qt-ar04.singnet.com.sg (202.166.121.129) 20.246 ms 20.928 ms 22.442 ms
5 xe-0-3-0.kirin.singnet.com.sg (202.166.124.241) 22.825 ms 23.468 ms 25.016 ms
6 ae6-0.singha.singnet.com.sg (202.166.120.186) 26.840 ms 9.790 ms 16.287 ms
7 ae5-0.beck.singnet.com.sg (202.166.126.41) 16.877 ms 20.414 ms 20.532 ms
8 203.208.190.129 (203.208.190.129) 22.218 ms 22.393 ms 22.412 ms
9 ge-1-0-0-0.sngtp-dr1.ix.singtel.com (203.208.173.133) 22.517 ms 22.648 ms 22.733 ms
10 203.208.152.209 (203.208.152.209) 22.776 ms 203.208.152.205 (203.208.152.205) 24.401 ms 203.208.152.209 (203.208.152.209) 24.893 ms
11 so-3-0-0-0.plapx-cr3.ix.singtel.com (203.208.173.158) 251.946 ms so-2-0-2-0.plapx-cr3.ix.singtel.com (203.208.149.30) 218.615 ms 219.022 ms
12 ge-0-0-0-0.plapx-dr1.ix.singtel.com (203.208.149.1) 219.103 ms ge-6-0-0-0.plapx-dr1.ix.singtel.com (203.208.183.162) 190.485 ms ge-0-0-0-0.plapx-dr1.ix.singtel.com (203.208.149.1) 215.484 ms
13 paix01-sfo4.amazon.com (198.32.176.36) 198.322 ms 188.865 ms 216.023 ms
14 72.21.222.198 (72.21.222.198) 337.997 ms 338.733 ms 205.274 ms
15 72.21.222.225 (72.21.222.225) 195.085 ms 195.981 ms 209.449 ms
16 server-216-137-37-180.sfo4.cloudfront.net (216.137.37.180) 212.211 ms 198.479 ms 189.777 ms - Thanks for the info! I have a support ticket open with cloudfront and I'll update here when I know more.
- thanks Bees!
-
Just to update the thread...
I don't know if anything's changed on cloudfront but connecting from Singapore is okay now. Ping times haven't really improved though but no more onLoadErrors for me and game loads just fine now.
Pinging d3tv7e6jdw6zbr.sfo4.cloudfront.net [216.137.37.19] with 32 bytes of data:
Reply from 216.137.37.19: bytes=32 time=406ms TTL=48
Reply from 216.137.37.19: bytes=32 time=224ms TTL=48
Reply from 216.137.37.19: bytes=32 time=246ms TTL=48
Reply from 216.137.37.19: bytes=32 time=269ms TTL=48
Reply from 216.137.37.19: bytes=32 time=292ms TTL=50
Ping statistics for 216.137.37.19:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 224ms, Maximum = 406ms, Average = 287ms -
I can connect too, but I'm stuck at The Next Step because the pig is unable to load.
Here's the error message that pops up:
LOADED BUT FAILED TO FIRE COMPLETE EVENT IN 10 SECONDS: Piggy c2.glitch.bz/items/2010-09/... -
Sorry ping, any chance you could give me the output of these commands?
dig identity.cloudfront.net txt
dig resolver-identity.cloudfront.net txt
There were a typos in the ones you pasted before. Thanks! -
@Bees,
My bad! Sorry about the horrible typos. Here it is again.
ping@Starling:~$ dig identity.cloudfront.net txt
; DiG 9.7.0-P1 HEADER DiG 9.7.0-P1 HEADER - Dunno if it'll help. I'm from Singapore using Singnet but I could play! So it couldn't have happened for everyone.