[opensuse-buildservice] Open Build Service 2.5 Release Candidate
Open Build Service 2.5 Release Candidate is out there. It is tagged as version 2.4.98 and everything except the version number is considered to be final. As usual, you can find the appliances or packages in the now stable OBS:Server:2.5 project: http://download.opensuse.org/repositories/OBS:/Server:/2.5/images/ Users of former OBS 2.5 development releases should update as fast as possible since it is also closing a security hole (which does not exist in 2.4 or before). Please find the full 2.5 release notes inside the packages or online here: https://github.com/openSUSE/open-build-service/blob/2.5/ReleaseNotes-2.5 -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hello obs On Mar 12, 2014, at 4:34 AM, Adrian Schröter <adrian@suse.de> wrote:
Open Build Service 2.5 Release Candidate is out there.
It is tagged as version 2.4.98 and everything except the version number is considered to be final.
installed the server using the Portal documentation sda raid 1 - xzcat > /dev/sda from w/in booted rescue session sdb raid 6 - pvcreate /dev/sdb1 - vgcreate OBS /dev/sdb1 had to play some device name games to get the DHCP working on 1st boot (eth0 -> ens2f0 for ifcfg- and a udev rule) boot's and tells me all is well at prompt. browse to https://<fqdn>/ and see: Web application could not be started An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem. Raw process output: WARN: Unresolved specs during Gem::Specification.reset: rake (>= 0.8.1) WARN: Clearing out unresolved specs. Please report a bug if this causes problems. /usr/lib64/ruby/gems/2.0.0/gems/passenger-4.0.33/lib/phusion_passenger/preloader_shared_helpers.rb:99:in `initialize': No such file or directory - "/tmp/passenger.1.0.3898/generation-1/backends/preloader.9723" (Errno::ENOENT) from /usr/lib64/ruby/gems/2.0.0/gems/passenger-4.0.33/lib/phusion_passenger/preloader_shared_helpers.rb:99:in `new' from /usr/lib64/ruby/gems/2.0.0/gems/passenger-4.0.33/lib/phusion_passenger/preloader_shared_helpers.rb:99:in `run_main_loop' from /usr/lib64/ruby/gems/2.0.0/gems/passenger-4.0.33/helper-scripts/rack-preloader.rb:153:in `<module:App>' from /usr/lib64/ruby/gems/2.0.0/gems/passenger-4.0.33/helper-scripts/rack-preloader.rb:29:in `<module:PhusionPassenger>' from /usr/lib64/ruby/gems/2.0.0/gems/passenger-4.0.33/helper-scripts/rack-preloader.rb:28:in `<main>' Application root /srv/www/obs/api Environment (value of RAILS_ENV, RACK_ENV, WSGI_ENV and PASSENGER_ENV) production Ruby interpreter command /usr/bin/ruby User and groups uid=30(wwwrun) gid=8(www) groups=8(www)
On Montag, 17. März 2014, 11:04:03 wrote Bahi, David:
On Mar 12, 2014, at 4:34 AM, Adrian Schröter <adrian@suse.de> wrote:
Open Build Service 2.5 Release Candidate is out there.
It is tagged as version 2.4.98 and everything except the version number is considered to be final.
installed the server using the Portal documentation
sda raid 1 - xzcat > /dev/sda from w/in booted rescue session
sdb raid 6 - pvcreate /dev/sdb1 - vgcreate OBS /dev/sdb1
had to play some device name games to get the DHCP working on 1st boot (eth0 -> ens2f0 for ifcfg- and a udev rule)
are you sure you had this problem with .98? It is supposed to be fixed there, enforcing udev to use eth0 always.
boot's and tells me all is well at prompt.
browse to https://<fqdn>/ and see:
Web application could not be started An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem. Raw process output:
most likely a follow up problem due to invalid web/rails configuration due to to invalid hostname. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
had to play some device name games to get the DHCP working on 1st boot (eth0 -> ens2f0 for ifcfg- and a udev rule)
are you sure you had this problem with .98? It is supposed to be fixed there, enforcing udev to use eth0 always.
Yes because it was assigning the wrong interface eth 0
boot's and tells me all is well at prompt.
browse to https://<fqdn>/ and see:
Web application could not be started An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem. Raw process output:
most likely a follow up problem due to invalid web/rails configuration due to to invalid hostname
Unlikely unless there is a dependency on the eth 0 ifname Regards David -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Montag, 17. März 2014, 11:31:04 wrote Bahi, David:
had to play some device name games to get the DHCP working on 1st boot (eth0 -> ens2f0 for ifcfg- and a udev rule)
are you sure you had this problem with .98? It is supposed to be fixed there, enforcing udev to use eth0 always.
Yes because it was assigning the wrong interface eth 0
What exactly was the case directly after boot: * You had an interface called eth0 without network? * You had an interface ens2f0 without network? * something else?
boot's and tells me all is well at prompt.
browse to https://<fqdn>/ and see:
Web application could not be started An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem. Raw process output:
most likely a follow up problem due to invalid web/rails configuration due to to invalid hostname
Unlikely unless there is a dependency on the eth 0 ifname
There is a dependency that a work DHCPD and DNS server was found before the obs*setup scripts did run on boot time. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mar 17, 2014, at 11:38, "Adrian Schröter" <adrian@suse.de> wrote:
On Montag, 17. März 2014, 11:31:04 wrote Bahi, David:
had to play some device name games to get the DHCP working on 1st boot (eth0 -> ens2f0 for ifcfg- and a udev rule)
are you sure you had this problem with .98? It is supposed to be fixed there, enforcing udev to use eth0 always.
Yes because it was assigning the wrong interface eth 0
What exactly was the case directly after boot:
* You had an interface called eth0 without network?
Yes - this - had eth0 without network and other three interfaces had 'rename#' for their ifname. eth0 was ifname was associated with 2nd (or on another try the 3rd) network interface - but only first was wired.
* You had an interface ens2f0 without network?
Not this. But after xzcat and before first boot of OBS my playing with udev and ifcfg file in /dev/sda1 allowed ens2f0 to be assigned to the correct interface and have DHPC and DNS working for the first boot configuration.
* something else?
boot's and tells me all is well at prompt.
browse to https://<fqdn>/ and see:
Web application could not be started An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem. Raw process output:
most likely a follow up problem due to invalid web/rails configuration due to to invalid hostname
Unlikely unless there is a dependency on the eth 0 ifname
There is a dependency that a work DHCPD and DNS server was found before the obs*setup scripts did run on boot time.
And that is working - I do not see the bad message about network not working before the prompt. Networking is good but the ifname is not eth0 and the above error message is seen. Haven't tried with ifname as eth0 (just messing with udev rules to get it bound to the first interface - in that pre-deploy play) So think it could be a deprecate issue.
participants (2)
-
Adrian Schröter -
Bahi, David