ScottLiu

  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ScottLiu

  • Rank
    Junior Member
...
  1. My DNS looks OK, but there seems to be packet loss when pinging. [steam@VM_0_3_centos ~]$ ping login.kleientertainment.com PING login.kleientertainment.com (13.248.132.235) 56(84) bytes of data. 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=1 ttl=251 time=222 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=2 ttl=251 time=223 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=3 ttl=251 time=222 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=6 ttl=251 time=223 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=8 ttl=251 time=222 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=9 ttl=251 time=222 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=10 ttl=251 time=223 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=11 ttl=251 time=222 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=12 ttl=251 time=223 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=13 ttl=251 time=222 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=14 ttl=251 time=222 ms 64 bytes from ac06bdf57acc78add.awsglobalaccelerator.com (13.248.132.235): icmp_seq=15 ttl=251 time=222 ms ^C --- login.kleientertainment.com ping statistics --- 15 packets transmitted, 12 received, 20% packet loss, time 14013ms rtt min/avg/max/mdev = 222.695/222.961/223.340/0.267 ms [steam@VM_0_3_centos ~]$ ping metric.kleientertainment.com PING metric.kleientertainment.com (52.221.85.223) 56(84) bytes of data. 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=1 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=2 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=3 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=4 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=5 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=6 ttl=251 time=206 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=7 ttl=251 time=204 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=8 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=9 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=11 ttl=251 time=206 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=12 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=13 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=14 ttl=251 time=205 ms 64 bytes from ec2-52-221-85-223.ap-southeast-1.compute.amazonaws.com (52.221.85.223): icmp_seq=15 ttl=251 time=205 ms ^C --- metric.kleientertainment.com ping statistics --- 15 packets transmitted, 14 received, 6% packet loss, time 14018ms rtt min/avg/max/mdev = 204.604/205.646/206.705/0.457 ms
  2. Does anyone meet these errors? CURL ERROR: (dst.metrics.klei.com) TCP connection reset by peer ... CURL ERROR: (login.kleientertainment.com) TCP connection reset by peer ...
  3. I started a dedicated server on my CentOS server one month ago. I didn't do any changes to it and today I found it doesn't work and tells me no auth token could be found. But I have put the cluster token in the right path and checked the content.run_dedicated_servers.sh.log Thanks!