Without trusting all rvmrc files (which works as a workaround), passenger fails to load the rvmrc file due to trust issues. I have explicitely trusted the rvmrc from the command line and verified that it shows up in the rvmrcs file with the correct path.
The pertinent details are covered in this gist.
If you need anything else, let me know. Thanks.
please run the following:
which md5 md5sum sha256sum sha256 shasum 2>/dev/null
if the binaries are located in directories different then /usr/bin or /bin then this might be reason of the problem, linking them to /usr/bin could possibly solve it
That command gives the following output:
I'm also experiencing this bug. I can produce the problem on my system with the following:
$ sudo mkdir /var/www/a_b
$ echo "rvm use 1.9.2" | sudo tee /var/www/a_b/.rvmrc
rvm use 1.9.2
$ rvmsudo rvm rvmrc trust /var/www/a_b
Marked /var/www/a_b/.rvmrc as trusted
$ rvm tools path-identifier /var/www/a_b ; echo " Return Code: $?"
ruby-1.9.2-p290 Return Code: 2
That return value from rvm tools path-identifier /some/path (apparently?) indicates that the specified directory is not trusted. I can further verify that the directory IS in fact trusted, both by cd /var/www/a_b and by manual inspection of my /usr/local/rvm/user/rvmrcs file.
rvm tools path-identifier /some/path
Some trusted directories work for me, others don't. Haven't figured out (yet) what the difference is. Anyhow, I've at least simplified things by removing the passenger and ruby library elements.