Closed thbar closed 7 years ago
Got access back to the server, and I can confirm that files under /home/myuser/.rvm/scripts
do not have the execute bit set (unlike in Vagrant, or even on my local Mac).
I have no idea what is happening at this stage.
After more tests and an attempt to install manually using \curl -sSL https://get.rvm.io | bash -s stable
, I see the same problem. This probably means my issue is not related to rvm1-ansible.
I'll investigate more and will come back (probably to close here).
Moving there https://github.com/rvm/rvm/issues/3832. Closing.
I'm facing a puzzling situation where in Vagrant, the RVM setup goes just fine, while on a production server with the same distribution/release, I get the following permission error (I'm using rvm1-ansible v2.2.0, but also tested with v1.3.9 in single user mode):
I've temporarily lost access to the server I was deploying to (unrelated), but seem to remember that the files under
~/.rvm/scripts
(such as version, list) did not have the execution bit set, while in my Vagrant setup I can see that most files there are executable.I'll investigate again once I get access back to the server, but thought I'd report that since it's fairly weird & blocking.