Support

jmackin · #1 04-26-2009, 05:43 PM

I'm not sure if I'm bringing up and old hat but I just upgrade to Rails 2.3.2 on my slicehost that runs litespeed and although litespeed doesn't seem to choke on it according to the logs it serves me with an 503 error.

I saw a post that was kind of addressing this issue but I didn't seem to understand too well, what's going on or how to fix it.

Is it an issue with litespeed? Can I solve it?

Any help is appreciated.

JM

mistwang · #2 04-27-2009, 06:59 AM

Have you upgrade Litespeed to the latest?

jmackin · #3 04-27-2009, 07:26 AM

I'm still trying... I just messed up my server doing it... Bugger! Doesn't seem to be automatic at all!!!

I'll have to deal with this, but I'll be back to report on how it goes.

So you reckon the latest upgrade will do the trick?

JM

jmackin · #4 04-27-2009, 08:35 AM

I finally got the latest version of litespeed installed. BTW, nothing wrong with your docs. It turns out, that I can't read that well. :-)

Anyway, after upgrading to 4.0.2 I was able to run the Rails app with version 2.3.2 no worries at all.

Thanks.

JM

jmackin · #5 04-28-2009, 04:39 PM

Actually cancel that... I just realized that I still had some pages in cache and after clearing that out, LiteSpeed still chokes on Rails 2.3.2.

So, we are back on square 1 except this time I have the current version of LiteSpeed installed.

Would you mind picking the issue up again?

JM

mistwang · #6 04-28-2009, 06:43 PM

Is there any Ruby processes get started?
Anything in Rails logs file? LSWS error.log and stderr.log?

4.x comes with a new RailsRunner.rb to support Rack, if you revert back to 3.3.24, you should copy over the old RailsRunner.rb, but 3.3.24 wont work with Rails 2.3.2 , only earlier Rails releases.

jmackin · #7 04-28-2009, 07:20 PM

LSWS error.log is fine
Rails access.log, error.log, production.log are fine

LSWS stderr.log ouput:

2009-04-29 02:04:53.921 [NOTICE] [78.46.95.46:39068-0#23point7.com] [uds://tmp/lshttpd/23point7.com:_.sock] Request in process stage, fail with 503

This output is not constant. My latest tests have not revealed the same behavior.

I watched the ruby process with top and when I start the virtual host, either with 2.2.2 or 2.3.2 a couple of ruby processes jump up and disappear but only with 2.2.2 one ruby process reappears presumably because the website is served.

mistwang · #8 04-30-2009, 02:13 PM

Does your app run properly under 2.3.2 with mongrel or webrick?
We tried the default rails app generated with 2.3.2, works fine.