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: ipfs daemon failed to start and produced no output (see error.log #2797

Open
stevenshen777 opened this issue Apr 28, 2024 · 1 comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@stevenshen777
Copy link

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

Specifications

  • OS: win32 6.1.7601
  • IPFS Desktop Version: 0.34.0
  • Electron Version: 19.1.9
  • Chrome Version: 102.0.5005.167

Error

Error: ipfs daemon failed to start and produced no output (see error.log for details)
    at errorTemplate (H:\Users\Administrator\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\migration-prompt.js:78:49)
    at loadWindow (H:\Users\Administrator\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\migration-prompt.js:129:26)
    at showMigrationPrompt (H:\Users\Administrator\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\migration-prompt.js:134:3)
    at startIpfsWithLogs (H:\Users\Administrator\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:193:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async startDaemon (H:\Users\Administrator\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:216:27)
    at async startIpfs (H:\Users\Administrator\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\index.js:49:17)
    at async restartIpfs (H:\Users\Administrator\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\daemon\index.js:103:5)%0
@stevenshen777 stevenshen777 added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Apr 28, 2024
Copy link

welcome bot commented Apr 28, 2024

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.

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) need/triage Needs initial labeling and prioritization
Projects
No open projects
Status: No status
Development

No branches or pull requests

1 participant