简体   繁体   English

用upstart脚本守护sidekiq-不起作用

[英]daemonizing sidekiq with upstart script - is not working

I'm trying to daemonize sidekiq using two upstart scripts following this example. 示例之后,我尝试使用两个新贵脚本来守护sidekiq。 Basically the workers service starts a fixed number of sidekiq services. 基本上,工人服务会启动固定数量的sidekiq服务。

The problem is that the sidekiq script fails at the line of code where I am starting sidekiq. 问题是,sidekiq脚本在我启动sidekiq的代码行中失败。 I've tried to run the command directly in bash and it works fine. 我试图直接在bash中运行命令,它运行正常。

I tried all different commented lines and none works. 我尝试了所有不同的注释行,但均无效。

So my question is what am I doing wrong? 所以我的问题是我做错了什么? Where can I see the error messages? 在哪里可以看到错误消息?

This is my modified sidekiq script: 这是我修改的sidekiq脚本:

# /etc/init/sidekiq.conf - Sidekiq config

# This example config should work with Ubuntu 12.04+.  It
# allows you to manage multiple Sidekiq instances with
# Upstart, Ubuntu's native service management tool.
#
# See workers.conf for how to manage all Sidekiq instances at once.
#
# Save this config as /etc/init/sidekiq.conf then mange sidekiq with:
#   sudo start sidekiq index=0
#   sudo stop sidekiq index=0
#   sudo status sidekiq index=0
#
# or use the service command:
#   sudo service sidekiq {start,stop,restart,status}
#

description "Sidekiq Background Worker"

respawn
respawn limit 15 5

# no "start on", we don't want to automatically start
stop on (stopping workers or runlevel [06])

# TERM and USR1 are sent by sidekiqctl when stopping sidekiq.  Without declaring these    as normal exit codes, it just respawns.
normal exit 0 TERM USR1

instance $index

script
exec /bin/bash <<EOT
  # use syslog for logging
  # exec &> /dev/kmsg

  # pull in system rbenv
  # export HOME=/home/deploy
  # source /etc/profile.d/rbenv.sh

  cd /home/rails
  touch /root/sidekick_has_started
  sidekiq -i ${index} -e production
  # exec sidekiq -i ${index} -e production
  # exec /usr/local/rvm/gems/ruby-2.0.0-p353/gems/sidekiq-3.1.3/bin/sidekiq -i ${index} -e production
  touch /root/sidekick_has_started_2
EOT
end script

You are right, RVM env are required to be loaded in. Try this: 没错,需要加载RVM env。请尝试以下操作:

.....    
.....

script
exec /bin/bash <<EOT

  #export HOME=/home/deploy
  source /usr/local/rvm/environments/ruby-2.0.0-p353@global

  cd /home/rails
  exec sidekiq -i ${index} -e production

.....    
.....

Does it work? 它行得通吗?

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM