Sphnix jobs in systemd

Sharetribe Go Community Edition
1

When I’m running sphnix jobs directly in the terminal, they work well:

bundle exec rake ts:index
bundle exec rake ts:start

However, when I run it as systemd service, they run for a little and then get restarted, and this happens without stopping.

Here’s my systemd script:

[Unit]
After=syslog.target
Requires=mysql.service

[Service]
WorkingDirectory=/home/ubuntu/my_app
ExecStart=/bin/bash -lc 'source /home/ubuntu/.profile && ./script/run_sphinx_jobs.sh'

# [.....]

Restart=always
RestartSec=10
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=my_sphinx_jobs
User=ubuntu
Group=ubuntu
Environment=RAILS_ENV=staging

[Install]
WantedBy=multi-user.target

And the bash script:

#!/bin/bash

export PATH=/home/ubuntu/bin:/home/ubuntu/.local/bin:/home/ubuntu/.nvm/versions/node/v7.8.0/bin:/home/ubuntu/.gem/ruby/2.3.4/bin:/home/ubuntu/.rubies/ruby-2.3.4/lib/ruby/gems/2.3.0/bin:/home/ubuntu/.rubies/ruby-2.3.4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
export GEM_HOME=/home/ubuntu/.gem/ruby/2.3.4

bundle exec rake ts:index
bundle exec rake ts:start

The other similar scripts of my app run with no problem.

2

It is because the sphinx script is forking. In other words, the process that is running after is not the process that kicked it off. Change the type to forking and give it the PIDFile pointing to the sphinx pid file. Should work from there…

[Service]

Type=forking

WorkingDirectory=/home/ubuntu/sharetribe

ExecStart=/bin/bash -lc ‘source /home/ubuntu/.profile && source /home/ubuntu/.rvm/scripts/rvm && bundle exec rake ts:index && bundle exec rake ts:start’

KillMode=control-group

Restart=always

RestartSec=10

StandardOutput=syslog

StandardError=syslog

SyslogIdentifier=st_sphinx

User=ubuntu

Group=ubuntu

Environment=RAILS_ENV=production

PIDFile=/home/ubuntu/sharetribe/log/production.sphinx.pid

[Install]

WantedBy=multi-user.target

1 Like
3

BTW - This is a good reference:

https://www.freedesktop.org/software/systemd/man/systemd.service.html

4

it’s working without pid file

is it required?

5

It won’t restart without knowing which process stopped.

See the below from the link above:

PIDFile=

Takes an absolute path referring to the PID file of the service. Usage of this option is recommended for services where Type= is set to forking . The service manager will read the PID of the main process of the service from this file after start-up of the service. The service manager will not write to the file configured here, although it will remove the file after the service has shut down if it still exists. The PID file does not need to be owned by a privileged user, but if it is owned by an unprivileged user additional safety restrictions are enforced: the file may not be a symlink to a file owned by a different user (neither directly nor indirectly), and the PID file must refer to a process already belonging to the service.

6

…no, it’s working

7

It will start, but if you kill the process (kill not stop the service) does it restart automatically? If so, great. My guess is that it might not always do that because it does not know the process to watch. That said, I am by no means an expert in systemd.

8

its not working…