I’ve installed Ruby 1.8.6 and Rubygems 1.1.1 in my VPS hosting account
on eApps.com. I’ve tried to install Rails several times, without
success. I then went through the following sequence:
gem install rails --include-dependencies
INFO: gem install -y is now default and will be removed
INFO: use --ignore-dependencies to install only the gems you list
Updating metadata for 476 gems from http://gems.rubyforge.org/
…
complete
Bulk updating Gem source index for: http://gems.rubyforge.org/
Terminated
gem install rails --include-dependencies
INFO: gem install -y is now default and will be removed
INFO: use --ignore-dependencies to install only the gems you list
Bulk updating Gem source index for: http://gems.rubyforge.org/
Successfully installed rake-0.8.1
Successfully installed activesupport-2.1.0
Successfully installed activerecord-2.1.0
Successfully installed actionpack-2.1.0
Successfully installed actionmailer-2.1.0
Successfully installed activeresource-2.1.0
Successfully installed rails-2.1.0
7 gems installed
Installing ri documentation for rake-0.8.1…
Installing ri documentation for activesupport-2.1.0…
RDoc failure in lib/active_support/core_ext/class/removal.rb at or
around line 37 column 19
Before reporting this, could you check that the file
you’re documenting compiles cleanly–RDoc is not a
full Ruby parser, and gets confused easily if fed
invalid programs.
Exception NameError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ command_manager.rb:133 - uninitialized constant Gem::Commands::InstallCommand Exception Gem::LoadError’ at /usr/local/lib/ruby/site_ruby/1.8/
rubygems.rb:523 - Could not find RubyGem sources (> 0.0.1)
Exception EOFError' at /usr/local/lib/ruby/1.8/net/protocol.rb:133 - end of file reached Exception EOFError’ at /usr/local/lib/ruby/1.8/net/protocol.rb:120 -
end of file reached
Bulk updating Gem source index for: http://gems.rubyforge.org/
Killed
Is it possible that there is a process running on the server that is
detecting high processor utilization due to the gem install and
killing the gem process automatically?
Maybe you can run tail -f /var/log/messages in a separate terminal
window and then run the gem install in another window for clues as to
what is causing the gem process to get killed.
I’ve installed Ruby 1.8.6 and Rubygems 1.1.1 in my VPS hosting account
on eApps.com. I’ve tried to install Rails several times, without
success. I then went through the following sequence:
If the problem was the documentation then you’re probably ok actually.
The --no-rdoc option will stop gem generating the rdoc for the gems.
Have you tried running your app?
I installed the latest rubygems without using rubygems itself and that
fixed the out of memory problems. Here’s how to do that:
I downloaded rubygems 1.2.0 from www.rubyforge.org and untarred it.
I cd’d into the directory and ran ruby setup.rb
That installed rubygems 1.2.0 for me.
After a little more investigation, my /var/log/messages shows my gem is
getting killed by the oom_killer because it’s using up all my memory.
Can I install rubygems 1.2.0 without using rubygems itself? And will
that
replace rubygems 1.1.1 or install alongside it? What are the issues
concerning that?
Thanks for your help.
On Sun, Aug 31, 2008 at 8:11 AM, Frederick C. < [email protected]> wrote:
Killed
wrote:> Is it possible that there is a process running on the
If rubygems is getting killed because of compilations using too much
CPU (which can peg a CPU), I would get concerned that hosting Rails is
going to also prove frustrating obviously depending on the
configuration of their(your hosts’) quota processes. Definitely you
should look at mod_rails to slim down your memory usage before you go
too far down this road. As they might be even more restrictive on
memory than CPU. Lastly, get ready to run something in cron to keep an
eye on your Rails app and restart if your hosting provider kills off
processes sometimes.
H
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
I may be very wrong.