# Can't get console to work in rails **URL:** \ **Category:** Rails\ **Created:** [April 2, 2009, 6:22pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572 "2009-04-02T18:22:01Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 2, 2009, 6:22pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/1 "2009-04-02T18:22:01Z")
Hi, i can’t get the console to work in rails . everything else seems to work fine. I think this happened after i updated to the most recent version of rails or maybe it has to do with postgres (which I’m also very new to as I usually use mysql) This is the error I get: ~/web\_sites/new\_early$ruby script/console Loading development environment (Rails 2.2.2) /usr/local/lib/ruby/gems/1.8/gems/postgres-0.7.9.2008.01.28/lib/postgres.bundle: [BUG] Bus Error ruby 1.8.4 (2005-12-24) [i686-darwin8.8.3] Abort trap any ideas? regards caspar ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 2, 2009, 10:52pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/2 "2009-04-02T22:52:27Z")
On Apr 2, 11:22 am, Cccc Bb [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > [BUG] Bus Error > ruby 1.8.4 (2005-12-24) [i686-darwin8.8.3] > > Abort trap > > ## any ideas? regards caspar > > Posted viahttp://www.ruby-forum.com/. Try installing the “pg” gem instead. I’ve had more luck with it than the older postgres gem. Whoever’s been maintaining the postgres gems, I think them for their work, but keeping track of what gem you’re supposed to use has been confusing (at least for me). Jeff [purpleworkshops.com](http://purpleworkshops.com) ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 3, 2009, 6:55am UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/3 "2009-04-03T06:55:31Z")
Yes, a second to that. I was doing a clean install of a full stack into a VM the other day with the intent of getting a little more familiar with Postgres, and it must me about 45 minutes to sort out which gem was the right one to use. Went with pg in the end, and it seems to have worked out fine, but your mileage may vary as you are still using Ruby 1.8.4. Would be cool if someone directly involved with either one of these gems’ maintenance could slap together a blog post about which gem to use in which situation and post the link to this list and all the other usual locations. I’m sure I’m we’re not the only ones who have this question. ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 4, 2009, 6:42pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/4 "2009-04-04T18:42:15Z")
Hi , thanks for the help. I uninstaled the postgres gem and installed the pg gem but still have the same error: ~/web\_sites/new\_early$ruby script/console Loading development environment (Rails 2.2.2) /usr/local/lib/ruby/gems/1.8/gems/pg-0.8.0/lib/pg.bundle: [BUG] Bus Error ruby 1.8.4 (2005-12-24) [i686-darwin8.8.3] Abort trap any other ideas? really struggling without the console. regards caspar ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 4, 2009, 6:55pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/5 "2009-04-04T18:55:48Z")
> ruby 1.8.4 (2005-12-24) [i686-darwin8.8.3] Well your Ruby version is like 3.5 years old. Time to update? ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 4, 2009, 7:59pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/6 "2009-04-04T19:59:40Z")
Fernando P. wrote: > > ruby 1.8.4 (2005-12-24) [i686-darwin8.8.3] > > Well your Ruby version is like 3.5 years old. Time to update? updating with macports as we speak… ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 4, 2009, 10:45pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/7 "2009-04-04T22:45:47Z")
Cccc Bb wrote: > Fernando P. wrote: > > > > ruby 1.8.4 (2005-12-24) [i686-darwin8.8.3] > > > > Well your Ruby version is like 3.5 years old. Time to update? > > updating with macports as we speak… Okay in the end macports was more trouble than good but installed ruby 1.8.7 from source now console works fine. Thanks for all the help. regards c ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 6, 2009, 6:00pm UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/8 "2009-04-06T18:00:51Z")
Fernando P. wrote: > > Okay in the end macports was more trouble than good but installed ruby > > 1.8.7 from source now console works fine. Thanks for all the help. > > regards > > c > > Why more trouble? Usually macports is cool. However for Ruby I find it > easier to compile it manually. Macports was trouble because I already had everything installed, rails, gems , lighttpd etc. elsewhere and I was getting lots of grief from messed up PATH. However it did look very useful and next time I do a clean install I’m going to have another crack at using it. ---
**Author:** ![itchy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/b3f665/32.png) [@itchy](https://www.ruby-forum.com/u/itchy)\ **Post date:** [April 6, 2009, 10:40am UTC](https://www.ruby-forum.com/t/cant-get-console-to-work-in-rails/164572/9 "2009-04-06T10:40:46Z")
> Okay in the end macports was more trouble than good but installed ruby > 1.8.7 from source now console works fine. Thanks for all the help. > regards > c Why more trouble? Usually macports is cool. However for Ruby I find it easier to compile it manually.