Rails 1.2.6
It’s that time again! Right now I’m compiling a new version of Ruby on Rails for our servers. I will be testing and slowly rolling these out this week and next week. The upgrade should be completed by the end of next week at the latest. I will be carefully testing the upgrade to be sure it does not impact customers negatively, but I highly recommend that everyone freezes their rails - especially if you are running a Typo blog!
To freeze your rails applications, ssh into the directory that holds the application and run rake freeze_gems. If you ever need to unfreeze the application, run rake unfreeze_rails.
UPDATE: I have finished the Rails upgrade on all the servers, and it seems to have been a relatively painless process. If you have any problems regarding the upgrade, please forward your questions to tech support.
.
November 27th, 2007 at 1:56 pm
Thanks for your hard work. And for Twittering to let us know. Really good.
November 27th, 2007 at 3:39 pm
Excellent! Thanks for upgrading Rails so we can stay up with the latest and greatest.
Here’s hoping this upgrade also fixes the mildly annoying message that running Rails currently produces: “/usr/bin/rails:17:Warning: require_gem is obsolete. Use gem instead.”
November 27th, 2007 at 4:25 pm
Huh, I figured you guys would wait until 2.0 was released.
November 27th, 2007 at 5:03 pm
“/usr/bin/rails:17:Warning: require_gem is obsolete. Use gem instead.”
I’m looking forward to seeing that message disappear too.
November 27th, 2007 at 5:59 pm
Hey, that’s awesome that you guys are upgrading Rails with relative frequency. I honestly applaud you guys, that’s great. Now how about the ancient, buggy version of Zend Optimizer (3.2.2) that’s still running on the servers? I was told, when I filled a support ticket back in July, that they would likely be upgrading zo when they upgraded PHP. It’s been 6 months, they’ve upgraded PHP a while ago, and I still can’t use the internationalization features in one of the larger PHP frameworks on a PHP5 domain because of Zend Optimizer.
http://www.zend.com/forums/index.php?t=msg&goto=7323
November 27th, 2007 at 6:07 pm
I love rails now. Wasn’t too familiar before but it’s growing on me!
November 27th, 2007 at 6:40 pm
@SomeGuy - Ask support again. We (customers) can’t do anything but bitch and you’ve already got that covered.
November 28th, 2007 at 1:01 am
Any news on Python side ? I stille see 2.4 … any hope to have also 2.5 (at least) ?
November 28th, 2007 at 6:01 am
@omg - Indeed, I have. But “bitching” or “trying to draw other peoples attention to an issue” is not all we can do. By being made aware of the the issue and deciding if it affects you, you can then contact support yourself or vote on the appropriate “suggestions” in the panel.
PHP4 end of life has been announced for the end of this year. If support for PHP4 is removed from DreamHost and they still haven’t updated Zend Optimizer then a number of my ( and I can only assume numerous others since this issue comes up on the mailing list from time to time ) sites will not work without hackish workarounds. Not cool.
So, any other PHP developers who might be reading this, please visit https://panel.dreamhost.com/index.cgi?tree=home.sugg& and vote or email support asking for the upgrading of Zend Optimizer or the option to turn it off. Or maybe the option of using XCache. Heck, why not vote for upgrading PHP to the latest version while you’re there
Besides, although this is not an “official” way of contacting dreamhost, it is known that some dreamhost employees view the comments of their postings. I’ll make use of any means of communication I can.
November 28th, 2007 at 10:45 am
Good to hear you’re keeping up to date. I look forward to the day I move from my dev box to dreamhost.
November 28th, 2007 at 6:08 pm
You misunderstood. I didn’t say the post was not useful, just that the statement was enough to fulfill the bitching quota.
Never underestimate the power of the bitch. I think I have an ex-girlfriend that said that.
And yes, by all means, old broken code really does need to be fixed.
November 28th, 2007 at 9:45 pm
You have to acknowledge this…. the sheer thought of 600,000 webmasters “freezing their gems” is a scary one, LOL
I wouldn’t freeze my gems if the fate of the world depended on it…. I just use and love’em very much
on a more serious note… thanks for the heads up guys!
November 29th, 2007 at 10:06 am
Short question: why pk.ridix.pl isn’t working? It supposed to. What does “Site Temporarily Unavailable
We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.
error id: “bad_httpd_conf” error means?
November 29th, 2007 at 12:28 pm
+1 for Python upgrade.
The current version is oooooooooooooold
November 29th, 2007 at 3:30 pm
# gem -v
0.9.2
What about to update to 0.9.5
November 30th, 2007 at 5:34 am
Mine seemed to run okay, but, at the end of the process, I got this feedback:
Unpacked gem: ‘rails-1.2.3′
cd -
The rake task freeze_gems has been deprecated, please use the replacement version rails:freeze:gems
Any concern?
November 30th, 2007 at 5:49 am
@Pete Gilbert
What’s the Twitter username for updates? Is that for DH Statuses in general, or just Rails-specific issues? Thanks.
November 30th, 2007 at 8:11 am
Whats up with the Twitter updates? That would be useful.
December 1st, 2007 at 2:24 am
hi… i have aquestion regarding my dream host account
December 4th, 2007 at 3:09 pm
Hey SomeGuy, I just got the Zend Optimizer bug TODAY. What a coincidence. Hope they upgrade Zend Optimizer soon; however I think I might better try compiling my own PHP binary…
December 4th, 2007 at 5:01 pm
I’m not able to even run a simple Hello World command through a Controller without getting a routing error…I’m hoping this has something to do with the timing of this RoR rollout, and that the problem goes away when all is done.
December 4th, 2007 at 8:38 pm
Why is this showing up in RSS (feeds.dreamhoststatus.com) as “resolved” when it’s not?
December 6th, 2007 at 2:08 pm
1.2.6 just showed up on my Dreamhost server today. Cool.
December 7th, 2007 at 11:55 am
This must be why my Rails app spontaneously stopped working last night? And why it fails to load now? I have Rails frozen but it blew up anyway. Now I get bizarre and untraceable LoadError messages at Dreamhost that I don’t get with the same code in development. Argh.
December 7th, 2007 at 8:14 pm
@talknightlife: You’re not the only one who’s been having troubles:
http://discussion.dreamhost.com/showthreaded.pl?Cat=0&Board=forum_troubleshooting&Number=96279
We’re seeing FCGI errors in our error logs:
[Thu Dec 06 09:48:29 2007] [error] [client x.x.x.x] FastCGI: incomplete headers (0 bytes) received from server “/home/xxx/example.com/public/dispatch.fcgi”
January 19th, 2008 at 8:09 am
I do have 1 issue when we go from one rails version to the next. Inside the config/environment.rb file, I have to specify a rails version. However, every time there is an upgrade (and I don’t know about it), it blows up my app. What are the best ways around this?
# Specifies gem version of Rails to use when vendor/rails is not present
#RAILS_GEM_VERSION = ‘1.2.3′
RAILS_GEM_VERSION = ‘1.2.6′
error message includes:
[client 71.204.91.95] FastCGI: comm with (dynamic) server “/home/myuser/domain.com/public/dispatch.fcgi” aborted: (first read) idle timeout (60 sec)
[client 71.204.91.95] FastCGI: incomplete headers (0 bytes) received from server “/home/myuser/domain.com/public/dispatch.fcgi”
those of you who see the above messages in your logs, probably just need to change the RAILS_GEM_VERSION. However, if anyone knows how to not require this field, that would be great.
January 22nd, 2008 at 9:58 am
filmmm izleeeee
March 22nd, 2008 at 10:44 am
Thanks for your hard work !
March 29th, 2008 at 12:34 pm
thanx man
March 29th, 2008 at 12:34 pm
thank you
March 29th, 2008 at 12:36 pm
thanx man
March 29th, 2008 at 12:37 pm
thank you
April 10th, 2008 at 9:01 pm
Thanks for your hard work !
April 10th, 2008 at 9:02 pm
thank you
April 23rd, 2008 at 9:49 am
resolved this post. Unfortunately it’s taking a bit longer to get these last stragglers online. Please bear with us, we’re very, very close.
April 25th, 2008 at 9:20 am
thanx man