I wanted to make use of the new Rails 2.1 features for my app. I have
everything running and mostly tested in development, but I can't get
Rails 2.1 (from 2.0.2) installed on my test/staging environment. My
test env is a 256M slice at SliceHost. My production envs are 512M
and 1G slices, but they installed just fine. All envs are CentOS 5.1.
The test server output is:
sudo gem update rails
Bulk updating Gem source index for: http://gems.rubyforge.org/
Updating metadata for 182 gems from http://gems.github.com/
......................................................................................................................................................................................
complete
Bulk updating Gem source index for: http://gems.rubyforge.org/
After that, it hangs up. I just let it run for several hours thinking
that swapping was slowing it down. Top shows gem still running and
using up >200M of Res memory. I also tried removing all the rails
gems (activeresource, etc.) and did a gem install rails, but I get the
same problem.
The gem version is 1.1.1.
Anyone successfully installed rails 2.1 on a smaller environment? Any
suggestions on what I might have to do to get this installed?
I wanted to make use of the new Rails 2.1 features for my app. I have
everything running and mostly tested in development, but I can't get
Rails 2.1 (from 2.0.2) installed on my test/staging environment. My
test env is a 256M slice at SliceHost. My production envs are 512M
and 1G slices, but they installed just fine. All envs are CentOS 5.1.
The test server output is:
sudo gem update rails
Bulk updating Gem source index for: http://gems.rubyforge.org/
Updating metadata for 182 gems from http://gems.github.com/
......................................................................................................................................................................................
complete
Bulk updating Gem source index for: http://gems.rubyforge.org/
That bit of gems can be a bit memory hungy. I think there is an
option which controls the size of the chunks it uses while bulk
updating, which should reduce usage.
If not, just downloading the gem files, copying onto the slice and
just installing from those should work.
I wanted to make use of the new Rails 2.1 features for my app. I have
everything running and mostly tested in development, but I can't get
Rails 2.1 (from 2.0.2) installed on my test/staging environment. My
test env is a 256M slice at SliceHost. My production envs are 512M
and 1G slices, but they installed just fine. All envs are CentOS 5.1.
Yeah,
this is down to gems using too much ram for a 256mb slice.
had the same problem myself, also with slicehost.
luckily there's a solution involving killing the gems source list and
stuff.
I tried everything in the slicehost forum, but the only thing I could
get to work was to downgrade gem from 1.1.1 to 1.0.1. Once I did that,
I was able to do the install as long as I didn't install the docs as
well.
