# Rails 1.1 hosed my Apache! **URL:** \ **Category:** Rails\ **Created:** [March 30, 2006, 11:37pm UTC](https://www.ruby-forum.com/t/rails-1-1-hosed-my-apache/56404 "2006-03-30T23:37:37Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![lkfken](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/7bcc69/32.png) [@lkfken](https://www.ruby-forum.com/u/lkfken)\ **Post date:** [March 30, 2006, 11:37pm UTC](https://www.ruby-forum.com/t/rails-1-1-hosed-my-apache/56404/1 "2006-03-30T23:37:37Z")
Just sharing an experience with you all – hopefully you take better precautions than I do. 🙂 I have a few sites built with Rails 0.8.3 that were ugpraded to 1.0. The newer sites are on edge rails. So when I heard 1.1 had come out, I unfroze my new apps, and installed the new gem for Rails 1.1. The sites that was operating on edge rails worked just fine. However, the sites that were working fine on 1.0 suddenly broke, and started spewing FCGI errors. Of course, I’m lazy and I didn’t check them right away. Serves me right. So I woke up this morning to find that my apache has died. FCGI errors from apache filled all the logs as my sites were spidered by Google. Ooops. For some reason I was under the mistaken impression that 1.0 -\> 1.1 should not have been a problem. ---
**Author:** ![lkfken](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/7bcc69/32.png) [@lkfken](https://www.ruby-forum.com/u/lkfken)\ **Post date:** [March 31, 2006, 12:02am UTC](https://www.ruby-forum.com/t/rails-1-1-hosed-my-apache/56404/2 "2006-03-31T00:02:51Z")
Kenneth L. wrote: > … > However, the sites that were working fine on 1.0 suddenly broke, and > started spewing FCGI errors. Of course, I’m lazy and I didn’t check > them right away. Serves me right. > > So I woke up this morning to find that my apache has died. FCGI > errors from apache filled all the logs as my sites were spidered by > Google. Ooops. > > For some reason I was under the mistaken impression that 1.0 -\> 1.1 > should not have been a problem. I love rails 1.1 but I think if a rails 1.1.1 isn’t released soon with ~8-12 key bugfixes, rails may–undeservedly–gain a reputation for being a ‘hobby’ framework that is too unreliable & risky for commercial websites. Also, many people have a vested interest in preventing migrations to rails (from Java, PHP, ASP, etc.) and may use this to spread FUD. With all the time/money they already have invested, it won’t be long before you see articles about rails being “too unreliable and risky”. I think the best we can do as rails users is to avoid pissing off the core team with insults and help them with useful bug reports or patches. I sincerely hope rails 1.1.1 will be released to address the top ~10 bugs before substantial new features are added–I especially hope the bugfixes will be focused on issues that cause problems during upgrades from 1.0 -\> 1.1… ---
**Author:** ![lkfken](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/7bcc69/32.png) [@lkfken](https://www.ruby-forum.com/u/lkfken)\ **Post date:** [March 31, 2006, 12:14am UTC](https://www.ruby-forum.com/t/rails-1-1-hosed-my-apache/56404/3 "2006-03-31T00:14:16Z")
I hope I didn’t come off as sounding like I was bitching/ranting. I was just noting that my older rails apps blew up badly while the ones running from the edge went just fine. Someone should put up/update the wiki with Rails 1.0 -\> 1.1 gotchas and resolutions. ---
**Author:** ![lkfken](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/7bcc69/32.png) [@lkfken](https://www.ruby-forum.com/u/lkfken)\ **Post date:** [March 31, 2006, 12:17am UTC](https://www.ruby-forum.com/t/rails-1-1-hosed-my-apache/56404/4 "2006-03-31T00:17:23Z")
1.1 release is not a bugfix release for 1.0. It’s more like 2.0 release. And in my practise, I don’t remember a single x.0 release that didn’t have some critical issues. That’s why I’m still waiting for MacBook Pro rev2.