Mailinglist Archive: opensuse-buildservice (105 mails)

< Previous Next >
Re: [opensuse-buildservice] broken builds due to "interconnect error: rpc timeout" with PMBS
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
  • Date: Fri, 27 Dec 2019 14:28:01 +0100
  • Message-id: <4638222.v36FrtDR5o@xrated>
Hi Jan,

Am Donnerstag, 26. Dezember 2019, 21:16:04 CET schrieb Jan Engelhardt:
On Thursday 2019-12-26 19:13, Hans-Peter Jansen wrote:
/srv/obs/log/scheduler_x86_64.log shows this:

2019-12-26 18:07:17: [2762] waiting for an event...
response from watcher for https://pmbs-api.links2linux.de/public
400 remote error: document element must be 'events', was 'html'
retrying in 60 seconds

HTML error page of some kind (i.e. of the "readable" kind that you could
open with your browser too, not some XML that needs a special parser).
opensuse.org no longer seems to like the request that PMBS made. Hooray for
API stability, hooray for... not seeing any of the HTTP headers sent or
received :-/

Another interesting observation: it indeed makes a difference, if I access the
public path of OBS and PMBS with curl or wget.

(All done from the local obs server):

$ wget -qO- https://pmbs-api.links2linux.de/public
<about>
<title>Open Build Service API</title>
<description>API to the Open Build Service</description>
<revision>2.10</revision>
<last_deployment>2019-07-05 14:35:37 +0200</last_deployment>
<commit>1b66a6c499ef52f61406c333d92731323d852fbc</commit>
</about>

$ curl -o- https://pmbs-api.links2linux.de/public
<html><body>You are being <a href="https://pmbs.links2linux.de/
about">redirected</a>.</body></html>

but the behavior is consistent with OBS.

I can provide many more details, but still have no idea, where these issues
stem from. It just shows any package build as broken, that links to PMBS.

I don't think, it's API related, it smells more like some transient issue,
that eventually turned chronic..

Cheers,
Pete


--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups