Rails application failed to start properly

Rails
1

Hi

I have just uploaded a site from my pc to a railsplayground server.
Everthing was working fine on my pc when i uploaded the site however
that its on the remote server i get

Application error
Rails application failed to start properly

Heres what i have done

  1. Created an app on the Railsplayground server
  2. Cleared out that app folder.
  3. Uploaded my app in its place.
  4. Created my db
  5. Set up the my YML files
  6. Run migration

Is there something i have missed?

Thanks for any help in advance…

Google has been unable to provide an answer thus far and i am getting
kind of desprate

2

On 10/27/06, Stewart [email protected] wrote:

  1. Cleared out that app folder.
  2. Uploaded my app in its place.
  3. Created my db
  4. Set up the my YML files
  5. Run migration

What is in your log files?

3

JDL wrote:

On 10/27/06, Stewart [email protected] wrote:

  1. Cleared out that app folder.
  2. Uploaded my app in its place.
  3. Created my db
  4. Set up the my YML files
  5. Run migration

What is in your log files?

okay, you’ll have to excuse my ignorance here are you referring to the
rails log or the Apache log?

I am 99% sure that this error is not being written to the rails log as I
just checked it then. I am also not sure how I would go about
retrieving my Apache log if that’s in fact what you are referring to.

Do you mean the Apache log?

4

Either log file could provide clues.
In the past i’ve had problems like this caused by things like not being
able to write to tmp/sessions (In my particular case that was because
the files/folders were owned by me, but the rails app was being run by
apache), or by the sessions folder containing old sessions that rails
couldn’t unserialize

Fred

5

Fred wrote:

Either log file could provide clues.
In the past i’ve had problems like this caused by things like not being
able to write to tmp/sessions (In my particular case that was because
the files/folders were owned by me, but the rails app was being run by
apache), or by the sessions folder containing old sessions that rails
couldn’t unserialize

Fred

Thanks for your posts I was able to work out that it was my shebang line
and some permissions where off as well