Rubygems down?

ruby-talk
1

Is it a rubygems problem or an error of mine ? For two days now :

C:\Documents and Settings\Michel>gem update
Updating installed gems
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
    SocketError: getaddrinfo: H¶te inconnu.
(http://rubygems.org/latest_specs.4.8.gz)

C:\Documents and Settings\Michel>gem sources --list
*** CURRENT SOURCES ***

http://rubygems.org/

···

--
Posted via http://www.ruby-forum.com/.

2

It's not RubyForge that is down, but the server (production.s3.etc)
that hosts the latest_specs file.

Assuming "s3" refers to AWS S3, there are no outages, either.

···

On Fri, Apr 29, 2011 at 9:55 AM, Michel Demazure <michel@demazure.com> wrote:

Is it a rubygems problem or an error of mine ? For two days now :

--
Phillip Gawlowski

Though the folk I have met,
(Ah, how soon!) they forget
When I've moved on to some other place,
There may be one or two,
When I've played and passed through,
Who'll remember my song or my face.

3

Can you browse rubygems.org and download gems from the browser?

Are you or were you behind a proxy?

If so, please use --http-proxy with gem install:

gem install foo --http-proxy=http://user:pass@server:port/

Get the proxy information from your current browser.

···

On Apr 29, 4:55 am, Michel Demazure <mic...@demazure.com> wrote:

Is it a rubygems problem or an error of mine ? For two days now :

C:\Documents and Settings\Michel>gem update
Updating installed gems
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
SocketError: getaddrinfo: H¶te inconnu.
(http://rubygems.org/latest_specs.4.8.gz\)

--
Luis Lavena

4

Phillip Gawlowski wrote in post #995748:

It's not RubyForge that is down, but the server (production.s3.etc)
that hosts the latest_specs file.

Thx Phillip.
_md

···

--
Posted via http://www.ruby-forum.com/\.

5

Luis Lavena wrote in post #995758:

···

On Apr 29, 4:55am, Michel Demazure <mic...@demazure.com> wrote:

Are you or were you behind a proxy?

Thanks for your help, Luis. I am at home, no proxy.

Actually, it was a transient error somewere on the server. I just waited
for the next day and tried again, successfully.

--
Posted via http://www.ruby-forum.com/\.