8:11 a.m.
Hi,
seems to me as if koji has seized operation:
https://kojipkgs.fedoraproject.org//work/tasks/1304/9081304/root.log
https://kojipkgs.fedoraproject.org//work/tasks/1319/9081319/root.log
Ralf
8:26 a.m.
On Thu, 26 Feb 2015 15:11:33 +0100
Ralf Corsepius <rc040203(a)freenet.de> wrote:
Hi,
seems to me as if koji has seized operation:
https://kojipkgs.fedoraproject.org//work/tasks/1304/9081304/root.log
https://kojipkgs.fedoraproject.org//work/tasks/1319/9081319/root.log
I guess this is the known "squid doesn't respond" issue. nirik will
restart it.
Dan
9:40 a.m.
On Thu, 26 Feb 2015 15:26:32 +0100
Dan Horák <dan(a)danny.cz> wrote:
On Thu, 26 Feb 2015 15:11:33 +0100
Ralf Corsepius <rc040203(a)freenet.de> wrote:
> Hi,
>
> seems to me as if koji has seized operation:
>
> https://kojipkgs.fedoraproject.org//work/tasks/1304/9081304/root.log
> https://kojipkgs.fedoraproject.org//work/tasks/1319/9081319/root.log
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.
I am working on tracking down the problem, but it's proving quite
elusive. ;(
kevin
10:06 a.m.
On 02/26/2015 04:40 PM, Kevin Fenzi wrote:
On Thu, 26 Feb 2015 15:26:32 +0100
Dan Horák <dan(a)danny.cz> wrote:
> On Thu, 26 Feb 2015 15:11:33 +0100
> Ralf Corsepius <rc040203(a)freenet.de> wrote:
>
>> Hi,
>>
>> seems to me as if koji has seized operation:
>>
>> https://kojipkgs.fedoraproject.org//work/tasks/1304/9081304/root.log
>> https://kojipkgs.fedoraproject.org//work/tasks/1319/9081319/root.log
>
> 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')]
...
I am working on tracking down the problem, but it's proving
quite
elusive. ;(
BTW: Here's another variant of a break down:
https://kojipkgs.fedoraproject.org//work/tasks/1835/9081835/root.log
This time, yum/dnf (whatever currently is being used, I presume it's
yum) is demonstrating one of the yum/dnf issues we discussed yesterday:
Yum retries to download packages from a mirror it could have know to be
broken, because it failed to connect to it before.
Ralf
10:12 a.m.
On Thu, 26 Feb 2015 17:06:03 +0100
Ralf Corsepius <rc040203(a)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(a)danny.cz> wrote:
>
>> On Thu, 26 Feb 2015 15:11:33 +0100
>> Ralf Corsepius <rc040203(a)freenet.de> wrote:
>>
>>> Hi,
>>>
>>> seems to me as if koji has seized operation:
>>>
>>> https://kojipkgs.fedoraproject.org//work/tasks/1304/9081304/root.log
>>> https://kojipkgs.fedoraproject.org//work/tasks/1319/9081319/root.log
>>
>> 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.
Can you do a:
koji list-tasks --mine
> I am working on tracking down the problem, but it's proving
quite
> elusive. ;(
BTW: Here's another variant of a break down:
https://kojipkgs.fedoraproject.org//work/tasks/1835/9081835/root.log
This time, yum/dnf (whatever currently is being used, I presume it's
yum) is demonstrating one of the yum/dnf issues we discussed
yesterday:
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.
This was caused by my restarting squid.
kevin
10:22 a.m.
On 02/26/2015 05:12 PM, Kevin Fenzi wrote:
On Thu, 26 Feb 2015 17:06:03 +0100
Ralf Corsepius <rc040203(a)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(a)danny.cz> wrote:
>>
>>> On Thu, 26 Feb 2015 15:11:33 +0100
>>> Ralf Corsepius <rc040203(a)freenet.de> wrote:
>>>
>>>> Hi,
>>>>
>>>> seems to me as if koji has seized operation:
>>>>
>>>> https://kojipkgs.fedoraproject.org//work/tasks/1304/9081304/root.log
>>>> https://kojipkgs.fedoraproject.org//work/tasks/1319/9081319/root.log
>>>
>>> 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:
> https://kojipkgs.fedoraproject.org//work/tasks/1835/9081835/root.log
>
> This time, yum/dnf (whatever currently is being used, I presume it's
> yum) is demonstrating one of the yum/dnf issues we discussed
> yesterday:
>
> 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.
11:14 a.m.
On Thu, 26 Feb 2015 17:22:01 +0100
Ralf Corsepius <rc040203(a)freenet.de> wrote:
And would you have the kindness to tell me what I can to about it?
I'm not sure. It's some issue with your communication to the koji
hub...
> Can you do a:
>
> koji list-tasks --mine
# koji list-tasks --mine
Error: [('SSL routines', 'SSL3_READ_BYTES', 'ssl handshake
failure')]
Is your fedora koji cert up to date?
Do:
fedora-cert -v
and if it's expired it should offer to issue you a new one.
Usually however, it would say expired, not handshake failure.
Can you ping koji.fedoraproject.org? browse to it?
Is the time correct on your machine?
>>> I am working on tracking down the problem, but it's
proving quite
>>> elusive. ;(
>>
>> BTW: Here's another variant of a break down:
>> https://kojipkgs.fedoraproject.org//work/tasks/1835/9081835/root.log
>>
>> This time, yum/dnf (whatever currently is being used, I presume
>> it's yum) is demonstrating one of the yum/dnf issues we discussed
>> yesterday:
>>
>> 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.
There's no other mirrors for internal builds. It's a baseurl to the
kojipkgs server.
I am considering making another kojipkgs server and making them round
robin in dns. At least with this restarting squid won't break a bunch
of builds.
kevin
11:18 a.m.
On Thu, Feb 26, 2015 at 10:44 PM, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Thu, 26 Feb 2015 17:22:01 +0100
Ralf Corsepius <rc040203(a)freenet.de> wrote:
> And would you have the kindness to tell me what I can to about it?
I'm not sure. It's some issue with your communication to the koji
hub...
> > Can you do a:
> >
> > koji list-tasks --mine
>
> # koji list-tasks --mine
> Error: [('SSL routines', 'SSL3_READ_BYTES', 'ssl handshake
failure')]
Is your fedora koji cert up to date?
Do:
fedora-cert -v
and if it's expired it should offer to issue you a new one.
Usually however, it would say expired, not handshake failure.
Can you ping koji.fedoraproject.org? browse to it?
Is the time correct on your machine?
I also get the same error. I have update cert. I can ping and browse koji.
Time is correct in the system.
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
Director Python Software Foundation
http://kushaldas.in
11:37 a.m.
On 02/26/2015 06:14 PM, Kevin Fenzi wrote:
On Thu, 26 Feb 2015 17:22:01 +0100
Ralf Corsepius <rc040203(a)freenet.de> wrote:
> And would you have the kindness to tell me what I can to about it?
I'm not sure. It's some issue with your communication to the koji
hub...
Meanwhile I rebooted (for unrelated reasons), now the ssl-errors are
gone. So, it have been could be your or my end - No idea.
>> Can you do a:
>>
>> koji list-tasks --mine
>
> # koji list-tasks --mine
> Error: [('SSL routines', 'SSL3_READ_BYTES', 'ssl handshake
failure')]
Is your fedora koji cert up to date?
Yes it is.
Do:
fedora-cert -v
and if it's expired it should offer to issue you a new one.
Usually however, it would say expired, not handshake failure.
Can you ping koji.fedoraproject.org? browse to it?
Is the time correct on your machine?
Yes, yes and yes ... BTW: koji/fedpkg now seems to work again.
>>>> I am working on tracking down the problem, but
it's proving quite
>>>> elusive. ;(
>>>
>>> BTW: Here's another variant of a break down:
>>> https://kojipkgs.fedoraproject.org//work/tasks/1835/9081835/root.log
>>>
>>> This time, yum/dnf (whatever currently is being used, I presume
>>> it's yum) is demonstrating one of the yum/dnf issues we discussed
>>> yesterday:
>>>
>>> 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.
There's no other mirrors for internal builds. It's a baseurl to the
kojipkgs server.
Yes, my point is it is X times trying in vain to access a host to
download X packages. Not sure what happens when this happens with a real
mirrorlist/metalink-list, whose top 5 are unreachable/flakey/dead or broken.
I am sure I've seen, yum iterating X times over the same list of broken
mirrors.
Ralf
11:44 a.m.
On 2015-02-26, 16:22 GMT, Ralf Corsepius wrote:
> 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?
This is usually very clear and obvious way how Koji tells me
that my certificates have expired. Running fedora-packager-setup
should take care of it.
Matěj
12:09 p.m.
On 02/26/2015 06:44 PM, Matěj Cepl wrote:
On 2015-02-26, 16:22 GMT, Ralf Corsepius wrote:
>> 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?
This is usually very clear and obvious way how Koji tells me
that my certificates have expired. Running fedora-packager-setup
should take care of it.
The koji message is far from being clear.
My certificate definitely had not expired.
From ~/.fedora.cert
...
Validity
Not Before: Feb 3 03:23:15 2015 GMT
Not After : Aug 2 03:23:15 2015 GMT
...
# fedora-cert -v
Verifying Certificate
cert expires: 2015-08-02
Ralf
4:15 a.m.
Ralf Corsepius venit, vidit, dixit 26.02.2015 19:09:
On 02/26/2015 06:44 PM, Matěj Cepl wrote:
> On 2015-02-26, 16:22 GMT, Ralf Corsepius wrote:
>>> 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?
>
> This is usually very clear and obvious way how Koji tells me
> that my certificates have expired.
Haha. Great sense of humor, Matěj.
> Running fedora-packager-setup
> should take care of it.
The koji message is far from being clear.
My certificate definitely had not expired.
From ~/.fedora.cert
...
Validity
Not Before: Feb 3 03:23:15 2015 GMT
Not After : Aug 2 03:23:15 2015 GMT
...
# fedora-cert -v
Verifying Certificate
cert expires: 2015-08-02
Ralf
Yes Ralf, fedora-cert is the better way to deal with the certs (rather
than re-running setup).
We used to be able to download a new cert from FAS. That page seems to
be MIA now without any reference to the cli tools. Doesn't help either.
Have you tried getting a new cert (even though yours is supposed to be
valid)?
Michael
4:49 a.m.
On 02/27/2015 11:15 AM, Michael J Gruber wrote:
Ralf Corsepius venit, vidit, dixit 26.02.2015 19:09:
Yes Ralf, fedora-cert is the better way to deal with the certs
(rather
than re-running setup).
We used to be able to download a new cert from FAS. That page seems to
be MIA now without any reference to the cli tools. Doesn't help either.
Have you tried getting a new cert (even though yours is supposed to be
valid)?
No. Things appear to be fully operational again now.
It likely was my fault to have rebooted the machine I was using or to
try on a different machine to furtherly investigate - but I didn't :(
I have absolutely no clue about what might have been going on. Saying
more about it would be speculation.
Ralf
10:49 p.m.
I still met
Could not execute build: [('SSL routines', 'SSL3_WRITE_BYTES', 'ssl
handshake failure')]
this morning (2 hrs ago).
--
Yours sincerely,
Christopher Meng
http://cicku.me
2:53 p.m.
On Sat, 28 Feb 2015 12:49:39 +0800
Christopher Meng <cickumqt(a)gmail.com> wrote:
I still met
Could not execute build: [('SSL routines', 'SSL3_WRITE_BYTES', 'ssl
handshake failure')]
this morning (2 hrs ago).
I think this is some kind of connectivity issue.
Next time this happens can you run the koji command again with
'--debug' and see if anything stands out? Also make sure you can ping
and reach the koji web page.
There's also a '--debug-xmlrpc' but I think that will show your cert
and other info that shouldn't be public, so you can run it, but don't
share that output in a bug ticket or anything.
kevin
5:55 p.m.
On Tuesday, March 3, 2015, Kevin Fenzi <kevin(a)scrye.com> wrote:
I think this is some kind of connectivity issue.
Next time this happens can you run the koji command again with
'--debug' and see if anything stands out? Also make sure you can ping
and reach the koji web page.
There's also a '--debug-xmlrpc' but I think that will show your cert
and other info that shouldn't be public, so you can run it, but don't
share that output in a bug ticket or anything.
Sure.
--
Yours sincerely,
Christopher Meng
http://cicku.me
3341
days inactive
3345
days old
15 comments
7 participants
participants (7)
-
Christopher Meng -
Dan Horák -
Kevin Fenzi -
Kushal Das -
Matěj Cepl -
Michael J Gruber -
Ralf Corsepius