How can we watch the Rails development log?

84,270

Solution 1

Look in the log/ directory - there should be a development.log. I bet your output is there.

If it's not, make sure that directory is writable.

For how to see it while you're running: if you have git bash installed, or some other shell such as cygwin, then you can open a shell and do tail -f log/development.log which will scroll the log as it gets stuff appended to it.

Solution 2

The Rails Configuration documentation suggests that you may have log_level set to something other than :debug in your configuration.

There is also an alternative place to view the requests: the log/development.log file in your Rails app. If nothing is written there, then your problem must be in configuration. On a *nix system I would run:

$ tail -f log/development.log

And watch the requests run by. They tell me that there is a Windows version of tail.

Solution 3

less -R log/development.log

I just started to use this.

Solution 4

I always use log/development.log to look at the logs. Just tail -f it using cygwin or something.

Maybe your Windows environment is using WEBrick and the OS X environment is using Mongrel or other webserver. I've noticed that with some webservers the logging output is (also) written directly into the shell and with others is written only to the log files.

Solution 5

Try this, to get development log:

tail -f log/development.log

Make sure that you are in the application path.

Share:
84,270
the1
Author by

the1

Updated on January 25, 2020

Comments

  • the1
    the1 over 4 years

    A member of my team is developing a Rails app on Windows XP. We are finding that when we run the app, either launching it within NetBeans or by opening a console and calling script/server, the Rails development log does not scroll by. There is only the Webrick startup message. The app is definitely running, but when we hit various pages in the browser we aren't seeing any logging output.

    When I look at the identical app on my OS X system, logging output works as expected.

    I did make sure that it's running in Rails "development" environment.

    Any ideas why logging would be suppressed?

    Are there config params for the environment.rb file that would affect it?