This may be a dumb question, but where can I see the error logs that are usually displayed when unicorn is not daemonized? The production.log file is empty in my app. Everything is currently running as root.
On Wed, Nov 18, 2009 at 9:06 PM, Preston Marshall <preston at synergyeoc.com> wrote:> This may be a dumb question, but where can I see the error logs that are > usually displayed when unicorn is not daemonized? ?The production.log file > is empty in my app. ?Everything is currently running as root.I''m not sure where the logs are directed by default, but I set their location in my unicorn config like so: stdout_path ''/home/deploy/public_html/rm/current/log/unicorn.log'' stderr_path ''/home/deploy/public_html/rm/current/log/unicorn-error.log'' More information here: http://unicorn.bogomips.org/Unicorn/Configurator.html Best, Michael Guterl
On Nov 18, 2009, at 6:47 PM, Michael Guterl wrote:> On Wed, Nov 18, 2009 at 9:06 PM, Preston Marshall > <preston at synergyeoc.com> wrote: >> This may be a dumb question, but where can I see the error logs that are >> usually displayed when unicorn is not daemonized? The production.log file >> is empty in my app. Everything is currently running as root. > > I''m not sure where the logs are directed by default, but I set their > location in my unicorn config like so: > > stdout_path ''/home/deploy/public_html/rm/current/log/unicorn.log'' > stderr_path ''/home/deploy/public_html/rm/current/log/unicorn-error.log'' > > More information here: http://unicorn.bogomips.org/Unicorn/Configurator.html > > Best, > Michael Guterl > _______________________________________________ > mongrel-unicorn mailing list > mongrel-unicorn at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-unicornI ended up doing something like: unicorn_logger = Logger.new("/home/xxxxxx/current/log/unicorn.log") unicorn_logger.formatter = Logger::Formatter.new logger unicorn_logger ... but, I think you can do this as well: Configurator::DEFAULTS[:logger].formatter = Logger::Formatter.new See: http://rubyforge.org/pipermail/mongrel-unicorn/2009-November/000147.html =Dylan
Michael Guterl <mguterl at gmail.com> wrote:> On Wed, Nov 18, 2009 at 9:06 PM, Preston Marshall > <preston at synergyeoc.com> wrote: > > This may be a dumb question, but where can I see the error logs that are > > usually displayed when unicorn is not daemonized? ?The production.log file > > is empty in my app. ?Everything is currently running as root. > > I''m not sure where the logs are directed by default, but I set theirThey go to /dev/null by default when daemonizing. But yes, it''s recommended that you configure them to something like below:> location in my unicorn config like so: > > stdout_path ''/home/deploy/public_html/rm/current/log/unicorn.log'' > stderr_path ''/home/deploy/public_html/rm/current/log/unicorn-error.log''
Possibly Parallel Threads
- Timestamp in unicorn logs
- 403 Forbidden from nginx when unicorn started in debug mode
- unicorn doesn't restart properly after cap deploy (not using Bundler)
- unicorn 3.0.0 - disable rewindable input!
- [PATCH] make stderr_path/stdout_path support IO objects directly