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!
@HedgeMage Try this command:
$ which ruby2.3
And see if that comes up with a location that's in your env
@munin No, I have Ruby 2.3.1 which may be the confusion if someone hardcoded the ruby2.3 string instead of some sane alternative.
I'm not sure where to dig in to debug it, though.
@HedgeMage Well, you could always use the sysadmin 'brute force and ignorance' solution, and
$ ln -s ruby2.3.1 ruby2.3
;-)
HedgeMage
Munin, Keeper of Lore