[HH#341542] Passenger Log File Location?

[HelioHost]

Username: bobrock, Server: Tommy, Main domain: bobrock.heliohost.us

bobrock/Tommy/bobrock.heliohost.us

After deploying my Ruby on Rails app and restarting the Ruby app, I get this error:
---
Error ID:

11cd7da1
Details:

Web application could not be started by the Phusion Passenger(R) application server.

Please read the Passenger log file (search for the Error ID) to find the details of the error.

?

How can I access that log file to see what?s wrong?

Bob
-------------------
Robert J. Rockefeller
Midway, GA

[Krydos]

Switch it to development environment (instead of production like it is now) and the error should be displayed in your browser.

[bobrock]

I switched Ruby to 'development' but I still get only the error number, not the Passenger log file. Is there something else I've missed?

[Krydos]

Did you restart the RoR app after changing the environment?

[bobrock]

Hmmm.

Now, whether in 'production' or 'development', after an app restart, no Passenger errors are thrown!

It's confusing but fixed.

Thanks, again!

[bobrock]

Well, it's not fixed anymore.

I deployed a few changes, re-started Rails, the Passenger error is back, and I can't see the log file in either 'production' or 'development' mode.

Error ID:

3a194af7

Details:

Web application could not be started by the Phusion Passenger(R) application server.

Please read the Passenger log file (search for the Error ID) to find the details of the error.

You can also get a detailed report to appear directly on this page, but for security reasons it is only provided if Phusion Passenger(R) is run with environment set to development and/or with the friendly error pages option set to on.

For more information about configuring environment and friendly error pages, see:

• Nginx integration mode
• Apache integration mode
• Standalone mode

[bobrock]

This is painful to debug without knowing how to view the Passenger log file.

Are node.js apps likely to be easier to deploy than Ruby on Rails apps?

[Krydos]

So, I was mistaken, there are 3 steps you need to do to switch from production to development.

1. Click the development button in Plesk.
2. Restart the app.
3. Wait up to 2 hours for an Apache restart.

I switched your app back to development mode for you, and the errors are shown again. I'm not sure why you keep switching it back to production, but as long as you leave it in development mode you should be able to get all the logs you need. For instance your domain shows this right now

That image won't send through email, so make sure you check the forum directly to see it.

You're welcome to write your website in whatever language you want, but I agree with you completely: When you turn off the error messages, it becomes a lot more challenging to know what the problem is.

[bobrock]

So it's just more self-induced problems. I was under the impression that it was Passenger that needed to be in development mode, not my Ruby app. With that error message, I was able to get things running again. Hopefully I will not screw it up again!

Thanks for the help.