Difference between revisions of "Yaml.rb:133: BUG Segmentation fault"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(4 intermediate revisions by the same user not shown)
Line 3: Line 3:
This means that your server does not have enough memory (RAM) for installation (GEM) to work.
This means that your server does not have enough memory (RAM) for installation (GEM) to work.


Increase RAM on your server or change server.
'''Solution: Increase RAM on your server or change server.'''
 
Is this really a solution?  Here's a real one:
https://boxpanel.blueboxgrp.com/public/the_vault/index.php/RFacebook


This often happens on cheap VPS (Virtual Private Servers).
This often happens on cheap VPS (Virtual Private Servers).
The problem is that ruby's decompresser uses over 100MB of RAM when extracting the rails and other gems. Since VPS servers have limited RAM and no virtual memory, the process fails.
----


Use '''top''' command to check it. If you have something like:
Use '''top''' command to check it. If you have something like:
Line 13: Line 20:


That means real trouble.
That means real trouble.
----
Use '''cat /proc/user_beancounters''' command. If you have something like (note '''failcnt''' at '''privvmpages'''):
        uid  resource          held    maxheld    barrier      limit    failcnt
            privvmpages      36796      65564      65536      81920        36
The failures shown in privvmpages is most likely the reason for the segmentation fault you've encountered.

Latest revision as of 16:50, 6 September 2008

/usr/lib/ruby/1.8/yaml.rb:133: [BUG] Segmentation fault

This means that your server does not have enough memory (RAM) for installation (GEM) to work.

Solution: Increase RAM on your server or change server.

Is this really a solution? Here's a real one: https://boxpanel.blueboxgrp.com/public/the_vault/index.php/RFacebook

This often happens on cheap VPS (Virtual Private Servers).

The problem is that ruby's decompresser uses over 100MB of RAM when extracting the rails and other gems. Since VPS servers have limited RAM and no virtual memory, the process fails.


Use top command to check it. If you have something like:

Mem:    131072k total,   131072k used,        0k free,        0k buffers
Swap:        0k total,        0k used,        0k free,        0k cached

That means real trouble.


Use cat /proc/user_beancounters command. If you have something like (note failcnt at privvmpages):

       uid  resource           held    maxheld    barrier      limit    failcnt
           privvmpages       36796      65564      65536      81920         36

The failures shown in privvmpages is most likely the reason for the segmentation fault you've encountered.