New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault with Ruby Enterprise Edition 2011.12 #81
Comments
Specifically for me, we upgraded to 2011.12 just fine 32-bit and it was working without any problems. I recently moved to a 64-bit box, 2011.12, and now I'm getting this segfault. |
I've got this problem too, have you found some workaround of this issue ? |
I'm with the same problem. Any idea?
|
REE 2012.02 was just released which claims to have a much more stable set of MBARI patches. I've yet to try it but it may fix this segfault issue. |
REE 2012.02 doesn't fix the issue on Debian running 2.6.38.2 (x86_64) |
Same issue with |
same issue here:
ruby version (64bit):
on Scientific Linux release 6.0 (Carbon) with 64bit (SELINUX disabled) |
Same issue here:
on Ubuntu 10.04.4 LTS |
So as it stands, I'm no longer using god at all but have instead switched to Upstart. |
I'm seeing this issue, too. I have a cron job which runs periodically to check to see if god is running, and it seems to have to restart god every few hours. |
I'm also on REE 2012.02, on Fedora 8 and 11: Sometimes I see this message:
and ometimes I see this message:
|
Experiencing same issue on Centos 5.4 ( 2.6.21.7-2.fc8xen x86_64 ) using REE 2012.02 |
is anyone debugging the error? so we can try to solve the issue? ... one solution that may work is to use rvm or another tool to define which ruby you use to execute god, so you can use ruby 1.9.2 for god and ree for the other things. update: it worked for me to use 1.8 debian system ruby for god, in our linode debian server. ;) |
The only thing I've been able to find is that other libraries are having this same issue: https://github.com/fastestforward/instrumental_agent/wiki/Using-with-Ruby-Enterprise-Edition They claim to have fixed it, maybe someone can tease out the fix from their commit log? |
having the same problem. gonna try using a different ruby |
I'm also having the same issue on 3 boxes, running ubuntu 10.04 /custom/ree/lib/ruby/1.8/monitor.rb:173: [BUG] Segmentation fault |
we've also seen the gc_sweep error /custom/ree/lib/ruby/1.8/monitor.rb:173: [BUG] gc_sweep(): unknown data type 0x0(0x34a6458) |
having the same issue: hui@ubuntu:/data/god/god_config$ tail -f /var/log/god.log |
Oh the irony! I've just installed god to keep an eye on a service that periodically segfaults on me and now I find I'm bitten by the REE bug. |
I haven't been able to fix the issue; but I made a temporary bandaid using upstart. It will at least restart god when it segfaults. put this (with your correct paths) in /etc/init/god.conf (assuming your on a dist with upstart or have otherwise installed it)
|
I've ran into this as well. I'll see what I can dig up... |
Have the error like this, but I don't use god. Same for 2012.02. I use RVM. Able to run ree without this error when install it like this: CC=/usr/bin/gcc-4.4 rvm install ree Possibly, it could help someone else ... |
Same error on SUSE Linux Enterprise Server 11 SP2 and Ruby Enterprise Edition 2012.02 with god 0.12.1 on x86_64:
Maybe this has something to do with an already fixed problem: Ruby Enterprise Edition 1.8.7-2010.01 released:
Ruby Enterprise Edition 1.8.7-2012.02 released:
|
This worked for me (on opensuse 12.2): http://deadc.org/blog/2012/10/19/rvm-install-ruby-1-dot-8-7-with-gcc-4-dot-7/ rvm remove ree
export CFLAGS="-O2 -fno-tree-dce -fno-optimize-sibling-calls"
rvm install ree |
any ideas howto fix that bug? should we use just a standard Ruby with God monitoring? |
fixed by installing non-enterprise Ruby edition |
God works perfectly with previous ree versions, we have been running it for almost 2 years without problem.
After upgrading ree to ree-1.8.7-2011.12, got the following error, and god process itself disappears after starting monitored processes.
os is ubuntu Ubuntu 10.04.3 LTS
The text was updated successfully, but these errors were encountered: