Follow the server install on the new server except for the canvas git
install. Ensure all users are added, including mysql.
Ensure your new server has all the correct levels of ruby, gems etc then
back up /var/rails/canvas, $GEM_HOME and the mysql database for canvas
If you already have /var/rails/canvas, remove or mv the folder before
the restore.
Restore /var/rails/canvas and $GEM_HOME on the new server. Restore the
mysql canvas database. Check /var/rails/config/*.yml files are still
correct for the new server.
Once working you could then do an upgrade, just remember to update the gems
cd /var/rails/canvas
$GEM_HOME/bin/bundle install
to pick up the correct versions for the new Gemfile.
John.
Sorry, I'm not a RoRs expert but you could first try
cd /var/rails/canvas
$GEM_HOME/bin/bundle install
Just to recheck your gems.
Then if not fixed I'd try performing the actions at
https://github.com/instructure/canvas-lms/wiki/Upgrading
from the "Compiled Assetts" onwards. Remember to prefix with
"RAILS_ENV=production" where applicable :-
$GEM_HOME/bin/bundle exec rake canvas:compile_assets
RAILS_ENV=production $GEM_HOME/bin/bundle exec rake db:migrate
RAILS_ENV=production $GEM_HOME/bin/bundle exec rake db:load_notifications
I would also restart canvas_init just in case
If still the same recheck your install in case you are missing a component.
Finally perhaps do a git update. Remember if your working path is not
the same as the git repository you will have to compare the two
directories and remove anything that is not in the git directory (except
for config and tmp). If they have removed a component and you still have
it in your directory it will error.
John.