Unable to update registry `crates-io`

[werdahias]

Problem

OS: Debian testing
Rustc version: rustc 1.59.0-nightly
cargo version: cargo 1.59.0-nightly

I am not able to build any rust project with cargo. It doesn't matter whether I have cargo/rustc installed by rustup or via apt. Switching from stable to nightly didn't resovel the issue either. All attemps at building throw the following error:

$ cargo build
    Updating crates.io index
error: failed to get `bytes` as a dependency of package `onenote_parser v0.3.0 (/home/user/onenote.rs)`

Caused by:
  failed to load source for dependency `bytes`

Caused by:
  Unable to update registry `crates-io`

Caused by:
  failed to fetch `https://github.com/rust-lang/crates.io-index`

Caused by:
  an unknown git error occurred; code=NotFound (-3)

Steps

No response

Possible Solution(s)

No response

Notes

No response

Version

No response

[ehuss]

If possible, can you ZIP up the contents of ~/.cargo/registry/index/github.com-1ecc6299db9ec823/ and post it here or somewhere? Afterwards, I think you can delete that directory and it should help.

[werdahias]

Zip file:
github.com-1ecc6299db9ec823.zip
deleting the whole registry folder didn't resolve the error.

[ehuss]

Hm, that's strange! This seems suspicious that this would be reported now, as we just squashed the index a few days ago (2021-12-21T00:22:52). Unfortunately the zip file doesn't show much, as it is just an empty repo.

Perhaps you can help debug this a little? Can you show the output of git config -l? Be sure to remove anything that is private. Another thing that might help is to set the environment variable CARGO_LOG=trace and run cargo fetch and post the output.

Can you show the output of nslookup github.com? As a very unlikely guess, maybe the squash corrupted one of github's caches.

Can you clone the index using the git cli? Try setting the environment variable CARGO_NET_GIT_FETCH_WITH_CLI=true and run cargo fetch and see if it succeeds.

[werdahias]

git config -l show up empty. Setting the environment variable and running cargo fetch gets me the same error (same goes for log).

nslookup github.com
Server:		192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
Name:	github.com
Address: 140.82.113.3

[ehuss]

Hm. CARGO_LOG=trace should have enabled logging. I would expect a few dozen log lines that look like this:

2021-12-25T16:28:40Z TRACE cargo::core::registry] clear_lock
[2021-12-25T16:28:40Z TRACE cargo::core::registry] register_lock: foo v0.1.0 (/root/foo)
[2021-12-25T16:28:40Z TRACE cargo::core::registry]      -> toml v0.5.8
[2021-12-25T16:28:40Z TRACE cargo::core::registry] register_lock: serde v1.0.132
[2021-12-25T16:28:40Z TRACE cargo::core::registry] register_lock: toml v0.5.8
[2021-12-25T16:28:40Z TRACE cargo::core::registry]      -> serde v1.0.132
[2021-12-25T16:28:40Z DEBUG cargo::ops::resolve] attempting to prefer foo v0.1.0 (/root/foo)
[2021-12-25T16:28:40Z DEBUG cargo::ops::resolve] attempting to prefer serde v1.0.132
[2021-12-25T16:28:40Z DEBUG cargo::ops::resolve] attempting to prefer toml v0.5.8
[2021-12-25T16:28:40Z DEBUG cargo::core::registry] load/missing  /root/foo
[2021-12-25T16:28:40Z DEBUG cargo::core::registry] loading source /root/foo
[2021-12-25T16:28:40Z DEBUG cargo::sources::config] loading: /root/foo
[2021-12-25T16:28:40Z TRACE cargo::core::source::source_id] loading SourceId; /root/foo
[2021-12-25T16:28:40Z TRACE cargo::ops::cargo_read_manifest] read_package; path=/root/foo/Cargo.toml; source-id=/root/foo
[2021-12-25T16:28:40Z TRACE cargo::util::toml] read_manifest; path=/root/foo/Cargo.toml; source-id=/root/foo
[2021-12-25T16:28:40Z TRACE cargo::core::registry] locking summary of foo v0.1.0 (/root/foo)
[2021-12-25T16:28:40Z TRACE cargo::core::registry]      toml/^0.5/registry `crates-io`
[2021-12-25T16:28:40Z TRACE cargo::core::registry]      first hit on toml v0.5.8
[2021-12-25T16:28:40Z TRACE cargo::core::dependency] locking dep from `toml` with `^0.5` at registry `crates-io` to toml v0.5.8
[2021-12-25T16:28:40Z DEBUG cargo::core::resolver] initial activation: foo v0.1.0 (/root/foo)
[2021-12-25T16:28:40Z TRACE cargo::core::resolver] activating foo v0.1.0 (/root/foo)
[2021-12-25T16:28:40Z DEBUG cargo::core::registry] load/missing  registry `crates-io`
[2021-12-25T16:28:40Z DEBUG cargo::core::registry] loading source registry `crates-io`
[2021-12-25T16:28:40Z DEBUG cargo::sources::config] loading: registry `crates-io`
[2021-12-25T16:28:40Z TRACE cargo::core::source::source_id] loading SourceId; registry `crates-io`
[2021-12-25T16:28:40Z DEBUG cargo::sources::registry] skipping update due to locked registry
[2021-12-25T16:28:40Z DEBUG cargo::sources::registry] attempting query without update
[2021-12-25T16:28:40Z TRACE cargo::sources::registry::remote] acquiring registry index lock
[2021-12-25T16:28:40Z DEBUG cargo::sources::registry::index] slow path for "to/ml/toml"
[2021-12-25T16:28:40Z DEBUG cargo::sources::registry] falling back to an update
[2021-12-25T16:28:40Z DEBUG cargo::sources::registry::remote] updating the index

And CARGO_NET_GIT_FETCH_WITH_CLI=true should have given a different output, as it doesn't use the internal git library. The error posted in the original comment only comes from the internal library.

Can you make sure to delete the ~/.cargo/registry directory before running the commands?

[werdahias]

I did delete the registry beforehand. Then I ran the commands like this:

~/test$ CARGO_LOG=trace
~/test$ cargo fetch
    Updating crates.io index
error: failed to get `bytes` as a dependency of package `test v1.0.0 (/home/user/test)`

Caused by:
  failed to load source for dependency `bytes`

Caused by:
  Unable to update registry `crates-io`

Caused by:
  failed to fetch `https://github.com/rust-lang/crates.io-index`

Caused by:
  an unknown git error occurred; code=NotFound (-3)

test is a hello world program. I still get the same error.

[ehuss]

~/test$ CARGO_LOG=trace
~/test$ cargo fetch

Ah, in most shells just typing a variable on a separate line like that doesn't "export" it so that programs like cargo can see it. You either have to place it all on one line:

CARGO_LOG=trace cargo fetch

or export it:

export CARGO_LOG=trace
cargo fetch

[werdahias]

ah ok, my bad. log trace is attached. It seems to work with CARGO_NET_GIT_FETCH_WITH_CLI=true
log_trace.txt
.

[wyatt8740]

I have the same issue on PowerPC Debian with a brand new install. CARGO_NET_GIT_FETCH_WITH_CLI=true seemed to fix things for me as well.

[ElijahLynn]

I had this too, but have an issue with my ssh-agent and it wasn't loading the key. I was able to run ssh -T git@github.com to test the auth and prompt for the passphrase for my key. Then a cargo run completed successfully without this error because it had the key loaded from my GitHub priming test. I gotta fix my ssh auth now.

I was able to figure this out because of this thread/issue and export CARGO_LOG=trace. Thanks!

[ElijahLynn]

Related #7662