Mailinglist Archive: opensuse-buildservice (148 mails)

< Previous Next >
RE: [opensuse-buildservice] Updating from 2.3 to 2.4.
-----Original Message-----
From: Stefan Botter [mailto:s.botter@xxxxxxxxxxxxxxxxxxxx]
Sent: 11 September 2013 20:20
To: opensuse-buildservice@xxxxxxxxxxxx
Subject: Re: [opensuse-buildservice] Updating from 2.3 to 2.4.

Hi Rob,

On Wed, 11 Sep 2013 16:19:02 +0000
Rob Zebedee <rzebedee@xxxxxxxxxx> wrote:

Thanks for the pointers on that.
I have managed to roll back to 2.3 for the moment and I am now trying
to get 2.4 working on a vm. The issue I am now seeing is in the
apache2/error_log is: [Wed Sep 11 16:42:28 2013] [notice]
Apache/2.2.21 (Linux/SUSE) mod_ssl/2.2.21 OpenSSL/1.0.0k PHP/5.3.8
Phusion_Passenger/3.0.18 mod_wsgi/3.3 Python/2.7.2 configured --
resuming normal operations
/usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.18/helper-scripts/prespa
wn:105:in
`initialize': Connection refused - connect(2) (Errno::ECONNREFUSED)
from
/usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.18/helper-scripts/prespa
wn:105:in
`new'
from
/usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.18/helper-scripts/prespa
wn:105:in
`connect'
from
/usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.18/helper-scripts/prespa
wn:112:in
`connect'
from
/usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.18/helper-scripts/prespa
wn:86:in
`socket'
from
/usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.18/helper-scripts/prespa
wn:90:in
`head_request'
from
/usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.18/helper-scripts/prespa
wn:145:in
`<main>'

Does anyone have any ideas as to where to begin with fixing this.
Access to the webui does not work at all and the api page just gives
the about xml. Please help it is driving me mad trying to get this to
work.


Did you follow the steps from
https://github.com/openSUSE/open-build-
service/blob/2.4/dist/README.UPDATERS
(the first section 2.3 to 2.4)?

No I had not come across that info I am reading all this before I start again
thanks for pointing me in the right direction hopefully I can get this clear in
my head.


I did the update from 2.3 to 2.4 several times on different OBS installations,
and apart from the missing DB entries, this worked.
If you have the working 2.3 setup, try to get back to it, stop all obs
processed,
update the obs rpms, follow the steps in the README.UPDATERS, and restart
the services. You need to have the mysql/mariadb process running, as the
db's need updating.

You may want to have a look at the log files of the api and webui apache
instances at /srv/www/obs/(api|webui)/logs.

Greetiings,

Stefan
--
Stefan Botter
Network Manager

Jacobs University Bremen gGmbH
Campus Ring 1 | 28759 Bremen | Germany

Commercial registry: Amtsgericht Bremen, HRB 18117 President &
Geschäftsführer: Prof. Dr. Heinz-Otto Peitgen Provost & Geschäftsführerin:
Prof. Dr.-Ing. Katja Windt Chair Board of Governors: Prof. Dr. Karin Lochte

Robert Zebedee
Senior Integration Engineer | Evertz Europe




This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this e-mail in error please notify the sender (as shown
above). Kindly do not reproduce, print or forward any material received in
error, please delete it immediately. Quartz Electronics Limited (Company No.
3013309) is incorporated in England and Wales and has its registered office at
100 Berkshire Place, Wharfedale Road, Winnersh, Wokingham, Berkshire, United
Kingdom, RG41 5RD. Pharos Communications Limited (Company No. 3458137) is
incorporated in England and Wales and has its registered office at 100
Berkshire Place, Wharfedale Road, Winnersh, Wokingham, Berkshire, United
Kingdom, RG41 5RD. Pharos Communications Pte Limited (Company No. 200817005N)
is incorporated in Singapore and has its registered office at One Marina
Boulevard, #28-00. Singapore 018989. Pharos Communications Limited is a wholly
owned subsidiary of Evertz Microsystems Limited, registered in Ontario, Canada.
< Previous Next >