tag:help.rubygems.org,2010-01-19:/discussions/problems/18425-could-not-ping-to-rubygemsorgRubyGems.org: Discussion 2018-10-18T19:51:22Ztag:help.rubygems.org,2010-01-19:Comment/338091012014-07-17T15:08:40Z2014-07-17T15:08:40ZCould not ping to 'rubygems.org'.<div><p>RubyGems does not respond to ICMP. what error does RubyGems
show?</p></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/338091012014-07-19T08:00:07Z2014-07-19T08:00:08ZCould not ping to 'rubygems.org'.<div><p>I'm seeing the following error intermittently:<br>
"ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
bad response Service Unavailable: Back-end server is at capacity
503 (<a href=
"https://api.rubygems.org/api/v1/dependencies?gems=GEMNAME&quot">https://api.rubygems.org/api/v1/dependencies?gems=GEMNAME&quot</a>;
with the referenced GEMNAME varies between a few gems</p>
<p>These errors are popping up at <em>around</em> the same points
while running spec/acceptance test runs on puppet-based server
builds (these tests install bunches of gems at several points, with
significant pauses inbetween )</p>
<p>I presume this is due to ramping up load capacity following up
from the recent updates and will try again tomorrow, but I'm
sending this heads-up now just in case.</p></div>Jon Obuchowskitag:help.rubygems.org,2010-01-19:Comment/338091012014-07-19T09:03:11Z2014-07-19T09:03:15ZCould not ping to 'rubygems.org'.<div><p>Confirmed 0200 2014-07-19:</p>
<p>ERROR: While executing gem ...
(Gem::RemoteFetcher::FetchError)<br>
bad response Service Unavailable: Back-end server is at capacity
503 (<a href=
"https://api.rubygems.org/api/v1/dependencies?gems=latinverb_chart_presenter">https://api.rubygems.org/api/v1/dependencies?gems=latinverb_chart_p...</a>)</p>
<p>➜ LatinVerb git:(master) ✗ ping rubygems.org<br>
PING rubygems.org (54.186.104.15): 56 data bytes<br>
Request timeout for icmp_seq 0<br>
Request timeout for icmp_seq 1<br>
Request timeout for icmp_seq 2<br>
Request timeout for icmp_seq 3<br>
Request timeout for icmp_seq 4<br>
Request timeout for icmp_seq 5<br>
^C --- rubygems.org ping statistics --- 7 packets transmitted, 0
packets received, 100.0% packet loss</p>
<p>➜ LatinVerb git:(master) ✗ ping google.com<br>
PING google.com (74.125.239.135): 56 data bytes<br>
64 bytes from 74.125.239.135: icmp_seq=0 ttl=56 time=4.045 ms<br>
64 bytes from 74.125.239.135: icmp_seq=1 ttl=56 time=4.618 ms<br>
^C --- google.com ping statistics --- 2 packets transmitted, 2
packets received, 0.0% packet loss<br>
round-trip min/avg/max/stddev = 4.045/4.332/4.618/0.286 ms</p>
<p>This is from my laptop in SF. How about from my VPS in NYC?</p>
<p>blankslate@dasein:~$ ping rubygems.org<br>
PING rubygems.org (54.186.104.15) 56(84) bytes of data.<br>
^C --- rubygems.org ping statistics --- 7 packets transmitted, 0
received, 100% packet loss, time 6047ms</p>
<p>blankslate@dasein:~$ traceroute !$<br>
traceroute rubygems.org<br>
traceroute to rubygems.org (54.186.104.15), 30 hops max, 60 byte
packets<br>
1 107.170.236.254 (107.170.236.254) 0.546 ms 0.641 ms 0.782 ms 2
198.199.99.233 (198.199.99.233) 0.253 ms 0.297 ms 0.290 ms 3
xe-0-4-0-17.r06.plalca01.us.bb.gin.ntt.net (129.250.203.81) 1.184
ms sjo-bb1-link.telia.net (62.115.34.17) 1.716 ms 1.705 ms 4
sea-b1-link.telia.net (80.91.253.20) 20.298 ms
ae-4.r07.snjsca04.us.bb.gin.ntt.net (129.250.4.119) 27.548 ms
26.233 ms 5 amazon-ic-302506-sea-b1.c.telia.net (213.248.84.190)
20.324 ms ae-8.r21.snjsca04.us.bb.gin.ntt.net (129.250.5.56) 62.678
ms 4.460 ms 6 ae-1.r20.sttlwa01.us.bb.gin.ntt.net (129.250.3.38)
21.633 ms 21.424 ms 205.251.225.182 (205.251.225.182) 20.317 ms 7
ae-1.r04.sttlwa01.us.bb.gin.ntt.net (129.250.5.43) 23.536 ms
ae-1.r05.sttlwa01.us.bb.gin.ntt.net (129.250.5.47) 21.347 ms
205.251.232.88 (205.251.232.88) 27.904 ms 8 205.251.232.141
(205.251.232.141) 28.017 ms 205.251.232.153 (205.251.232.153)
28.009 ms ae-0.amazon.sttlwa01.us.bb.gin.ntt.net (129.250.201.166)
19.170 ms 9 205.251.225.202 (205.251.225.202) 21.077 ms
205.251.225.160 (205.251.225.160) 19.683 ms 205.251.232.63
(205.251.232.63) 28.008 ms 10 205.251.232.62 (205.251.232.62)
28.134 ms 205.251.232.164 (205.251.232.164) 28.114 ms
205.251.232.92 (205.251.232.92) 28.488 ms<br>
11 205.251.232.140 (205.251.232.140) 32.565 ms 205.251.232.153
(205.251.232.153) 28.909 ms 205.251.232.141 (205.251.232.141)
27.190 ms<br>
12 205.251.232.157 (205.251.232.157) 28.108 ms 28.091 ms
205.251.232.165 (205.251.232.165) 28.149 ms<br>
13 205.251.232.164 (205.251.232.164) 28.117 ms 205.251.232.62
(205.251.232.62) 28.042 ms 205.251.232.169 (205.251.232.169) 28.223
ms<br>
14 205.251.232.146 (205.251.232.146) 33.807 ms * *<br>
15 205.251.232.157 (205.251.232.157) 28.321 ms * 205.251.232.151
(205.251.232.151) 29.310 ms<br>
16 * * 205.251.232.169 (205.251.232.169) 27.908 ms<br>
17 * * *<br>
18 * * *<br>
19 * * *<br>
20 * *^C</p></div>Confirmtag:help.rubygems.org,2010-01-19:Comment/338091012014-07-21T06:30:58Z2014-07-21T06:31:00ZCould not ping to 'rubygems.org'.<div><p>Following up on my message from Saturday; I am no longer
encountering the "bad response Service Unavailable: Back-end server
is at capacity 503" errors.</p></div>Jon Obuchowski