Web application could not be started after deployment in digital ocean

Question

-------- The exception is as follows: -------

Your bundle is locked to activesupport (4.2.8), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of activesupport (4.2.8) has removed it. You'll need to update your bundle to a different version of activesupport (4.2.8) that hasn't been removed in order to install. (Bundler::GemNotFound). I have updated ruby from 2.2.4 to 2.4.0 in server

Image of the error

Did you tried what the image says? It seems that you have rvm installed on your server and need to update the wrapper for the new ruby version with a new gemset — Javier Menéndez Rizo, Jan 16 '19 at 17:53
Yeah, I have done that, later I found out that I have to update passenger_root path in my nginx conf file — Tauseef Mamun, Jan 17 '19 at 01:13

Tauseef Mamun · Accepted Answer · 2019-01-17T02:01:17.053

0

I just set the correct path for passenger_root in my nginx.conf file. Though after that nginx was not starting, from error.log file (nginx), I found out that I have to do some compiling. I followed the instructions there, also looked into this Unable to start the Phusion Passenger watchdog?

command line

/usr/local/rvm/gems/ruby-2.4.0/gems/gems/passenger-5.0.30/bin/passenger-config compile-agent

edited Jan 17 '19 at 02:01

answered Jan 16 '19 at 21:53

Tauseef Mamun

126
1
3
11

Web application could not be started after deployment in digital ocean

1 Answers1