HedgeMageApr 9, 2017

Our Masto instance is still getting "/usr/bin/env: ‘ruby2.3’: No such file or directory" when trying to-be-crontabbed commands from the production guide such as "RAILS_ENV=production bundle exec rake mastodon:media:clear" as the mastodon user.

Ruby 2.3.1 is installed and any other command seems to use it just fine.

Help!

Show threadVeritech Yelp ComplainerApr 9, 2017
@HedgeMage Cron may be running /bin/sh which may not be loading .bashrc, or rbenv init may be in .bash_profile. Make sure rbenv init happens in .bashrc, add "source ~/.bashrc" to .bash_profile, and add ". /home/mastodon/.bashrc; " to the beginning of each command in the crontab (assuming you followed the production guide and have a Serbian or ubuntu server)
Show threadHedgeMageApr 9, 2017
@superbranch I tested from the CLI directly to ensure that cron wasn't doing anything weird...it's not working there either.
Show threadVeritech Yelp ComplainerApr 9, 2017
@HedgeMage For completeness, I'm using debian jessie and this is my .bashrc
export HOME=/home/mastodon
export PATH="$HOME/.rbenv/bin:$PATH"
export RAILS_ENV=production
eval "$(rbenv init -)"
Show threadHedgeMageApr 9, 2017
@superbranch Mind telling me what commit you were at when you installed Mastodon?
Show threadVeritech Yelp Complainer
@HedgeMage I cloned the repo at 0200 GMT on Thursday. Not sure how to find the precise commit.
Apr 9, 2017 at 1:29amWeb