https://sourceware.org/bugzilla/show_bug.cgi?id=27531
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
Frank Ch. Eigler changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |alizhang at redhat dot
com
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #11 from Sergio Durigan Junior ---
Up to you. I think a retry mechanism is an interesting thing to have, even if
it's not used much nor enabled by default. But I understand there are higher
priorities now.
--
You are receiving
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #10 from Frank Ch. Eigler ---
OK, for your use case, a retry possibly would not help, but an enlarged timeout
does. Interesting. Should we keep this RFE open or close it?
--
You are receiving this mail because:
You are on the C
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #9 from Shengjing Zhu ---
With large timeout it works. I paste the log with timestamp in attachment.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #8 from Shengjing Zhu ---
Created attachment 13309
--> https://sourceware.org/bugzilla/attachment.cgi?id=13309&action=edit
large timeout output
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #7 from Frank Ch. Eigler ---
OK, it looks like four separate instances of "Timer expired (err=-62)"
errors, indicating that the system did wait the 90 seconds (each time).
Doing a retry on our own initiative after this would be pos
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #6 from Shengjing Zhu ---
I'm the one that has complained "Timer expired" error when using
https://debuginfod.debian.net. Sergio points me this issue one week ago.
The problem is that I have a bad connection to the server. Log is
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
Shengjing Zhu changed:
What|Removed |Added
CC||zsj950618 at gmail dot com
--- Commen
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #4 from Frank Ch. Eigler ---
> having a big timeout does not necessarily mean that the download will
> succeeded, therefore having the possibility of retrying makes a lot of sense.
OK, retrying for an outright aborted connection
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #3 from Sergio Durigan Junior ---
(In reply to Frank Ch. Eigler from comment #1)
> Can you collect more information about the nature of the timeouts and
> what diagnostics if any libcurl/debuginfod-client returned? The default
> t
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
--- Comment #2 from Frank Ch. Eigler ---
BTW env DEBUGINFOD_VERBOSE=1 can assist collection of client side
diagnostics
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
Frank Ch. Eigler changed:
What|Removed |Added
CC||fche at redhat dot com
13 matches
Mail list logo
