unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Yoav Aner <yoav@kenhub.com>
To: mongrel-unicorn@rubyforge.org
Subject: using unicorn with logging-rails gem
Date: Fri, 30 Nov 2012 18:20:51 +0100	[thread overview]
Message-ID: <CA+mA6PhVKCWudvEDsAdJ5oTT7C3xFtGnoWoExuDFGg4oJ2Koug@mail.gmail.com> (raw)

Hope this is the right place to ask questions about unicorn. I'm not
on the mailing list though, so please CC my email address.

Since moving from phusion passenger to Unicorn, it seems like one
functionality of the logging-rails gem
(https://github.com/TwP/logging-rails) is (half) broken.

Logging-rails supports an email appender, which aggregates log
messages (typically ERROR and above) and then emails them. However,
since moving to Unicorn we stopped getting those emails.

The interesting thing however, is that when we USR2 signal our unicorn
and it restarts itself, then those emails somehow get flushed out and
get sent all at once... I tried sending USR1 signal to see if it has
something to do with log flushing, but this does not seem to make any
difference.

Any ideas how to investigate this / make it work again??

Cheers
Yoav
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

             reply	other threads:[~2012-11-30 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 17:20 Yoav Aner [this message]
2012-11-30 19:15 ` using unicorn with logging-rails gem Eric Wong
2012-11-30 19:59   ` Yoav Aner
     [not found]   ` <CA+mA6PgTGcyLy2Dua9a6gDWhRwsQLtHEyk17fhBE8DW1TkO5EA@mail.gmail.com>
2012-11-30 20:05     ` Eric Wong
2012-11-30 20:17       ` Yoav Aner
2012-11-30 20:55         ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+mA6PhVKCWudvEDsAdJ5oTT7C3xFtGnoWoExuDFGg4oJ2Koug@mail.gmail.com \
    --to=yoav@kenhub.com \
    --cc=mongrel-unicorn@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).