Puma / missing logs
10,702
Rails has a seperate log file and doesn't log to the puma log. By default, Rails logs to a file in logs/<environment>.log
, e.g. log/production.log
Author by
astropanic
Take me home to paradise city where the build is green and the code is pretty...
Updated on June 20, 2022Comments
-
astropanic almost 2 years
Why I don't see any Rails specific entries in the logs ?
I'm using Puma 2.7.1 with Nginx proxy, on a normal Debian box, nothing fancy, ruby 1.9.3 via RVM.
My puma config:
#!/usr/bin/env puma environment 'sandbox' bind 'unix://tmp/puma.sock' stdout_redirect 'log/puma.log', 'log/puma_error.log', true pidfile 'tmp/pids/puma.pid' state_path 'tmp/pids/puma.state' daemonize true workers 4
I start puma via:
bundle exec puma -C config/puma/config.rb
I see:
[23664] Puma starting in cluster mode... [23664] * Version 2.7.1, codename: Earl of Sandwich Partition [23664] * Min threads: 0, max threads: 16 [23664] * Environment: sandbox [23664] * Process workers: 4 [23664] * Phased restart available [23664] * Listening on unix://tmp/puma.sock [23664] * Daemonizing...
I run:
tail -f log/puma*
I see:
==> log/puma_error.log <== X-Accel-Mapping header missing === puma startup: 2014-02-13 14:08:52 +0100 === [deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message. ==> log/puma.log <== === puma startup: 2014-02-13 14:08:52 +0100 === [23670] - Worker 23678 booted, phase: 0 [23670] - Worker 23674 booted, phase: 0 [23670] - Worker 23686 booted, phase: 0 [23670] - Worker 23682 booted, phase: 0
But I don't see any more logs, nothing application related.
When the application raises an exception, I get nothing in the logs... "tabula rasa"