If your Mac is unable to complete the ping or traceroute to either then it will not end or not for a long time. It should give up trying after a set period. This is why it fails which seems to indicate some issue with the connection to the launcher/ patcher servers.
| HOSTS FILE |
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
| PING |
PING a1092.d.akamai.net (81.52.201.73): 56 data bytes
64 bytes from 81.52.201.73: icmp_seq=0 ttl=57 time=37.059 ms
64 bytes from 81.52.201.73: icmp_seq=1 ttl=57 time=37.370 ms
64 bytes from 81.52.201.73: icmp_seq=2 ttl=57 time=39.721 ms
64 bytes from 81.52.201.73: icmp_seq=3 ttl=57 time=35.937 ms
--- a1092.d.akamai.net ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 35.937/37.522/39.721/1.377 ms
| PING |
PING a1213.g1.akamai.net (90.84.59.169): 56 data bytes
64 bytes from 90.84.59.169: icmp_seq=0 ttl=56 time=36.589 ms
64 bytes from 90.84.59.169: icmp_seq=1 ttl=56 time=37.115 ms
64 bytes from 90.84.59.169: icmp_seq=2 ttl=56 time=38.163 ms
64 bytes from 90.84.59.169: icmp_seq=3 ttl=56 time=38.174 ms
--- a1213.g1.akamai.net ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 36.589/37.510/38.174/0.684 ms
| TRACEROUTE |
1 192.168.1.1 (192.168.1.1) 1.478 ms 1.205 ms 1.202 ms
2 80.10.125.86 (80.10.125.86) 22.648 ms 23.166 ms 22.905 ms
3 10.125.175.138 (10.125.175.138) 26.125 ms 130.475 ms 22.125 ms
4 xe-5-3-0-0.nctou202.toulouse.francetelecom.net (193.253.93.170) 21.303 ms 22.268 ms 23.096 ms
5 ae43-0.nipoi102.poitiers.francetelecom.net (193.252.160.54) 28.050 ms 28.459 ms 28.417 ms
6 81.253.184.110 (81.253.184.110) 58.009 ms 36.413 ms 40.417 ms
7 81.52.201.73 (81.52.201.73) 38.394 ms 36.695 ms 35.945 ms
| TRACEROUTE |
1 192.168.1.1 (192.168.1.1) 1.329 ms 1.092 ms 1.117 ms
2 80.10.125.86 (80.10.125.86) 23.723 ms 50.563 ms 22.352 ms
3 10.125.175.202 (10.125.175.202) 21.746 ms 22.311 ms 22.270 ms
4 xe-2-2-1-0.nctou201.toulouse.francetelecom.net (193.253.93.190) 22.198 ms 22.967 ms 21.797 ms
5 ae43-0.nipoi101.poitiers.francetelecom.net (193.252.160.49) 30.407 ms 31.533 ms 28.485 ms
6 ae40-0.nipoi102.poitiers.francetelecom.net (193.252.160.46) 28.261 ms 28.541 ms 32.797 ms
7 81.253.184.110 (81.253.184.110) 38.458 ms 41.323 ms 40.276 ms
8 tengige0-8-0-4.auvtr1.aubervilliers.opentransit.net (193.251.128.234) 36.793 ms 38.869 ms 41.176 ms
9 90.84.59.169 (90.84.59.169) 36.469 ms 36.218 ms *
Think it's because on the traceroute it wont stop at the last hop (usually blocked from ping for security) so just keeps going. It was noted a while ago on this post.I guess I wasn't clear, I apologize. The game consultant doesn't work after leaving it over night as well... I can login and play the game just fine with the exception of the horrible client crashing. traceroute and its dependant ping are both able to reach the hosts just fine with sub 30ms latency. The math doesn't add up for the issue to be simply hosts unreachable.
Yes, thank you. It didn't come up when I switched it off though, it came up when I switched it back. The repair completed successfully and of course game still crashes, though I entertained support's odd request anyway.Do you have the Repair options now in the Launcher? Usually switching off Auto Update will make it appear as above.
Well, like I said it's not completely functioning anyhow as it is and really not much use for it. They tend to just ask for it as it works fine for PC and they don't understand it pretty much broken on the Mac version.I have little faith that the game consultant will work unfortunately. watching the processes running, I never see any traceroute called in lsof, activity monitor or dtruss and the log file hangs withDo you have the Repair options now in the Launcher? Usually switching off Auto Update will make it appear as above.
"Version:1.0
| SYSTEM PROFILER |
"
I don't have the time to debug any further though, they will just have to do proper troubleshooting to figure out why it wont launch... though Im positive that was a stall tactic.
Game\x20C 3147 xxxxxxxxxxx 5u IPv4 0xf934f727ebfbd3d 0t0 TCP localhost:65385 (LISTEN) Game\x20C 3147 xxxxxxxxxxx 27u IPv4 0xf934f72854f3d3d 0t0 TCP 192.168.1.10:65431->ec2-54-217-220-134.eu-west-1.compute.amazonaws.com:http (CLOSED) Game\x20C 3147 xxxxxxxxxxx 29u IPv4 0xf934f72854f3d3d 0t0 TCP 192.168.1.10:65431->ec2-54-217-220-134.eu-west-1.compute.amazonaws.com:http (CLOSED)
Oh I can To be fair I have mostly had good intentioned help from ESO Support and before the crush of launch they answered fast and would pass it up quite quickly and got a lot of factual details. It's been slower since though my last two tickets were resolved within a day which is reasonable including not being able to sign in to forum@Moonraker you wouldnt believe how many techs have actually asked for that and msinfo output =P in the same ticket where I can scroll up and show me responding to the first guy that its a mac and doesnt have it... smh