koji is broken
rc040203 at freenet.de
Thu Feb 26 16:22:01 UTC 2015
On 02/26/2015 05:12 PM, Kevin Fenzi wrote:
> On Thu, 26 Feb 2015 17:06:03 +0100
> Ralf Corsepius <rc040203 at freenet.de> wrote:
>> On 02/26/2015 04:40 PM, Kevin Fenzi wrote:
>>> On Thu, 26 Feb 2015 15:26:32 +0100
>>> Dan Horák <dan at danny.cz> wrote:
>>>> On Thu, 26 Feb 2015 15:11:33 +0100
>>>> Ralf Corsepius <rc040203 at freenet.de> wrote:
>>>>> seems to me as if koji has seized operation:
>>>> I guess this is the known "squid doesn't respond" issue. nirik will
>>>> restart it.
>>> Rather it's the known 'squid starts being very slow and failing some
>>> builds' so that was me restarting it.
>>> Just resubmit for now.
>> # fedpkg build
>> Could not execute build: [('SSL routines', 'SSL3_WRITE_BYTES', 'ssl
>> handshake failure')]
> That should be completely unrelated to the kojipkgs issue, as that is
> talking to the koji hub directly.
And would you have the kindness to tell me what I can to about it?
> Can you do a:
> koji list-tasks --mine
# koji list-tasks --mine
Error: [('SSL routines', 'SSL3_READ_BYTES', 'ssl handshake failure')]
>>> I am working on tracking down the problem, but it's proving quite
>>> elusive. ;(
>> BTW: Here's another variant of a break down:
>> This time, yum/dnf (whatever currently is being used, I presume it's
>> yum) is demonstrating one of the yum/dnf issues we discussed
>> Yum retries to download packages from a mirror it could have know to
>> be broken, because it failed to connect to it before.
> Sure, but then it would have just failed faster as thats the only
> mirror thats defined internally for builders.
yum could have tried a different mirror instead of retrying the already
broken one again.
More information about the devel