Forum: Ruby gem problems: install "bulk updating..." gets oom killed: no memory.

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
itsastickup (Guest)
on 2009-04-30 15:35
(Received via mailing list)
Hello,

ruby 1.8.4, gems 1.0.1

On a 256MB VPS my gem installs blow up. I had this problem when the
VPS was at 128MB, then upgraded to 256 and it went away. But now it's
happening again. It doesn't matter how many processes I kill to make
free memory I still run out. This time around I can't justify
upgrading the VPS.

I also can't update the gem system in case this is a bug that's been
fixed: the same thing happens.

Any help appreciated.
Farrel L. (Guest)
on 2009-04-30 15:44
(Received via mailing list)
2009/4/30 itsastickup <removed_email_address@domain.invalid>:
> Hello,
>
> ruby 1.8.4, gems 1.0.1

That version of gems is really old. The version on my box is 1.3.1. I
think there are some backwards incompatibilities between the newer and
older versions which can cause issues such as what you describe. See
if upgrading to a newer gems version helps.

Farrel
itsastickup (Guest)
on 2009-04-30 16:00
(Received via mailing list)
>
> > Hello,
>
> > ruby 1.8.4, gems 1.0.1
>
> That version of gems is really old. The version on my box is 1.3.1. I
> think there are some backwards incompatibilities between the newer and
> older versions which can cause issues such as what you describe. See
> if upgrading to a newer gems version helps.

Thanks for that.

Is there a way of upgrading without the memory problems?  I've tried
gem install <url to 1.3.1>

but it still insists on "Bulk updating..." and dies.
itsastickup (Guest)
on 2009-04-30 18:30
(Received via mailing list)
> Is there a way of upgrading without the memory problems?  I've tried
> gem install <url to 1.3.1>
>
> but it still insists on "Bulk updating..." and dies.

So the solution seems to be to use the -B option to avoid the bulk
update feature. It then gets each one at a rate of 7 a second for
22,000: I had to wait an hour, but the following worked:

gem update --system -B 100000000
Eric H. (Guest)
on 2009-04-30 22:54
(Received via mailing list)
On Apr 30, 2009, at 07:30, itsastickup wrote:
>> Is there a way of upgrading without the memory problems?  I've tried
>> gem install <url to 1.3.1>
>>
>> but it still insists on "Bulk updating..." and dies.
>
> So the solution seems to be to use the -B option to avoid the bulk
> update feature. It then gets each one at a rate of 7 a second for
> 22,000: I had to wait an hour, but the following worked:
>
> gem update --system -B 100000000

You can also upgrade my manually upgrading, see the last set of
install instructions here:

http://rubyforge.org/forum/forum.php?forum_id=31661
This topic is locked and can not be replied to.