[packman] [opensuse-buildservice] broken builds due to "interconnect error: rpc timeout" with PMBS
jsj at jsj.dyndns.org
Thu Dec 26 20:04:03 CET 2019
On Thursday, December 26, 2019 7:14:27 PM CET Hans-Peter Jansen wrote:
> Am Mittwoch, 25. Dezember 2019, 18:40:21 CET schrieb Hans-Peter
> > [A request on the OBS ML kept unanswered for two days, hence trying
> > my luck here..]
> > Hi,
> > I stumbled across broken builds in a local OBS due to "interconnect
> > error: rpc timeout" for packages, that link to PMBS.
> > PMBS is setup as:
> > <project name="Packman">
> > <title>Packman Build Service PMBS</title>
> > <description>This instance can be used to access resources from
> > Packman.</>
> > description>
> > <remoteurl>https://pmbs-api.links2linux.de/public</remoteurl>
> > </project>
> > My OBS itself is fully updated from OBS:/Server:/2.10/openSUSE_15.1.
> > The magic spell, that comes closest to mitigate the issue *ought* to
> > obs_admin --recheck-dod https://pmbs-api.links2linux.de
> > or
> > obs_admin --recheck-dod https://pmbs-api.links2linux.de/public
> > but even after creating the missing /srv/obs/dods directory, things
> > still misbehave.
> > Is this a PMBS issue, a local configuration issue, or something
> > completely different?!?
> /srv/obs/log/scheduler_x86_64.log shows this:
> 2019-12-26 18:07:17:  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
I am not 100% sure, PMBS is working correct, but I have two OBS
instances connected to PMBS without issue. One is running on the same
subnet as PMBS, even on the same ESXi, the other is running at a
different location and has to go through my reverse proxy - like your
I grepped through a month's worth of log files and on both instances
there are no mentions of error messages like yours, not even any mention
Did this work before? Up until when?
PMBS and both my other instances are on 2.10 on 15.1 since July.
PMBS and my close instance are on the ESXi behind the reverse proxy
since end of August, since then there are just the occasional reboots
for security updates.
I can see at least 8 other IP addresses accessing the public interface
today, so to all: Speak up if you too have problems.
Stefan Botter zu Hause
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: This is a digitally signed message part.
More information about the Packman