From: Aaron Merey <amerey@redhat.com>
To: Milian Wolff <mail@milianw.de>
Cc: Mark Wielaard <mark@klomp.org>, elfutils-devel@sourceware.org
Subject: Re: caching failed lookups of debuginfo?
Date: Fri, 8 Apr 2022 17:34:06 -0400 [thread overview]
Message-ID: <CAJDtP-RvDssk9JwuAGLLtZfmqMK9OQoMX0U0G-_N54mJgKbZ1w@mail.gmail.com> (raw)
In-Reply-To: <19455068.ZVunK98tCv@milian-workstation>
Hi Milian,
On Fri, Apr 8, 2022 at 5:08 PM Milian Wolff <mail@milianw.de> wrote:
> I can reproduce it now suddenly with debuginfod-find too:
>
> ```
> $
> debuginfod-find debuginfo 85766e9d8458b16e9c7ce6e07c712c02b8471dbc
> debuginfod_find_debuginfo 85766e9d8458b16e9c7ce6e07c712c02b8471dbc
> server urls "https://debuginfod.archlinux.org/"
> checking build-id
> checking cache dir /home/milian/.cache/debuginfod_client
> using timeout 90
> init server 0 https://debuginfod.archlinux.org/buildid
> url 0 https://debuginfod.archlinux.org/buildid/
> 85766e9d8458b16e9c7ce6e07c712c02b8471dbc/debuginfo
> query 1 urls in parallel
> server response HTTP response code said error
> url 0 The requested URL returned error: 404
> not found No such file or directory (err=-2)
> Server query failed: No such file or directory
> ```
>
> I do see an empty `/home/milian/.cache/debuginfod_client/
> 85766e9d8458b16e9c7ce6e07c712c02b8471dbc/debuginfo` file. But the server is
> still queried (i.e. rerunning the above command always produces the same
> output for me). The lookup is costly too at ~70ms overall:
I am not able to reproduce this on Fedora 35 using commit 8db849976f070.
The first time I run debuginfod-find I get similar output to you:
```
debuginfod_find_debuginfo 85766e9d8458b16e9c7ce6e07c712c02b8471dbc
server urls "https://debuginfod.archlinux.org/"
checking build-id
checking cache dir /home/amerey/.cache/debuginfod_client
using timeout 90
init server 0 https://debuginfod.archlinux.org/buildid
url 0 https://debuginfod.archlinux.org/buildid/85766e9d8458b16e9c7ce6e07c712c02b8471dbc/debuginfo
query 1 urls in parallel
server response HTTP response code said error
url 0 The requested URL returned error: 404
not found No such file or directory (err=-2)
Server query failed: No such file or directory
```
But when I rerun debuginfod-find I get output indicating that the cache was
checked:
```
debuginfod_find_debuginfo 85766e9d8458b16e9c7ce6e07c712c02b8471dbc
server urls "https://debuginfod.archlinux.org/"
checking build-id
checking cache dir /home/amerey/.cache/debuginfod_client
not found No such file or directory (err=-2)
Server query failed: No such file or directory
```
No calls to curl_multi_wait occur. Is there a "cache_miss_s" file in the top
level of your debuginfod cache? It should contain the number of seconds
that must elapse after a failed attempt before another query would be
attempted (default is 600 seconds).
Aaron
next prev parent reply other threads:[~2022-04-08 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 19:58 Milian Wolff
2022-04-08 20:05 ` Frank Ch. Eigler
2022-04-08 20:45 ` Milian Wolff
2022-04-08 20:59 ` Mark Wielaard
2022-04-08 21:08 ` Milian Wolff
2022-04-08 21:34 ` Aaron Merey [this message]
2022-04-08 21:56 ` Milian Wolff
2022-04-08 22:21 ` Mark Wielaard
2022-04-08 22:23 ` Milian Wolff
2022-04-08 22:40 ` Mark Wielaard
2022-04-08 22:54 ` Aaron Merey
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=CAJDtP-RvDssk9JwuAGLLtZfmqMK9OQoMX0U0G-_N54mJgKbZ1w@mail.gmail.com \
--to=amerey@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mail@milianw.de \
--cc=mark@klomp.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).