Getting Started hash returns `merkledag: not found` #85

abacon · 2015-12-25T07:02:28Z

Fresh install of ipfs ipfs version 0.3.10 (prebuilt go binary for OSX, running 10.11.1)

The hash indicated in Getting Started isn't available.

> ipfs init
> ipfs cat /ipfs/QmPXME1oRtoT627YKaDPDQ3PwA8tdP9rWuAAweLzqSwAWT/readme
Error: merkledag: not found

RichardLitt · 2015-12-29T23:46:21Z

I was able to find it fine:

🐕  ipfs cat /ipfs/QmPXME1oRtoT627YKaDPDQ3PwA8tdP9rWuAAweLzqSwAWT/readme
Hello and Welcome to IPFS!

██╗██████╗ ███████╗███████╗
██║██╔══██╗██╔════╝██╔════╝
██║██████╔╝█████╗  ███████╗
██║██╔═══╝ ██╔══╝  ╚════██║
██║██║     ██║     ███████║
╚═╝╚═╝     ╚═╝     ╚══════╝

If you're seeing this, you have successfully installed
IPFS and are now interfacing with the ipfs merkledag!

 -------------------------------------------------------
| Warning:                                              |
|   This is alpha software. use at your own discretion! |
|   Much is missing or lacking polish. There are bugs.  |
|   Not yet secure. Read the security notes for more.   |
 -------------------------------------------------------

Check out some of the other files in this directory:

  ./about
  ./help
  ./quick-start     <-- usage examples
  ./readme          <-- this file
  ./security-notes

Maybe open this issue on ipfs/support or hop into the IRC channel?

chris-martin · 2016-02-28T01:17:06Z

Same error for me, using ipfs version 0.3.11 via NixOS.

chris-martin · 2016-02-28T02:19:09Z

It worked after I started ipfs daemon. Is that supposed to be a requirement?

RichardLitt · 2016-02-28T18:20:16Z

Oh! Yes, it is! And that explains the error above.

RichardLitt · 2016-02-28T18:25:21Z

Hmm. Actually, I'm not sure. @whyrusleeping @diasdavid Shouldn't this work without being connected?

daviddias · 2016-02-28T19:41:24Z

@RichardLitt that is because the init docs have changed (https://github.com/ipfs/go-ipfs/commits/master/assets/init-doc) but the hash on that welcome text hasn't. This means that everyone has indeed the welcome docs in their machine, but it is trying to load a older version that is available on the network (and so needs the daemon on).

RichardLitt · 2016-02-28T20:06:51Z

Hmm. How can I remove a version of the older file from my local so that I can reproduce?

daviddias · 2016-02-28T20:12:00Z

@RichardLitt the best way to reproduce is to backup your repo and init a new one, so you start on the same ground that @chris-martin and @abacon started

See ipfs-inactive#85

ohimors · 2016-06-11T01:07:46Z

I just downloade 0.4.2 and I had to manually start the daemon before Getting Started. Please update the Getting Started tutorial.

ghost · 2016-10-23T19:55:50Z

The error message could definitely be more helpful.

Manish166 · 2017-01-06T10:19:56Z

Using version ipfs version 0.4.4.
I have got my peer ID and started daemon...i am able to run all other command except cat ...
when i do cat it just stops there for long time.

Fixes ipfs-inactive/website#85

Fixes ipfs-inactive/website#85 License: MIT Signed-off-by: Timothy Hobbs <timothyhobbs@seznam.cz>

daviddias · 2017-08-23T05:58:53Z

This should not be an issue anymore. If anyone finds an issue in go-ipfs, please report at https://github.com/ipfs/go-ipfs

Thanks!

shroomist · 2017-08-30T21:49:21Z

still a problem here. installed and getting
#grep PeerID ~/.ipfs/config "PeerID": "QmW8DKrYwdatoKxnYt3jK9SKMfurAfQ9m8XGVhhaczF61z", #ipfs cat /ipfs/QmW8DKrYwdatoKxnYt3jK9SKMfurAfQ9m8XGVhhaczF61z Error: merkledag: not found

shroomist · 2017-08-30T21:54:09Z

ah sorry, i'll repost it there

renexdev · 2017-12-27T13:33:35Z

Hi there, I've got the same error at the very begining when I ran the code given in the section "init the repo" from the documentation (https://gateway.ipfs.io/ipfs/QmeYYwD4y4DgVVdAzhT7wW5vrvmbKPQj8wcV2pAzjbj886/docs/getting-started/). Maybe you wrote that peer identity instead the one given by your console output. Here was mine after initializing ipfs:

peer identity: Qmf6wk63u1YV4tgzExK1QrqzA6AcmNXArUtGmPnEi6LiTB
to get started, enter:

	ipfs cat /ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme

geeogi · 2018-03-07T23:13:17Z

same here. Running daemon fixed it.

proehlen · 2018-04-15T05:42:32Z

The getting started guide has the ipfs cat readme file step before the ipfs daemon command so it's a bit confusing.

kizerkizer · 2018-06-07T18:51:17Z

ADD ipfs daemon TO THE GETTING STARTED GUIDE!!

Stebalien · 2018-06-07T19:33:51Z

This should actually work without starting ipfs daemon. You only need to run ipfs daemon to fetch something from the network and we ship go-ipfs with these files. Unfortunately, we updated them and failed to update the guide (again).

Fix: #263

rustyx · 2018-07-02T08:48:18Z

@Stebalien On Windows it doesn't work without manually running ipfw daemon.

Stebalien · 2018-07-02T19:22:54Z

@rustyx try initializing a new repo and never running the daemon. Does that work (still a bug but trying to narrow it down)?

Also, what error do you get and what version are you using?

rustyx · 2018-07-02T20:10:46Z

@Stebalien I'm using version 0.4.16-rc1. It seems to be related to the FAR file manager that I'm using, as I now tried it in a regular cmd window and it's working fine.

Stebalien · 2018-07-02T20:25:15Z

Your file manager shouldn't make a difference. Could you elaborate?

rustyx · 2018-07-02T20:40:02Z

I know, weird right!?

whyrusleeping · 2018-07-02T20:41:20Z

@rustyx in your screenshot, youre running ipfs cat on a different hash than the one that init prints out

Stebalien · 2018-07-02T20:47:10Z

Hm. Did my update to the website not get automatically deployed? He's using the old hash on the website but that should have been fixed in #263. Are we not using CI to deploy?

rustyx · 2018-07-02T20:52:51Z

Oh I see. I got the path from the getting-started page, I guess that page is outdated?? The path starts working after starting the daemon, which added to my confusion.

whyrusleeping · 2018-07-02T21:01:20Z

yep. things work when you start your daemon because it can then fetch it from people who ran init with earlier versions of ipfs. Definitely one of the more confusing parts of our 'getting started' docs... I'm in favor of replacing the hash with <hash from your init output> so people don't just copy it.

We could also add more automation to keep things up to date, but thats harder and more prone to breaking.

michaelmcandrew · 2018-11-08T19:19:29Z

There is a note on https://docs.ipfs.io/introduction/usage/ that says:

The HASH in the ipfs cat /ipfs/HASH/readme line above may differ from the HASH in your output. If it does, use the one you got in the following instructions. Be sure not to confuse these hashes with your peer identity hash; ipfs cat /ipfs/PEER_ID/readme won't work.

I would argue that the above is key info and should not be in a 'pull out note'. (which to my mind suggests that it is content that can be skipped if you are in a hurry).

You could replace:

Now, try running:

ipfs cat /ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme

with:

Now try running the command that was suggested to you in the output of ipfs init. It looks like ipfs cat /ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme but the hash may be different in your case.

For a better first experience with IPFS

spudwa · 2019-09-08T09:26:09Z

ait@ipfsTest:$ ipfs daemon&
[1] 22369
ait@ipfsTest:$ Initializing daemon...
go-ipfs version: 0.4.22-
Repo version: 7
System version: amd64/linux
Golang version: go1.12.7
Swarm listening on /ip4/10.0.0.5/tcp/4001
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
WebUI: http://127.0.0.1:5001/webui
Gateway (readonly) server listening on /ip4/127.0.0.1/tcp/8080
Daemon is ready
ait@ipfsTest:~$ ipfs cat /ipfs/QmRdzqKJPVzjaUJsfFDyUdvZdAn3eidAAyQtehNczv2hmc/about

Just hangs

Stebalien · 2019-09-09T15:14:26Z

The content changes every so often. The new hash should be /ipfs/QmS4ustL54uo8FzR9455qaxZwuMiUhyvMcX9Ba8nUH4uVv.

Take a look at the message produced by ipfs init.

RichardLitt added a commit to RichardLitt/website that referenced this issue Feb 28, 2016

Update the Getting Started hash

7500a62

See ipfs-inactive#85

RichardLitt mentioned this issue Feb 28, 2016

Update the Getting Started hash #101

Merged

timthelion added a commit to timthelion/go-ipfs that referenced this issue Apr 9, 2017

Clarify error message when merkel dag is not found

920d2d9

Fixes ipfs-inactive/website#85

timthelion mentioned this issue Apr 9, 2017

Clarify error message when merkel dag is not found timthelion/go-ipfs#1

Closed

timthelion added a commit to timthelion/go-ipfs that referenced this issue Jul 28, 2017

Clarify error message when merkle dag is not found

1357cbe

Fixes ipfs-inactive/website#85 License: MIT Signed-off-by: Timothy Hobbs <timothyhobbs@seznam.cz>

timthelion added a commit to timthelion/go-ipfs that referenced this issue Jul 28, 2017

Clarify error message on merkeldag not found

d501ba8

Fixes ipfs-inactive/website#85 License: MIT Signed-off-by: Timothy Hobbs <timothyhobbs@seznam.cz>

timthelion mentioned this issue Jul 28, 2017

Clarify error message on merkeldag not found ipfs/kubo#4099

Closed

daviddias closed this as completed Aug 23, 2017

michaelmcandrew mentioned this issue Nov 8, 2018

Clearer instructions for running the get started command ipfs-inactive/docs#131

Merged

Getting Started hash returns `merkledag: not found` #85

Getting Started hash returns `merkledag: not found` #85

abacon commented Dec 25, 2015

RichardLitt commented Dec 29, 2015

chris-martin commented Feb 28, 2016

chris-martin commented Feb 28, 2016

RichardLitt commented Feb 28, 2016

RichardLitt commented Feb 28, 2016

daviddias commented Feb 28, 2016

RichardLitt commented Feb 28, 2016

daviddias commented Feb 28, 2016

ohimors commented Jun 11, 2016

ghost commented Oct 23, 2016

Manish166 commented Jan 6, 2017

daviddias commented Aug 23, 2017

shroomist commented Aug 30, 2017

shroomist commented Aug 30, 2017

renexdev commented Dec 27, 2017 •

edited

geeogi commented Mar 7, 2018

proehlen commented Apr 15, 2018

kizerkizer commented Jun 7, 2018

Stebalien commented Jun 7, 2018

rustyx commented Jul 2, 2018

Stebalien commented Jul 2, 2018

rustyx commented Jul 2, 2018

Stebalien commented Jul 2, 2018

rustyx commented Jul 2, 2018

whyrusleeping commented Jul 2, 2018

Stebalien commented Jul 2, 2018

rustyx commented Jul 2, 2018

whyrusleeping commented Jul 2, 2018

michaelmcandrew commented Nov 8, 2018 •

edited

spudwa commented Sep 8, 2019

Stebalien commented Sep 9, 2019

Getting Started hash returns merkledag: not found #85

Getting Started hash returns merkledag: not found #85

Comments

abacon commented Dec 25, 2015

RichardLitt commented Dec 29, 2015

chris-martin commented Feb 28, 2016

chris-martin commented Feb 28, 2016

RichardLitt commented Feb 28, 2016

RichardLitt commented Feb 28, 2016

daviddias commented Feb 28, 2016

RichardLitt commented Feb 28, 2016

daviddias commented Feb 28, 2016

ohimors commented Jun 11, 2016

ghost commented Oct 23, 2016

Manish166 commented Jan 6, 2017

daviddias commented Aug 23, 2017

shroomist commented Aug 30, 2017

shroomist commented Aug 30, 2017

renexdev commented Dec 27, 2017 • edited

geeogi commented Mar 7, 2018

proehlen commented Apr 15, 2018

kizerkizer commented Jun 7, 2018

Stebalien commented Jun 7, 2018

rustyx commented Jul 2, 2018

Stebalien commented Jul 2, 2018

rustyx commented Jul 2, 2018

Stebalien commented Jul 2, 2018

rustyx commented Jul 2, 2018

whyrusleeping commented Jul 2, 2018

Stebalien commented Jul 2, 2018

rustyx commented Jul 2, 2018

whyrusleeping commented Jul 2, 2018

michaelmcandrew commented Nov 8, 2018 • edited

spudwa commented Sep 8, 2019

Stebalien commented Sep 9, 2019

Getting Started hash returns `merkledag: not found` #85

Getting Started hash returns `merkledag: not found` #85

renexdev commented Dec 27, 2017 •

edited

michaelmcandrew commented Nov 8, 2018 •

edited