Mailinglist Archive: opensuse-buildservice (306 mails)

< Previous Next >
Re: [opensuse-buildservice] enable proxy support in the backend
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Wed, 16 Jun 2010 15:11:29 +0200
  • Message-id: <201006161511.30132.adrian@xxxxxxx>
On Wednesday 16 June 2010 14:31:28 John Beranek wrote:
On 07/06/10 08:40, Adrian Schröter wrote:
On Donnerstag, 3. Juni 2010 20:47:11 Marcus Hüwe wrote:
[snip]
Anyway I just committed it.

No, it would error out, because the proxy object does not exist.
It is fixed now. (there were also some typos, so this code could never have
worked).

Hmm, did this proxy code get into OBS 2.0? I've got a local OBS
Appliance behind a corporate proxy that I just 'zypper update'd to:

obs-common-2.0-2.1.i586
obs-server-2.0.0-5.2.i586
obs-worker-2.0.0-5.2.noarch
obs-api-2.0.0-5.2.i586

And if I configure a proxy in BSConfig.pm like:

our $proxy = "http://proxy.example.com:8080";;

The scheduler is still having trouble accessing api.opensuse.org. From
/srv/obs/log/scheduler_i586.log:

response from watcher for https://api.opensuse.org/public
setting up watcher for https://api.opensuse.org/public, start=12813181
2010-06-16 13:17:53: waiting for an event...
response from watcher for https://api.opensuse.org/public
502 remote error: Bad Gateway
retrying in 60 seconds
2010-06-16 13:18:58: waiting for an event...
retrying watcher for https://api.opensuse.org/public
setting up watcher for https://api.opensuse.org/public, start=12813181
2010-06-16 13:19:58: waiting for an event...
response from watcher for https://api.opensuse.org/public
504 remote error: Gateway Time-Out
retrying in 60 seconds
2010-06-16 13:22:59: waiting for an event...


Ah, however, it seems I was premature to think the build wasn't working
due to this. My local OBS has just built a package using a remote
repository!

So, I guess the scheduler is still occasionally trying to contact
api.opensuse.org without a proxy in particular cases?

It tries to keep a connection open permanently to be able to get notified
on changes on api.opensuse.org (new sources, new binaries).

api.o.o has to close the connection unfortunatly or we would run out of ports
due to broken connections. So these timeouts are "okay", nothing is lost and
the scheduler is reconnecting again.

bye
adrian
--

Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx

--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
List Navigation