Still somehow wants ruby 2.2

philippbayer commented 7 years ago

I'm getting this error when starting nginx:

App 595 stdout: 
App 595 stderr: *** ERROR ***: Cannot execute /usr/bin/ruby2.2: No such file or directory (2)
[ 2017-06-02 02:52:01.3922 532/7f1a4c064700 age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /home/app/snpr: An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger.
  Error ID: f8f850bd
  Error details saved to: /tmp/passenger-error-MSDQkF.html
  Message from application: An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read <a href="https://github.com/phusion/passenger/wiki/Debugging-application-startup-problems">this article</a> for more information about this problem.<br>
<h2>Raw process output:</h2>
<pre>
*** ERROR ***: Cannot execute /usr/bin/ruby2.2: No such file or directory (2)
</pre>

Currently circumventing by symlinking 2.2 to 2.3, but that's not a permanent solution and will revert on next deploy. Checking what happened here.

gedankenstuecke commented 7 years ago

Issue is that nginx-opensnp.org.conf still links hard to 2.2 instead of 2.3. Problem here: the production systems are running on the fork by @tsujigiri which neither @philippbayer nor I have write-access to. 😱

philippbayer commented 7 years ago

I changed the nginx-opensnp.org.conf now to the 'new' 2.3 ruby file. still needs the docker hub fix.

philippbayer commented 7 years ago

Fixed!

openSNP / opensnp.org-docker

Still somehow wants ruby 2.2 #7