I have run into this error 5 or 10 times over the past few years and have never found a clear answer to this problem. Here is the error:
$ rake db:migrate
/usr/lib/ruby/gems/1.8/gems/libxml-ruby-0.9.5/lib/libxml_ruby.bundle: [BUG] Bus Error
ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin9.7.0]
Abort trap
The app I am running this in is using RMagick.
I have run into this problem when installing ImageMagick a while ago, and when installing Nokogiri, and when installing MySQL. For Nokogiri it was because I needed a more recent version of libxml. What are your thoughts on this? Any fixes? How can I check the version of RMagick the project is loading?
I am on a Mac, 10.5.8.
Thanks for the help,
Lance
I hit this issue running a worker in resque after upgrading Ruby from 1.8.6 to 1.8.7:
$ QUEUE=* rake resque:work
(in /Users/kimball/pulse)
/usr/local/lib/ruby/1.8/openssl/ssl-internal.rb:30: [BUG] Bus Error
ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-darwin9.8.0]
Abort trap
Found this, but pretty much just says upgrade to 1.9.1:
http://redmine.ruby-lang.org/issues/show/405
If anyone knows how to fix it in 1.8.7, I'd be grateful.
Kimball
Related
I have CentOS6 on which I have configured puppet server. but Whenever I try to execute ant puppet command it fails with ruby issue. see the output for puppet --version
-bash-4.1# puppet --version
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/json-1.8.3/lib/json/ext/parser.so: [BUG] Segmentation fault
ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]
Aborted (core dumped)
Tried re-installing puppet and ruby but no luck.
Try I had a similar issue, and did a few things and it was fixed before I knew which one fixed it, but try this:
gem update --system
yum install ruby-json
Good luck!
Your Ruby 1.8.7 is trying to use a 1.9.3 gem for some reason.
This can be tricky to get right. In your shoes, I would check if I can
get rid of ruby1.8 altogether
make ruby1.9 the default Ruby on the system
make sure that Puppet always uses ruby1.9
Specifics depend heavily on the way Ruby and Puppet were actually installed.
I am installing a new Heroku app for Rails 3.1, Ruby 1.9.2. The problem is in doing 'heroku db:push' to populate the database (which has been duly schematized--the only problem now is getting it some data). It fails with the following report:
/Users/upstill/.rvm/gems/ruby-1.9.2-p290/gems/sqlite3-1.3.5/lib/sqlite3/sqlite3_native.bundle: [BUG] Segmentation fault
ruby 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin11.0]
Abort trap: 6
This is puzzling for two reasons: one, I am using a postgresql database both locally and on heroku (duly declared in config/database.yml). And two, where has ruby 1.8.7 got to do with anything? rvm is set up for 1.9.2, it's on my path, and yet heroku is trying to run it? What gives?
Thanks,
Steve Upstill
Had this problem as well, it was extremely annoying but eventually I got it to work. I had the toolbelt installed but it started working once I did this:
gem install heroku
sudo gem install taps
Yes, the toolbelt is already installed but I think this really fixed it.
Plenty of people are having this problem, you're not alone.
Hope this helps (:
Your code is trying to run the 1.9.2 version of SQLite using Ruby 1.8.7.
I would suggest switching to 1.9.2 before trying your push.
rvm use 1.9.2-p290
heroku db:push
Ideally you want to be switching to 1.9.2 full stop.
I have the following problem and whatever I try, nothing helps. I hope someone could help me with this.
I have a redhat server and I'm trying to install redmine on it. Redmine needs Ruby >= 1.8.7 to run so I installed it and when I execute ruby -v in the console it says I have version 1.8.7 (so that's great)
[root#vms redmine]# ruby -v
ruby 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
But when i try to install the passenger gem I need to run redmine on Apache it says I don't have ruby 1.8.7
[root#vms redmine]# gem install passenger
ERROR: Error installing passenger:
rake requires Ruby version >= 1.8.6
Does anyone know how this can be fixed?
You need newer ruby, you have patchlevel 0, try to get patchlevel 173 at least.
RVM can help you.
Using vendor build ruby packages is an exercise in frustration.
For anything with ruby it's easier just to use RVM and build a virtual environment. You can then build exactly what you need and have an environment you can replicate reliably. Also you won't end up clobbering your vendor's Ruby install.
I am trying to run this project https://github.com/eLobato/cartodb-rb-client but apparently either my rvm is messed up or pg has a terrible bug.
This is the error trace
/usr/bin/ruby1.8 -S bundle exec rspec "./spec/model/data_spec.rb" "./spec/model/metadata_spec.rb" "./spec/model/scopes_spec.rb" "./spec/client_spec.rb"
/home/daniel/.rvm/gems/ruby-1.9.2-p290#cartodb-rb-client/gems/pg-0.11.0/lib/pg_ext.so: [BUG] Segmentation fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
Aborted
rake aborted!
ruby -S bundle exec rspec "./spec/model/data_spec.rb" "./spec/model/metadata_spec.rb" "./spec/model/scopes_spec.rb" "./spec/client_spec.rb" failed
Tasks: TOP => spec
(See full trace by running task with --trace)
The Segmentation fault line really bugs me a lot because I tried to reinstall pg with no avail. I am running Ubuntu 11.10 and I have installed both ruby 1.9.2 and 1.8.7
Any clue?
I had this error too. Fixed it by removing all versions of Ruby installed on my system, then re-installing 1.9.3
Like so:
$ rvm remove all
$ rvm install ruby-1.9.3-p392
You're running a system Ruby 1.8.7 interpreter, but somehow loading a pg gem installed under Ruby 1.9.2 installed via rvm.
Ruby 1.8.7 and 1.9.2 have substantially different ABIs, so their extensions are not interchangeable.
For me it seemed to be the version of the pg gem that was in my Gemfile.lock. I had 0.13.2 in there, and it just didn't seem to work on Ruby 1.9.3. I ran bundle update pg and got 0.14.0, and then things started working.
Segmentation fault is, when program is accessing memory, which kernel don't expect (out of index, out of memory allocated block etc.).
What do you see, when you try:
ruby -S bundle --trace exec rspec "./spec/model/data_spec.rb" "./spec/model/metadata_spec.rb" "./spec/model/scopes_spec.rb" "./spec/client_spec.rb"
as backtrace advice to you?
I have a very very weird problem. My rvm setup is ruby enterprise edition (ree 2011-02-18 patchlevel 334), it is set to be the default (rvm use ree --default). I am on rvm 1.6.13 and on a rails 3 project.
Now: once i try to run rails s, rails c, or any rake command I get the following:
/Users/florianvallen/.rvm/gems/ree-1.8.7-2011.03#flats/gems/mysql2-0.2.7/lib/mysql2/mysql2.bundle: [BUG] Segmentation fault
ruby 1.8.7 (2011-02-18 patchlevel 334) [i686-darwin10.4.0], MBARI 0x6770, Ruby Enterprise Edition 2011.03
Abort trap
which ruby is: ~/.rvm/rubies/ree-1.8.7-2011.03/bin/ruby
The weird thing is that i can resolve that with rvm use ree
which tells me Using /Users/florianvallen/.rvm/gems/ree-1.8.7-2011.03
After that everything works. Now, one might think that putting rvm use ree in your ~/.profile would at least solve the problem, but when i switch directories with cd .. and enter the rails project again, I get the same thing, [Bug] Segmentation fault...
Does anyone have an idea why this is like that?
Any help is highly appreciated, thank you!
The issue has been solved as the installed gems werent in the correct gemset. weirdly the gemset has not been created when switching to the directory even though it has been defined by the .rvmrc in that directory.
Removing and installing the gemset again has solved the issue.
Are you sure the gems you installed with your rails project were installed under ree? The gems have C extensions which are dependent on your ruby version which is probably your problem. Remove all of your gems and rebundle/reinstall them under rvm ree.