public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "zsj950618 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27531] Support retry of failed downloads
Date: Sun, 14 Mar 2021 17:16:57 +0000	[thread overview]
Message-ID: <bug-27531-10460-5dpbryUXao@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27531-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27531

--- Comment #6 from Shengjing Zhu <zsj950618 at gmail dot com> ---
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 attached with
DEBUGINFOD_VERBOSE=1.

url 0
https://debuginfod.debian.net/buildid/75703faf54dc0d3014ce34c9ce110eb6fe217818/debuginfo
query 1 urls in parallel
Downloading separate debug info for
/lib/x86_64-linux-gnu/libapt-private.so.0.0...
committed to url 0
server response Timeout was reached
url 0 Operation too slow. Less than 102400 bytes/sec transferred the last 90
seconds
not found Timer expired (err=-62)
Download failed: Timer expired.  Continuing without debug info for
/lib/x86_64-linux-gnu/libapt-private.so.0.0.


$ curl -v
https://debuginfod.debian.net/buildid/75703faf54dc0d3014ce34c9ce110eb6fe217818/debuginfo
-o /dev/null 
<skip>
{ [5 bytes data]
100 2700k  100 2700k    0     0  20137      0  0:02:17  0:02:17 --:--:-- 24550
* Connection #0 to host debuginfod.debian.net left intact

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-03-14 17:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06  7:46 [Bug debuginfod/27531] New: " sergiodj at sergiodj dot net
2021-03-06 18:08 ` [Bug debuginfod/27531] " fche at redhat dot com
2021-03-07  2:34 ` fche at redhat dot com
2021-03-07 20:38 ` sergiodj at sergiodj dot net
2021-03-07 22:04 ` fche at redhat dot com
2021-03-14 17:14 ` zsj950618 at gmail dot com
2021-03-14 17:16 ` zsj950618 at gmail dot com [this message]
2021-03-14 17:29 ` fche at redhat dot com
2021-03-14 18:02 ` zsj950618 at gmail dot com
2021-03-14 18:03 ` zsj950618 at gmail dot com
2021-03-14 22:58 ` fche at redhat dot com
2021-03-14 23:07 ` sergiodj at sergiodj dot net
2021-03-18 16:54 ` fche at redhat dot com
2021-07-09 13:58 ` mark at klomp dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27531-10460-5dpbryUXao@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).