Re: [sidekiq] Suggestions on daemonizing
- From:
- Patrick Veverka
- Date:
- 2012-07-26 @ 21:09
Great, thanks.
BTW - awesome project. We are loving it.
Mike Perham wrote:
> We use monit to stop / start sidekiq. We're using system-wide RVM +
> bundler binstubs along with this in monitrc:
>
> check process sidekiq
> with pidfile /opt/theclymb/shared/pids/sidekiq.pid
> alert ops@theclymb.com not on { action }
> start program = "/usr/local/rvm/bin/rvm-shell -c 'cd
> /opt/theclymb/current&& bin/sidekiq -e<%= rails_env %> -C
> config/sidekiq.yml -P tmp/pids/sidekiq.pid>> log/sidekiq.log 2>&1'"
> as uid deploy and gid clydev
> stop program = "/usr/local/rvm/bin/rvm-shell -c 'cd
> /opt/theclymb/current&& bin/sidekiqctl stop tmp/pids/sidekiq.pid 30
>>> log/sidekiq.log 2>&1'"
> as uid deploy and gid clydev
> if not exist then alert
> if 1 restart within 5 cycles then timeout
> if totalmem is greater than 1000 MB for 2 cycles then restart
>
>
> On Thu, Jul 26, 2012 at 1:55 PM, Patrick Veverka
> <patrick.veverka@threatsim.com> wrote:
>> What is the current standard or suggested method for running sidekiq in
>> production?
>>
--
*Patrick Veverka*/Lead Developer//
/
/ThreatSim // Stop Phishing Attacks/
Office: 888.687.1337 x757| Cell: 757.745.3485
patrick.veverka@threatsim.com| www.threatsim.com