-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logs not printing to STDOUT #28
Comments
Thanks for the report. I'm not completely sure I understand the problem. I'm running a demo app in Heroku and the logs come out just fine: So, I don't believe logging goes to https://github.com/socketry/async/blob/master/lib/async/logger.rb#L42 Do you mind showing me how you are starting falcon (do you include |
Here's what I mean - only the Heroku router logs are shown when the requests are made, but when I restart and SIGTERM is sent, all the logs are dumped. This is the Rails 5.2.1 with the
|
Not using verbose mode, start command is |
I just deployed the latest version of falcon and https://github.com/socketry/utopia-falcon-heroku to Heroku and the logging is certainly happening in real time as I make individual requests. I took a look at rails_12factor and see that it pulls in the following code: https://github.com/heroku/rails_stdout_logging/blob/master/lib/rails_stdout_logging/rails.rb#L2-L4 It seems to me that it's likely to stop |
Apps with the rails_12factor gem / apps running on Heroku need to print logs to STDOUT - but falcon seems to be blocking this. On Heroku it dumps the logs only on exit. Can we have logging behaviour respected / flushed when the app is trying to log to STDOUT?
The text was updated successfully, but these errors were encountered: