Phusion Passenger: Web application could not be started

[Marius Stuparu]

After initial setup, I get this error when going to the app:

You have already activated rack 1.5.2, but your Gemfile requires rack 1.4.5. Using bundle exec may solve this.

I have tried these options, with no luck:

1. gem install rack -v 1.4.5

2. edit Gemfile.lock to "rack (>= 1.5.0)"

I'm not very familiar with Ruby, so I don't know what exactly to put afer "bundle exec".

Can you help?

Thanks!

[Marius Stuparu]

Update:

After removing the higher version of rake, with:

gem uninstall rake -v 1.5.2

I get redirected to auth/users/sign_in, but there's an error:

We're sorry, but something went wrong.

We've been notified about this issue and we'll take a look at it shortly.

There's nothing in the /log folder, nor in the Apache error_log

I cannot remove the older version of rake, because actionpack 3.2.13 depends on rack 1.4.5

[Bernhard Rosenberger]

i´ve got the same message when installing jobsworth.

the main failure was that i have startet the install script as root.

This was my solution to solve the problem:
run update.sh
chmod and chown all folders and directories to the webuser (in my case redXXXX:psacln and [not optimal but it works] 0777)

[Marius Stuparu]

I did a 

chown -R apache:apache * | chmod 777 -R *

but still no luck. 

Now I have a "production.log", with: http://pastebin.com/vA6FbRXw

[Mike Stewart]

I'm thinking the syntax you used is incorrect, you might try:

​​

chown -R apache:apache . && chmod -R 777 .

​

this will change the owner for the current directory and everything underneath (recursively).  the chmod will change permissions to rwx for anyone that accesses your system. 777 is virtually never needed -- even in development. 

Instead of 777, I'd suggest chmod -R ug+rwX .

which I feel is easier to understand, only adds any needed permissions for the user & group. (specifically, it adds rw to all files, and rwx to all folders). I'd also recommend that if you're not certain the effects of chown or chmod -- then don't run the command without investigating linux permissions (for your distro) -- the outcome can be quite dangerous.  anything from disabling your system to totally opening it to the world (as in the case of 777).

[Marius Stuparu]

The command was fine and it worked, there's no problem there. Probably that's why I see the production.log now (see my pastebin above).