Home/ Questions/Q 8479697
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T19:06:15+00:00

I have two servers that are running (almost) identical installs. Both servers are VMs

  • 0

I have two servers that are running (almost) identical installs. Both servers are VMs and server_b was created as a copy of server_a (this is how I know they are identical installs). Server_a has since been updated using ‘rvm get HEAD’.

server_a:

  • rvm version 1.15.4
  • ruby-1.8.7-p334
  • .rvmrc file specifying ruby-1.8.7@my_gemset (no patch level specified)
  • Rails 3.0.5

server_b:

  • rvm v 1.2.8
  • ruby-1.8.7-p334
  • .rvmrc file specifying ruby-1.8.7@my_gemset (no patch level specified)
  • Rails 3.0.5

When I deploy to server_a, RVM complains that ruby-1.8.7-p370 is not installed, but deploying to server_b does not generate this error. I’m not sure why it is looking for the latest patchlevel for 1.8.7 — I have gone through the RVM configs on each server, comparing them. (The output from ‘rvm info’ results in the same information from both servers, other than the RVM version).

I’ve come to the conclusion that it might have to do with the version of RVM? Have I missed something obvious? Any suggestions would be greatly appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    you should rather update then downgrade, you real problem is that you specify ruby version without patchlevel, in this case RVM will take the latest known patchlevel, so instead of rvm use 1.8.7 you need to tell it rvm use 1.8.7-p334.

    As for the downgrade question you can specify version rvm get 1.2.8, just keep in mind this version is about 2 years old, a lot of things was fixed in rvm since then, and you will not get any support for the old version.

    • 0