My Rails application crashes intermittently with the following message:
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/multibyte/utils.rb:52: [BUG] gc_sweep(): unknown data type 0x0(0xbdc2ca0)
ruby 1.8.7 (2009-12-24 patchlevel 248) [i686-linux], MBARI 0x8770, Ruby Enterprise Edition 2010.01
I am running the app on Nginx / Passenger.
Ruby 1.8.7 Enterprise Edition 2010.10, Rails 2.3.5, Ubuntu 9.10 32bit.
Does anybody have an idea how to fix this?
I had to switch back to Ruby MRI. It is a temporary solution though. Hopefully, this problem will be fixed in the next release of REE.
try opening an issue at:
http://github.com/FooBarWidget/rubyenterpriseedition187-248/issues
Related
I'm configuring my first VPS for my first ruby on rails app that I´m soon deploying to the web.
I'm following this documentation https://gorails.com/deploy/ubuntu/16.04
it is going greate, but I just realised that my version of Ruby is ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin15] and the recommended for the setup is ruby version 2.3.1.
So do I have to update the ruby version on my computer to 2.3.1 or is it ok to deploy an app build on ruby 2.2.3 to an server running version 2.3.1.
This might be a stupid question, but I just want to be sure because I lack experience and I´m setting up VPS for the first time.
p.s
The App soon to deployed is built in rails 4.2.5
It is totally fine if you use Ruby 2.2.3 in this circumstance because there's not much difference between Ruby 2.2.3 and 2.3.1, they are all minor versions of Ruby 2.0.0. In addition, Rails 4.2.5 works normally with both of them.
I'm really new to coding so please pardon my inexperience.
I'm following Michael Hartl's tutorial, and I'm stuck on the part where you're supposed to make a server.
The instruction is to simply type:
$ rails server
The error message I'm getting is:
/Users/name/.rvm/gems/ruby-1.9.3-p429/gems/sqlite3-1.3.5/lib/sqlite3/sqlite3_native.bundle: [BUG] Segmentation fault
ruby 1.8.7 (2012-02-08 patchlevel 358) [universal-darwin12.0]
I'm confused as to why it says ruby 1.8.7 even though i'm using 1.9.3. Please help me fix this problem. I'm a complete beginner so please keep it simple.
you probably didn't bundle your gem before running your server. Try
bundle install
then run rails s
After upgrading my Ruby to 1.9.3-p429, I tried to start the Rails server. It told me rails was not installed so, I boldly did a 'gem install rails'. Now when I try to start the server, I'm getting this:
andrunix#amp-laptop~/code/madrilla$ rails s
/Users/andrunix/.rvm/gems/ruby-1.9.3-p429/gems/mysql2-0.3.11/lib/mysql2/mysql2.bundle: [BUG] Segmentation fault
ruby 1.8.7 (2012-02-08 patchlevel 358) [universal-darwin12.0]
Abort trap: 6
I have no idea why that says, "ruby 1.8.7" in that output. Perhaps that's a clue to my problem.
But anyway, super frustrated at this point.
And by the way, this is on OS X.
Help me please!
Try to set the version you've installed as the default for your whole system:
rvm --default use ruby-1.9.3-p429
I'm trying to run my applications under Passenger 3.0.2 on Mac OSX 10.6.4 with Rails 2.3.8 and 3.0.4. Using Ruby EE v2011.01. And Nginx.
I have completed this successfully on my laptop, and on a Redhat server. However, on my Mac Pro I am getting the following on both apps:
Passenger encountered the following error:
The application spawner server exited unexpectedly: Unexpected end-of-file detected.
Nginx log file shows a segmentation fault:
/opt/ruby-enterprise-1.8.7-2011.01/lib/ruby/gems/1.8/gems/passenger-3.0.2/lib/phusion_passenger/utils.rb:708: [BUG] Segmentation fault
ruby 1.8.7 (2010-12-23 patchlevel 330) [i686-darwin10.4.0], MBARI 0x6770, Ruby Enterprise Edition 2011.01
I KNOW this has to be some gem issue. Unfortunately Passenger is not reporting it, and I have it's log level set to 3.
I have seen a few logging issues in Passenger that have caused me some headaches. I'm not complaining, it's free and it's fast. But I don't know how to get past this one.
Looks like some kind of Ruby bug to me. Try 1.9? It looks like the Ruby core developers give 1.9 more attention than 1.8 these days.
I got same problem with Ruby Enterprise (ree) 1.8.7-2011.02 and install Passenger that bundle with it.
Server is OpenSuSe 11.x
Ruby Enterprise 1.8.7-2011.02
Passenger 3.0.2
/var/log/apache2/error_log show looks like this
*** glibc detected *** Passenger ApplicationSpawner: /srv/www/apps/xxxxxx/current: munmap_chunk(): invalid pointer: 0x0000000000ccd400 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x73226)[0x7f40d5d1e226]
/lib64/libnsl.so.1(+0xfd4a)[0x7f40d40f3d4a]
/lib64/libpthread.so.0(pthread_once+0x53)[0x7f40d5a9a943]
/lib64/libnsl.so.1(_nsl_default_nss+0x21)[0x7f40d40f3e61]
/lib64/libnss_compat.so.2(_nss_compat_initgroups_dyn+0x594)[0x7f40d4301de4]
/lib64/libc.so.6(+0x9cc1b)[0x7f40d5d47c1b]
/lib64/libc.so.6(initgroups+0x6c)[0x7f40d5d47e7c]
/opt/ruby-enterprise-1.8.7-2011.02/lib/ruby/gems/1.8/gems/passenger-2.2.15/ext/phusion_passenger/native_support.so(+0xf48)[0x7f40d4b5af48]
so, solution is install Passenger gem to your MRI Ruby.
sudo gem install passenger
sudo passenger-install-apache2-module
Last report of passenger should give you apache's configuration to MRI ruby /usr/bin/ruby
It is slower but till new patch is out, this is only solution for me.
Had the same error (on ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.5.0],
passenger 3.0.2, Mac OS X 10.6.6 dual Quad-Core) and reverting to Passenger 2.2.15 also worked for me. Weird! Thank you.
Backing off to Passenger 2.2.15 fixed my problem. Note that this error only occurs on Mac OS X 10.6.4 on my Mac Pro dual quad core CPU machine, NOT on my MacBook Pro laptop running the same version of the OS.
I have problems using passenger standalone with a debugger. If I try this:
passenger start --debugger
I get this error:
Your version of ruby-debug is too old. Please upgrade to the latest version.
My Ruby is: ruby 1.8.7 (2010-04-19 patchlevel 253) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2010.02
Ruby debug:
ruby-debug (0.10.3)
ruby-debug-base (0.10.3)
So, has anyone successfully used Passenger 3.0 with a debugger?
It isn't supposed to work, the flag was experimental but we forgot to remove it for 3.0.0, that's why it isn't documented. It'll be removed for 3.0.1.
You can run a debugger in Passenger by using rack-debug
It works by having a client connect to the Passenger process at the breakpoints you set. A bit more complicated than using Thing/Mongrel with a debugger. But pretty simple to setup.