Have upstart or bash scripts been used on Ubuntu 14.04? (Trying to load sidekiq with an upstart)

Question

I am new to bash scripts, but it seems to me that I really missed something basic. I am trying to change the version of the Mike Perham upstart sidekiq script on a Ubuntu 14.04 machine, but almost nothing evaluates as expected:

• export does not work.
• the source does not seem to evaluate the changed PATH variable in .bashrc or run the rbenv init command
• cd does not seem to change directories unless the $ (pwd) command is the correct way to evaluate it.

Here is my modified script:

# /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 native service management tool. # change to match your deployment user setuid deploy setgid deploy stop on (stopping workers or runlevel [06]) respawn respawn limit 3 30 instance $index script # this script runs in /bin/sh by default # respawn as bash so we can source in rbenv exec /bin/bash <<EOT # use syslog for logging # exec &> /dev/kmsg # pull in system rbenv export HOME=/home/deploy echo "home is $HOME" source /home/deploy/.bashrc echo "path is $PATH" cd /home/deploy/domain_freek/current echo "user is $(whoami) and pwd is $(pwd) and rbenv is located at $(which rbenv)" exec bundle exec sidekiq -i ${index} -e production EOT end script 

Here is the output that I get in the upstart log file:

 home is path is /usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin user is deploy and pwd is / and rbenv is located at /bin/bash: line 12: exec: bundle: not found 

Answer 1

2 Changes made all the difference:

1) Add hard quotes to EOT in exec /bin/bash << 'EOT' (credit Mat, thanks!)

2) Instead of loading .bashrc using the source, add the rbenv lines from .bashrc directly to the upstart script. Replace source /home/deploy/.bashrc with:

 export PATH="$HOME/.rbenv/bin:$PATH" eval "$(rbenv init -)" export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH" 

I have no idea why these two changes made a difference, and if this is due to a newer version of ubuntu, upstart or bash. If anyone can explain, please call.

I have included my full script work for those just looking for an answer:

 # /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 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" # no "start on", we don't want to automatically start stop on (stopping workers or runlevel [06]) # change to match your deployment user setuid deploy setgid deploy respawn respawn limit 3 30 # TERM is sent by sidekiqctl when stopping sidekiq. Without declaring these as normal exit codes, it just respawns. normal exit 0 TERM instance $index script # this script runs in /bin/sh by default # respawn as bash so we can source in rbenv exec /bin/bash << 'EOT' # use syslog for logging # exec &> /dev/kmsg # pull in system rbenv export HOME=/home/deploy echo "$HOME" #source /home/deploy/.bashrc export PATH="$HOME/.rbenv/bin:$PATH" eval "$(rbenv init -)" export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH" echo "$PATH" cd /home/deploy/domain_freek/current echo "user is $(whoami) and pwd is $(pwd) and rbenv is located at $(which rbenv)" exec bundle exec sidekiq -i ${index} -e production EOT end script 

Answer 2

By default, a .bashrc on Ubuntu 14.04 has a couple of lines to return immediately if the shell is in silent mode. When you delete these lines from your bashrc, then source will work as expected at the upstart.

~ / .bashrc (lines to delete)

 # If not running interactively, don't do anything case $- in *i*) ;; *) return;; esac 

Answer 3

Josh solution does not work for me on ubuntu 14.04 using rbenv. However, this worked:

 exec /bin/bash <<EOF export RBENV_ROOT=/home/ubuntu/.rbenv export RBENV_VERSION=2.2.2 cd /var/www/app/current exec /home/ubuntu/.rbenv/bin/rbenv exec bundle exec sidekiq -i ${index} -e production EOF