On Mon, Nov 25, 2013 at 5:00 PM, Jimmy Soho <[email protected]> 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 - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
