HostingRails.com

I hope looking into your production log would make you wiser to deal with this issue.
Why don't you paste the contents of your production log in here ?

sorry. but production.log is empty. it never even started up

Oj
it's working now.
No idea why.
But thanks anyway.

Having the same problem getting fastcgi to fire up. Entry below is from my fastcgi log. Dispatchers all set to 0755 permissions. From a front end perspective an http request to my site is actually displaying the dispatch.fcgi file.

I know that I'm missing something trivial here but I can't figure out what it is.

[05/Jun/2007:02:56:31 :: 5927] starting
[05/Jun/2007:02:56:31 :: 5927] Dispatcher failed to catch: You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.split (NoMethodError)
 /usr/local/lib/ruby/1.8/cgi.rb:898:in `parse'
 /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/cgi_ext/raw_post_data_fix.rb:45:in `initialize_query'
 /usr/local/lib/ruby/1.8/cgi.rb:2275:in `initialize'
 /usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:606:in `new'
 /usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:606:in `each_cgi'
 /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:141:in `process_each_request!'
 /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:55:in `process!'
 /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:25:in `process!'

Can you provide me the exact link that you are trying. We can help you out if we get those details.

Rahul - whatever you did got this working for me. Can you share the solution with everyone else?

Thanks

Sorry..I didnt understand. I havent worked on it yet. I was asking you for the exact link so that I can check the issue.

I am getting the same error in my fastcgi.crash.log when running ./dispatch.fcgi.  The only items in my production log are my successful migration rakes.  

And obviously I get, "Application error: Rails application failed to start properly" when I try and access my site.

Seems like this problem magically went away for the others.  Is there a fix.  Please advise.

Thank you,
sf

Hello,

Please make sure that the permissions on your folders and files are not exceeding 755. Refer the link given below

http://www.hostingrails.com/forums/wiki_thread/7

Thanks for the quick response!

I am deploying with capistrano and subversion.  All my permissions seem to be set to 755 on all files already.  I went through and changed all the permissions on all the files to 644 and all the directories and the dispatcher.* files to 755 but I still get the same error.

Any other ideas?

Thanks,
sf

Hello,

Make sure that your are clearing your browser cache before checking it. Thank you

I have the same problem and have not fix it yet. I have try all the solution in the thread. And the production.log has only migration information. Any ideas?

Hello,

It should be permission issue causing the error. Please confirm it again. Make sure that the directories and files are not having permissions more that 755. If you are still facing the issue please post a ticket to the Support Team. We will help you to get it solved. Thank you

I'm a bit confused, I have the same error on my railsapp since today (04/Feb/2008:12:06:04), but the fact is my app hasn't changed since... wow, quite a long time...

I checked the permissions just to see, and ran a find | xargs chmod to be sure permissions are OK, and they were.

I tried to run it in the dev environment, nothing. Samething freezing rails to 1.2.3 (which is the gem version in my config/environment.rb file), without any success.

I also created a new dummy app to see, and this one worked...

The only way to make it work was to use a mongrel server, and it works... Will try to make it activated asap so my app could work back...

Anyway, for my own culture, if someone think to have the answer please tell me.

Hi,

Good to know that you have got this working on Mongrel. But if you still wish to run this app on fastcgi and want this to be investigated, please post a ticket with support.