Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gui error report] Error: Initializing daemon... #2130

Closed
do-nothing opened this issue May 9, 2022 · 2 comments
Closed

[gui error report] Error: Initializing daemon... #2130

do-nothing opened this issue May 9, 2022 · 2 comments
Labels
kind/bug A bug in existing code (including security flaws) status/duplicate A question or request for support

Comments

@do-nothing
Copy link

👉️ Please describe what you were doing when this error happened.

Specifications

  • OS: win32
  • IPFS Desktop Version: 0.20.5
  • Electron Version: 18.0.3
  • Chrome Version: 100.0.4896.75

Error

Error: Initializing daemon...
go-ipfs version: 0.12.2
Repo version: 12
System version: amd64/windows
Golang version: go1.16.15
Found outdated fs-repo, migrations need to be run.
Looking for suitable migration binaries.
Need 1 migrations, downloading.
Downloading migration: fs-repo-11-to-12...
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions"
Error fetching: exceeded number of retries. last error was http.DefaultClient.Do error: Get "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions": dial tcp 192.133.77.189:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Fetching with IPFS: "fs-repo-11-to-12/versions"
Error fetching: context deadline exceeded
could not get latest version of migration fs-repo-11-to-12: 2 errors occurred:
	* exceeded number of
@do-nothing do-nothing added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels May 9, 2022
@welcome
Copy link

welcome bot commented May 9, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@SgtPooki SgtPooki added status/duplicate A question or request for support and removed need/triage Needs initial labeling and prioritization labels May 9, 2022
@SgtPooki
Copy link
Member

SgtPooki commented May 9, 2022

Thanks for submitting this error report! Is that the end of the error log, or is there more you can share?

This seems to be a duplicate of #2099 (comment), can you follow the steps mentioned there? You can follow along on an issue for improving this error messaging at ipfs/kubo#8911.

@SgtPooki SgtPooki closed this as completed May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) status/duplicate A question or request for support
Projects
None yet
Development

No branches or pull requests

2 participants