# Crashing after Update **URL:** \ **Category:** Rails\ **Created:** [July 2, 2008, 2:54pm UTC](https://www.ruby-forum.com/t/crashing-after-update/142000 "2008-07-02T14:54:05Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gbesch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/f1d935/32.png) [@gbesch](https://www.ruby-forum.com/u/gbesch)\ **Post date:** [July 2, 2008, 2:54pm UTC](https://www.ruby-forum.com/t/crashing-after-update/142000/1 "2008-07-02T14:54:05Z")
Hello All! I’ve been running Rails 2.0.2 with Ruby 1.8.6 for the last six months. I developed an application that runs fine on two different servers – or at least, it used to. I used Mongrel as a development server, but requirements called for using Apache for a production deployment. I found Phusion Passenger (mod\_rails) and decided to give it a try. I decided to update my rubygems to the latest version before installing Passenger, so I did a “gem update --system”. A slew of gems were updated (at least six or eight). All seemed fine until I tried actually using my application again 😉 Now the application crashes when it tries to access any of my named routes. Rubygems cores, usually with a segmentation fault, generating messages like this in /var/log/httpd/error\_log: \*\*\* glibc detected \*\*\* Rails: /var/www/rails/wave: double free or corruption (out): 0x0a188d90 \*\*\* and Premature end of script headers: users, referer: [http://shrimp/wave](http://shrimp/wave) and /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action\_view/helpers/ url\_helper.rb:488: [BUG] Segmentation fault and /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action\_view/ template\_error.rb:78: [BUG] Segmentation fault I tried using both mod\_rails and mongrel to serve the application, but both give the same results. In hindsight I should have done a backup before the update, but my hindsight seems a lot better than my foresight lately. So now we finally come to my question: How do I undo the mess I made? Is there a log somewhere that tells me specifically which versions of which gems were updated, and is there an easy way to roll back to a specific version? Even better would be if someone else has seen the same problem and knows of a patch or update that would allow me to use the updated gems… but I figure that’s probably asking too much. One more thing: My development environment is Fedora Core 8 and I have the yum updatesd service running. I’ve noted at least two Ruby “security” updates over the last week, so I’m also wondering if anything pushed down via that route might be causing (or at least contributing to) my problems… Greg ---
**Author:** ![gbesch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/f1d935/32.png) [@gbesch](https://www.ruby-forum.com/u/gbesch)\ **Post date:** [July 2, 2008, 3:19pm UTC](https://www.ruby-forum.com/t/crashing-after-update/142000/2 "2008-07-02T15:19:17Z")
On 2 Jul 2008, at 13:53, gbesch wrote: > I decided to update my rubygems to the latest version before > installing Passenger, so I did a “gem update --system”. A slew of > gems were updated (at least six or eight). All seemed fine until I > tried actually using my application again 😉 Did you update ruby itself? the currently available version (1.8.6p230) is known to segfault (no official release that fixes the problem, a number of people have backported the security fixes etc…) Fred ---
**Author:** ![gbesch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/f1d935/32.png) [@gbesch](https://www.ruby-forum.com/u/gbesch)\ **Post date:** [July 3, 2008, 12:18am UTC](https://www.ruby-forum.com/t/crashing-after-update/142000/3 "2008-07-03T00:18:37Z")
> Did you update ruby itself? Sure did: ruby -v ruby 1.8.6 (2008-06-20 patchlevel 230) [i386-linux] It was one of the updates listed in yum’s automatic updates feed, I think from Livna. I see now that I can’t rely on the repo to provide stable releases, so evidently I need to kill updatesd and start doing manual updates again. So much for time saving conveniences like automatic updates, huh? I’m sorry to have taken up your time with a question that could have been answered by doing a bit more research on my own. Too many short deadlines lately, so I’m a bit more scattered-brained than usual… Thanks! I sincerely appreciate the help. Greg On Jul 2, 9:18 am, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) ---
**Author:** ![gbesch](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/f1d935/32.png) [@gbesch](https://www.ruby-forum.com/u/gbesch)\ **Post date:** [July 3, 2008, 12:33am UTC](https://www.ruby-forum.com/t/crashing-after-update/142000/4 "2008-07-03T00:33:14Z")
On Wed, 2008-07-02 at 15:18 -0700, gbesch wrote: > manual updates again. So much for time saving conveniences like > automatic updates, huh? > > I’m sorry to have taken up your time with a question that could have > been answered by doing a bit more research on my own. Too many short > deadlines lately, so I’m a bit more scattered-brained than usual… > > Thanks! I sincerely appreciate the help. * * * you need to update again… yum clean all yum update the ruby-1.8.6-230-3 packages for Fedora 8 & Fedora 9 went out today and that solved this issue. Also, these are fedora packages, not Livna. As for not running yum-updatesd…by itself, it doesn’t do any updating unless you tell it to do automatic upgrades. The reality is though, that the ruby developers put out patches that broke rails and the fedora packagers could not have known but this issue affected Ubuntu and other Linux distributions as well. All should be well for systems that are up to date. Craig