[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

gem command hangs with no output

Jarrod Menoube

8/29/2008 3:08:00 AM

Tried to run "gem outdated" on my CentOS 5 server. It just hung with no
response on the command line for about 10 minutes.

After that, tried "gem update passenger". I got...

Updating installed gems...
Bulk updating Gem source index for: http://gems.rub...

then nothing. It's 15 minutes and it's still just hanging.

Control-C has no effect.

Looks like I'll have to open another shell and kill it.

Any way to get gem command to work right now?

Thanks,

E
--
Posted via http://www.ruby-....
3 Answers

John Pritchard-williams

8/29/2008 11:53:00 AM

0

Hi Jarrod,

This happens to me now and then: especially on my Ubuntu box (low-spec
machine as it happens) - the whole machine can become totally
unresponsive for 5-10 minutes.

I tried killing it once, but I just made things worse. (ended up with a
force-reboot).

I don't why this happens, but in my experience just letting it run its
course was the only way of not causing damage to my system....

John

Jarrod Menoube wrote:
> Tried to run "gem outdated" on my CentOS 5 server. It just hung with no
> response on the command line for about 10 minutes.
>
> After that, tried "gem update passenger". I got...
>
> Updating installed gems...
> Bulk updating Gem source index for: http://gems.rub...
>
> then nothing. It's 15 minutes and it's still just hanging.
>
> Control-C has no effect.
>
> Looks like I'll have to open another shell and kill it.
>
> Any way to get gem command to work right now?
>
> Thanks,
>
> E

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

Jarrod Menoube

8/29/2008 5:35:00 PM

0

John Pritchard-williams wrote:
> Hi Jarrod,
>
> This happens to me now and then: especially on my Ubuntu box (low-spec
> machine as it happens) - the whole machine can become totally
> unresponsive for 5-10 minutes.
>
> I tried killing it once, but I just made things worse. (ended up with a
> force-reboot).
>
> I don't why this happens, but in my experience just letting it run its
> course was the only way of not causing damage to my system....
>
> John

Thanks for the reply. I upgraded to the latest version of gem and the
problem went away. I wonder if they changed something on the other end
and old versions of gem don't work any more.

E
--
Posted via http://www.ruby-....

deepak

9/2/2008 11:42:00 AM

0

on the rubygems FAQ page a link is there on

http://rubygems.org/read/chapter..., but the answer has been
lost.

Personally in my case flushing the cache by doing a "gem sources --
clear-all" worked.