AWS – 弹性负载均衡器无法处理请求

我对AWS和全世界都是陌生的 。 我的问题在这里是请求到AWS服务器。 我有一个服务器staging-storage.zazzercode.co指向下面的DNS's与各自的负载平衡器,

 s-storage-us-west-2-483191837.us-west-2.elb.amazonaws.com => s-storage-us-west-2 s-storage-us-east-1-1318227839.us-east-1.elb.amazonaws.com => s-storage-us-east-1 

我住在东方世界 。

点0

我将实例大小从t1.micro升级到了m3.medium希望能够得到解决。

要点1

当使用主机名'staging-storage.zazzercode.co'请求服务器时,我得到一个curl请求中的错误,

 curl: (6) Couldn't resolve host 'staging-storage.zazzercode.co' 

根据man curl6是,

 6 Couldn't resolve host. The given remote host was not resolved. 

第2点

它有时告诉我

 HTTP/1.1 100 Continue HTTP/1.1 504 Gateway Timeout Content-length:0 

这是在这里logging – Elastic Load Balancing疑难解答:错误消息build议

  1. 负载均衡器处理请求的容量不足(暂时问题)
  2. 实例closures到ELB的连接。

第3点

经过几次尝试后,它会作出适当的回应。 我的团队其他人也面临同样的问题。

第4点

当我ping主机名时,它挂起

 $ ping staging-storage.zazzercode.co PING s-storage-us-west-2-483191837.us-west-2.elb.amazonaws.com (54.199.188.111) 56(84) bytes of data. 

第5点

我可以正确地ssh这两个实例。

第六点

nslookup zazzercode.co给我,

 $ nslookup -type=NS zazzercode.co Server: 127.0.1.1 Address: 127.0.1.1#53 Non-authoritative answer: zazzercode.co nameserver = ns-1605.awsdns-08.co.uk. zazzercode.co nameserver = ns-1302.awsdns-34.org. zazzercode.co nameserver = ns-510.awsdns-63.com. zazzercode.co nameserver = ns-692.awsdns-22.net. Authoritative answers can be found from: 

nslookup staging-storage.zazzercode.co给我,

 $ nslookup -q=NS staging-storage.zazzercode.co Server: 127.0.1.1 Address: 127.0.1.1#53 Non-authoritative answer: staging-storage.zazzercode.co canonical name = s-storage-us-west-2-483191837.us-west-2.elb.amazonaws.com. Authoritative answers can be found from: us-west-2.elb.amazonaws.com origin = ns-332.awsdns-41.com mail addr = awsdns-hostmaster.amazon.com serial = 1 refresh = 7200 retry = 900 expire = 1209600 minimum = 60 

第7点

zazzercode.co给我 ,

 $ dig TXT ns-692.awsdns-22.net _amazonses.zazzercode.co ; <<>> DiG 9.9.2-P1 <<>> TXT ns-692.awsdns-22.net _amazonses.zazzercode.co ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33984 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;ns-692.awsdns-22.net. IN TXT ;; Query time: 46 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Thu Jul 24 11:54:31 2014 ;; MSG SIZE rcvd: 49 ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30277 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_amazonses.zazzercode.co. IN TXT ;; AUTHORITY SECTION: zazzercode.co. 900 IN SOA ns-692.awsdns-22.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 ;; Query time: 173 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Thu Jul 24 11:54:31 2014 ;; MSG SIZE rcvd: 137 

我怀疑这是LoadBalancer问题。 有没有办法检查LoadBalancer是否正在删除连接? 或者这里有什么问题?

如果需要,我会提供更多细节。

zazzercode.co是虚构的名字在这里隐藏实际名称,直到这一点,实际是soothsayer.co其他一切保持不变)

参考

EC2弹性负载平衡器DNS和路由问题