#543 Logging from rake tasks is broken in production environment - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#543 ✓resolved

Logging from rake tasks is broken in production environment

Reported by Michael Lovitt | July 3rd, 2008 @ 01:53 PM | in 2.x

To reproduce, create a fresh Rails project, put the attached test_logging.rake file inside /lib/tasks, and then run:

rake test_logging RAILS_ENV=production

The test_logging task calls RAILS_DEFAULT_LOGGER.info, so the logged text should appear in the production.log file, but it does not.

I've reproduced in 2.0.2 and 2.1. Other folks have reported the same problem here:

Michael Lovitt July 3rd, 2008 @ 01:56 PM
- no changes were found...
- test_logging.rake 132 Bytes
josh October 5th, 2008 @ 03:18 PM
- State changed from “new” to “wontfix”
You flagged this item as spam.
David Muir October 30th, 2009 @ 05:13 AM
eh? why is this a wontfix?
I just wasted half my day trying to figure out why I wasn't getting any logs...
Can this be overridden via the production.rb?
If not, is my only option to run all my rake tasks in development mode?
Ryan Bigg April 2nd, 2011 @ 12:32 AM
- State changed from “wontfix” to “open”
- Importance changed from “” to “”
This is still happening. This should not be marked as "wontfix" without a good reason.
Ryan Bigg April 2nd, 2011 @ 12:36 AM
If you come across this error, it's because you're not flushing the log output. Use this which will automatically flush the log on every log call:

Rails.logger.auto_flushing = true
Ryan Bigg April 2nd, 2011 @ 12:36 AM
- State changed from “open” to “resolved”