[Rubygems-developers] Running a gem server

Jim Freeze rubygems at freeze.org
Wed Jul 13 13:49:23 EDT 2005


* Hugh Sasse <hgs at dmu.ac.uk> [2005-07-13 17:40:18 +0100]:

> On Wed, 13 Jul 2005, Jim Freeze wrote:
> 
> > gem install <gemname> --source http://10.0.0.1:8808
>         [....]
> > Updating Gem source index for: http://10.0.0.1:8808
> > ERROR:  While executing gem ... (OpenURI::HTTPError)
> >     503 Service Unavailable
> 
> I can't see why this wouldn't work.  Does using -p on the gem_server
> help?  I see the line:

No. Tried that with -p 9000. No difference.
 
>  s = WEBrick::HTTPServer.new(:Port => options[:port] || 8808)
> 
> and wonder if it might possibly be read as
> 
>  s = WEBrick::HTTPServer.new((:Port => options[:port]) || 8808)
> 
> rather than
> 
>  s = WEBrick::HTTPServer.new(:Port => (options[:port] || 8808))
> 
> But surely someone would have hit that by now, and your server
> should have whinged about it anyway.
> 
> Other things, are they running the same versions [of ruby?] at each end?

Machine A:
   % ruby -v
   ruby 1.8.2 (2004-12-25) [powerpc-darwin7.7.0]
   % gem -v
   0.8.10

Machine B:
  % ruby -v
  ruby 1.8.2 (2004-12-25) [sparc-solaris2.8]
  % gem -v
  0.8.10

Also, browsing to the gem_server 10.0.0.1:8808 works just fine.

-- 
Jim Freeze


More information about the Rubygems-developers mailing list