2.0 update report and question

I put the 2.0.8 to our test instance that run 1.8 and the update was very smooth. Many thanks for making it so easy. Pretty much everything works after the update, which is great as well. We have had more quirks with the past updates.

The only thing that does not work is the Cluster Status app, which is a fairly heavily customized knock-off from OSC’s System Status, GitHub - OSC/osc-systemstatus. The error is:

Error ID:



Web application could not be started by the Phusion Passenger application server.

Please read the Passenger log file (search for the Error ID) to find the details of the error.

You can also get a detailed report to appear directly on this page, but for security reasons it is only provided if Phusion Passenger is run with environment set to development and/or with the friendly error pages option set to on .

Not knowing anything about the Passenger, I figure it may be quicker to ask here than google around so if something strikes out right away, I appreciate any good direction, otherwise I’ll go to Google.


One more thing - the Apache log files don’t contain anything of use, perhaps the Passenger log file is elsewhere? If so, where?

Logs should be in /var/log/ondemand-nginx/mcuma/error.log. But I’m almost sure you need to rebuild the gems for that app because we went from Ruby 2.5 to Ruby 2.7.

What does the Gemfile look like? OnDemand now includes a gemset that you may be able to use if the gem requirements are similar to the preexisting app.

Hi Eric,
here’s the Gemfile

source 'https://rubygems.org'
gem 'ood_core', '~> 0.11'
gem 'sinatra'
gem 'minitest'
gem 'rake'
gem 'mocha'

Now we seem to have a host name resolution problem with the rubygems.org on that machine, though, so I am waiting for our admin to fix that.

If I can use the OnDemand gems, what would I need to do to get those included?


If you remove , '~> 0.11' from the Gemfile, remove the Gemfile.lock, and remove the .bundle/config file (if there is one in that directory), then you should be able to just access the app and it should “just work”.