Mod_rails -- where do logs go?

Ruby
1

I just set up mod_rails (http://www.modrails.com/). Install was easy.
Application seems to be running fine.

One thing I am confused about is that on my server no new entries to the
production log are being added. I am not sure if this is by design or I
made a mistake.

Any advice? It seems mod-rails has only been out for a few days so not
a ton of information I could find yet.

Thanks,

John

2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John H. wrote:
| I just set up mod_rails (http://www.modrails.com/). Install was easy.
| Application seems to be running fine.
|
| Any advice? It seems mod-rails has only been out for a few days so not
| a ton of information I could find yet.

However, Apache modules stuff their logs into apache’s log (not
surprising, since they are part of the Apache webserver).

Phillip G.
Twitter: twitter.com/cynicalryan

Each module should do one thing well.
~ - The Elements of Programming Style (Kernighan & Plaugher)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgBsfcACgkQbtAgaoJTgL/s4wCfZ8MV9jhymkHzW1KwlpHTYpGF
URgAoIf7KcxRgtylANgk8lvcrwQf8/5b
=pzqr
-----END PGP SIGNATURE-----

3

I got it working. It seems mod_rails is logging to log/production.logs,
same as before but it can require a minor tweek.

The fix was to follow:

By default, Passenger runs Rails applications in production mode, so
please be sure to check production.log instead of development.log. See
RailsEnv for configuration.

By default, Passenger runs Rails applications as the owner of
environment.rb. So the log file can only be written to if that user has
write permission to the log file. Please chmod or chown your log file
accordingly.