From: Michael Fischer <mfischer@zendesk.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Issues with PID file renaming
Date: Mon, 25 Nov 2013 17:42:02 -0800 [thread overview]
Message-ID: <CABHxtY7R8yACnJt0_SntDUA_tBwDucEewjOovtnsCHAveXfAcw@mail.gmail.com> (raw)
In-Reply-To: <CAHStS5gFYcPBDxkVizAHrOeDKAkjT69kruFdgaY0CbB+vLbK8Q@mail.gmail.com>
On Mon, Nov 25, 2013 at 5:00 PM, Jimmy Soho <jimmy.soho@gmail.com> wrote:
> I think the problem for us is caused by monit, our process monitor,
> which monitors the unicorn.pid file:
>
> check process unicorn with pidfile
> /srv/app.itrp-staging.com/shared/pids/unicorn.pid
> start program = "/etc/init.d/unicorn start"
> stop program = "/etc/init.d/unicorn stop"
> …
I'd suggest that you monitor Unicorn by issuing a test request to it
via its listening socket instead. Ultimately, you're more likely
concerned about whether Unicorn is serving requests, not whether its
pid file exists. (Such a check can also lead to false positives;
consider what might happen if an admin or the Linux OOM killer sends
it a SIGKILL, leaving the pid file intact.)
Best regards,
--Michael
_______________________________________________
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
next prev parent reply other threads:[~2013-11-26 1:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 1:00 Issues with PID file renaming Jimmy Soho
2013-11-26 1:20 ` Eric Wong
2013-11-26 1:40 ` Michael Fischer
2013-11-26 2:07 ` Eric Wong
2013-12-10 12:46 ` Petteri Räty
2013-12-10 19:52 ` Eric Wong
2013-12-10 22:44 ` Petteri Räty
2013-12-11 13:54 ` Michael Fischer
2013-12-12 19:15 ` Petteri Räty
2013-12-12 20:51 ` Eric Wong
2013-11-26 1:42 ` Michael Fischer [this message]
2013-11-26 4:55 ` Jimmy Soho
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=CABHxtY7R8yACnJt0_SntDUA_tBwDucEewjOovtnsCHAveXfAcw@mail.gmail.com \
--to=mfischer@zendesk.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).