Concerto 2 Error Following Upgrade: Web Application Could Not Be Started

[Brian Yulke]

Following an attempt to upgrade from 2.1.x I got the following error when trying to access the web interface:

Web application could not be started

no such file to load -- rubygems (LoadError)
/usr/share/concerto/config/boot.rb:17:in `require'
/usr/share/concerto/config/boot.rb:17
/usr/share/concerto/config/setup_load_paths.rb:7:in `require'
/usr/share/concerto/config/setup_load_paths.rb:7
/usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:214:in `require'
/usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:214:in `run_load_path_setup_code'
/usr/share/passenger/helper-scripts/rack-preloader.rb:100:in `preload_app'
/usr/share/passenger/helper-scripts/rack-preloader.rb:158

Granted, this was months ago and I have not had time to get back to it until now.  This is my dev box, my production box is still running 0.8.7 julietjaguar and I dare not touch it.

The server is running Ubuntu 12.04 LTS.  I just ran apt-get update and upgrade to make sure everything is up-to-date, which it is.  The error persists and, as far as I can tell, remains unchanged.

I looked at line 17 of the boot.rb file to find that it is trying to require yaml.  I don't see why yaml would not be installed if it was installed before and, if it's a new dependency, why it wouldn't have been installed as part of the upgrade.

Has anyone encountered this error, or something similar?  Any suggestions? 

I'm okay blowing away my dev box and rebuilding it (wouldn't be the first time), but this box was setup identically to my production server, so I assume what happened here will happen on prod when I go to upgrade.  Thus, I'd like to figure out what went wrong so I can avoid it on prod.

Thanks!

Brian

[August]

I don't believe the yaml require is the root of your problem. Some searching seems to suggest that this is an error involving having multiple versions of Ruby installed and Concerto trying to use one with no gems installed. I'd search on this error and try some suggestions from there (such as http://stackoverflow.com/questions/2896485/no-such-file-to-load-rubygems-loaderror)

--
August

Brian Yulke

January 23, 2015 at 5:17 PM

Following an attempt to upgrade from 2.1.x I got the following error when trying to access the web interface:

Granted, this was months ago and I have not had time to get back to it until now.  This is my dev box, my production box is still running 0.8.7 julietjaguar and I dare not touch it.

The server is running Ubuntu 12.04 LTS.  I just ran apt-get update and upgrade to make sure everything is up-to-date, which it is.  The error persists and, as far as I can tell, remains unchanged.

I looked at line 17 of the boot.rb file to find that it is trying to require yaml.  I don't see why yaml would not be installed if it was installed before and, if it's a new dependency, why it wouldn't have been installed as part of the upgrade.

Has anyone encountered this error, or something similar?  Any suggestions? 

I'm okay blowing away my dev box and rebuilding it (wouldn't be the first time), but this box was setup identically to my production server, so I assume what happened here will happen on prod when I go to upgrade.  Thus, I'd like to figure out what went wrong so I can avoid it on prod.

Thanks!

Brian

--
You received this message because you are subscribed to the Google Groups "Concerto Digital Signage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concerto-digital-s...@googlegroups.com.
To post to this group, send email to concerto-dig...@googlegroups.com.
Visit this group at http://groups.google.com/group/concerto-digital-signage.
For more options, visit https://groups.google.com/d/optout.

[Brian Yulke]

Holy guacamole!  That, my friend, was indeed the issue.  I have two instances of Ruby - Ruby1.8 and Ruby1.9.1.  Indeed Ruby1.8 was taking precedence while Ruby1.9.1 is what had the gems installed.