[opensuse-factory] OBS:Server:Unstable broken on Factory? (Passenger error)
Hi, For some weeks I've been running a local OBS server on armv7hl Factory. After updating the machine this weekend, I get the following error page accessing its Web UI on https port 443: Web application could not be started cannot load such file -- phusion_passenger/platform_info/ruby (LoadError) /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger.rb:237:in `require_passenger_lib' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:415:in `rescue in running_bundler' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:411:in `running_bundler' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:287:in `run_load_path_setup_code' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:99:in `preload_app' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:153:in `module:App' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:29:in `module:PhusionPassenger' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:28:in `<main>' Error ID 840136e9 Application root /srv/www/obs/api [...] Unfortunately I'm pretty clueless about Ruby... I do see a platform_info/ruby.rb here: -rw-r--r-- 1 root root 18826 Sep 20 11:51 /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/platform_info/ruby.rb Can anyone clue me in on what is going wrong there? It seems that the OBS scheduler, for instance, is running fine, so I imagine this is either a Passenger/... packaging problem in Factory or a configuration/code problem on the OBS side? In order to get OBS running on armv7l, I needed to branch the following packages (in addition to OBS:Server:Unstable noarch packages), with no link diff left: apache2-mod_xforward perl-BSSolv rubygem-acts_as_list rubygem-acts_as_tree rubygem-clockwork rubygem-cocoon rubygem-dalli rubygem-escape_utils rubygem-hoptoad_notifier rubygem-innertube rubygem-joiner rubygem-kaminari rubygem-middleware rubygem-passenger rubygem-pundit rubygem-redcarpet rubygem-riddle rubygem-ruby-ldap rubygem-thinking-sphinx https://build.opensuse.org/project/show/home:a_faerber:branches:OBS:Server:U... @Adrian, it would be nice if you could add openSUSE_Factory_ARM to OBS:Server:Unstable, to build them centrally instead. To save resources you could disable the build for aarch64/armv7l by default and just enable the above list of non-noarch packages for now. Also note that there's an OBS-WorkerOnly-midway Kiwi package that references obs://OBS:Server:Unstable/openSUSE_13.1_ports which no longer exists. rubygem-rails-4_2 is available in Tumbleweed already and probably shouldn't be rebuilt for openSUSE_Factory(_ARM) - it originally caused Gemfile problems that their 4.2.x versions between openSUSE:Factory:ARM and OBS:Server:Unstable were slightly out of sync: There's a link diff on that package, being at 4.2.2 while Factory has 4.2.4 currently - intentional? I am using the available Factory version. https://build.opensuse.org/package/show/OBS:Server:Unstable/rubygem-rails-4_... In case anyone wonders why :Unstable, :2.6 is not being built for Factory at all. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 21.09.2015 um 09:41 schrieb Andreas Färber:
For some weeks I've been running a local OBS server on armv7hl Factory. After updating the machine this weekend, I get the following error page accessing its Web UI on https port 443:
Web application could not be started
cannot load such file -- phusion_passenger/platform_info/ruby (LoadError) /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger.rb:237:in `require_passenger_lib'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:415:in `rescue in running_bundler'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:411:in `running_bundler'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:287:in `run_load_path_setup_code' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:99:in `preload_app' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:153:in `module:App' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:29:in `module:PhusionPassenger' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:28:in `<main>'
Doh, managed to get it to work again, by running `rake gem:check` in that directory: Turned out that my `zypper up` reverted all my hand-tweaked gem versions in /srv/www/obs/api/Gemfile.lock, which then showed in this hard to understand way... Question remains what can be done to make obs-server Tumbleweed-friendler. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Montag, 21. September 2015, 11:32:47 CEST wrote Andreas Färber:
Am 21.09.2015 um 09:41 schrieb Andreas Färber:
For some weeks I've been running a local OBS server on armv7hl Factory. After updating the machine this weekend, I get the following error page accessing its Web UI on https port 443:
Web application could not be started
cannot load such file -- phusion_passenger/platform_info/ruby (LoadError) /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger.rb:237:in `require_passenger_lib'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:415:in `rescue in running_bundler'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:411:in `running_bundler'
/usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:287:in `run_load_path_setup_code' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:99:in `preload_app' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:153:in `module:App' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:29:in `module:PhusionPassenger' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:28:in `<main>'
Doh, managed to get it to work again, by running `rake gem:check` in that directory: Turned out that my `zypper up` reverted all my hand-tweaked gem versions in /srv/www/obs/api/Gemfile.lock, which then showed in this hard to understand way...
Question remains what can be done to make obs-server Tumbleweed-friendler.
Why do you need to hand-tweek that file? Which rubygem version does not match? The published obs* rpms are only verified against the rubygem packages from the same repository. If you use different ones no one knows what happens ... -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 21.09.2015 um 11:34 schrieb Adrian Schröter:
On Montag, 21. September 2015, 11:32:47 CEST wrote Andreas Färber:
managed to get it to work again, by running `rake gem:check` in that directory: Turned out that my `zypper up` reverted all my hand-tweaked gem versions in /srv/www/obs/api/Gemfile.lock, which then showed in this hard to understand way...
Question remains what can be done to make obs-server Tumbleweed-friendler.
Why do you need to hand-tweek that file? Which rubygem version does not match?
Rails 4.2.2 vs. 4.2.4 affects multiple gems (activesupport etc.), plus: minitest 5.8.0 vs. 5.7.0 * rails-dom-testing 1.0.6 vs. 1.0.7 loofah 2.0.2 vs. 2.0.3 rack 1.6.2 vs. 1.6.4 globalid 0.3.5 vs. 0.3.6 mime-types 2.6.2 vs. 2.6.1 * arel 6.0.0 vs. 6.0.3 daemons 1.2.2 vs. 1.2.3 haml 4.0.6 vs. 4.0.7 sprockets 3.2.0 vs. 3.3.4 sprockets-rails 2.3.1 vs. 2.3.3 In particular when it's just the x.y.Z level differing, I don't see the point of building the package in a branch of my own when the Tumbleweed repo provides me with the latest fixes. Only in two cases (*) was it an x.y.Z-1 or x.Y-1.z downgrade - guessing the package submission is in Staging or not published/built for armv7l yet. Anyway, this looks just as bad as Maven (Java), which also hardcodes the exact version as dependency rather than leaving fixes to the distro! Further, the version of python-yum differs not in the version but by one build number, 3.4.3-17.3 vs. 3.4.3-17.2, causing package conflicts.
The published obs* rpms are only verified against the rubygem packages from the same repository. If you use different ones no one knows what happens ...
I doubt that many people have tested this on ARMv7 anyway... I know we have installations on AArch64 that we've demo'ed, but there still doesn't seem to be an official way to install that either, with your home:adrianSuSE branch gone. And like I said, it seemed and now again seems to work just fine with the current Tumbleweed versions. When it breaks with some update, it will need to be fixed at some point anyway. Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Adrian Schröter
-
Andreas Färber