Booting rbenv managed rails app with Systemd

19 views
Skip to first unread message

medr...@gmail.com

unread,
Apr 3, 2019, 5:23:55 PM4/3/19
to Ruby on Rails: Talk
Have been working on creating some systemd services to launch some features on a raspberrypi that is used for running a rails app. No issues with a service for launching a python script nor one for putting the pi in kiosk mode, when it comes to launching the systemd service for rails it is failing. 

Here is my service file:

[Unit] Description=evr server boot After=network.target After=local-fs.target [Service] Type=forking User=pi Group=pi WorkingDirectory=/home/pi/evr ExecStart=/home/pi/.rbenv/bin/rbenv bundle exec rails s -b 192.168.1.66 TimeoutSec=180 RestartSec=180s Restart=always [Install] WantedBy=multi-user.target


when running it produces this error:

$ systemctl status evrserver ● evrserver.service - evr server boot Loaded: loaded (/etc/systemd/system/evrserver.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2019-04-03 18:34:22 BST; 2min 51s ago Process: 425 ExecStart=/home/pi/.rbenv/bin/rbenv bundle exec rails s -b 192.168.1.66 (code=exited, status=1/FAILURE) CGroup: /system.slice/evrserver.service Apr 03 18:34:22 raspberrypi systemd[1]: Failed to start evr server boot. Apr 03 18:34:22 raspberrypi systemd[1]: evrserver.service: Unit entered failed state. Apr 03 18:34:22 raspberrypi systemd[1]: evrserver.service: Failed with result 'exit-code'.

any thoughts here? thinking the rbenv PATH is causing the issue, not sure how its needing to be structured to access that correct PATH to execute the 'rails' command.

medr...@gmail.com

unread,
Apr 3, 2019, 11:30:11 PM4/3/19
to Ruby on Rails: Talk
snap, missed the other exec before bundle in the ExecStart line, and needed to switch the type to =simple.

botp

unread,
Apr 4, 2019, 2:57:27 AM4/4/19
to rubyonra...@googlegroups.com
On Thu, Apr 4, 2019 at 11:30 AM <medr...@gmail.com> wrote:
ExecStart=/home/pi/.rbenv/bin/rbenv bundle exec rails s -b 192.168.1.66
 
i havent used rbenv like that, but, have you tested that statement alone on a command line?
have you tried running without rbenv in that line?

any thoughts here? thinking the rbenv PATH is causing the issue, not sure how its needing to be structured to access that correct PATH to execute the 'rails' command.

you already have a working directory; and assumming that directory is a rails app dir, you can run bundle and rails among others in there.

--
many thanks and many regards,
--botp

Reply all
Reply to author
Forward
0 new messages