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

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

Closed
abacon opened this Issue Dec 25, 2015 · 28 comments

Comments

Projects
None yet
@abacon

abacon commented Dec 25, 2015

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

This comment has been minimized.

Show comment
Hide comment
@RichardLitt

RichardLitt Dec 29, 2015

Member

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?

Member

RichardLitt commented Dec 29, 2015

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

This comment has been minimized.

Show comment
Hide comment
@chris-martin

chris-martin Feb 28, 2016

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

chris-martin commented Feb 28, 2016

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

@chris-martin

This comment has been minimized.

Show comment
Hide comment
@chris-martin

chris-martin Feb 28, 2016

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

chris-martin commented Feb 28, 2016

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

@RichardLitt

This comment has been minimized.

Show comment
Hide comment
@RichardLitt

RichardLitt Feb 28, 2016

Member

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

Member

RichardLitt commented Feb 28, 2016

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

@RichardLitt

This comment has been minimized.

Show comment
Hide comment
@RichardLitt

RichardLitt Feb 28, 2016

Member

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

Member

RichardLitt commented Feb 28, 2016

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

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Feb 28, 2016

Member

@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).

Member

diasdavid commented Feb 28, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@RichardLitt

RichardLitt Feb 28, 2016

Member

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

Member

RichardLitt commented Feb 28, 2016

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

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Feb 28, 2016

Member

@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

Member

diasdavid commented Feb 28, 2016

@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

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

@ohimors

This comment has been minimized.

Show comment
Hide comment
@ohimors

ohimors Jun 11, 2016

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

ohimors commented Jun 11, 2016

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

@voltagex

This comment has been minimized.

Show comment
Hide comment
@voltagex

voltagex Oct 23, 2016

The error message could definitely be more helpful.

voltagex commented Oct 23, 2016

The error message could definitely be more helpful.

@Manish166

This comment has been minimized.

Show comment
Hide comment
@Manish166

Manish166 Jan 6, 2017

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.

Manish166 commented Jan 6, 2017

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.

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

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

Clarify error message when merkle dag is not found
Fixes ipfs/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
Fixes ipfs/website#85

License: MIT
Signed-off-by: Timothy Hobbs <timothyhobbs@seznam.cz>
@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Aug 23, 2017

Member

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!

Member

diasdavid commented Aug 23, 2017

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!

@diasdavid diasdavid closed this Aug 23, 2017

@shroomist

This comment has been minimized.

Show comment
Hide comment
@shroomist

shroomist Aug 30, 2017

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

shroomist commented Aug 30, 2017

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

@shroomist

This comment has been minimized.

Show comment
Hide comment
@shroomist

shroomist Aug 30, 2017

ah sorry, i'll repost it there

shroomist commented Aug 30, 2017

ah sorry, i'll repost it there

@renexdev

This comment has been minimized.

Show comment
Hide comment
@renexdev

renexdev Dec 27, 2017

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

renexdev commented Dec 27, 2017

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

This comment has been minimized.

Show comment
Hide comment
@geeogi

geeogi Mar 7, 2018

same here. Running daemon fixed it.

geeogi commented Mar 7, 2018

same here. Running daemon fixed it.

@proehlen

This comment has been minimized.

Show comment
Hide comment
@proehlen

proehlen Apr 15, 2018

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

proehlen commented Apr 15, 2018

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

@kizerkizer

This comment has been minimized.

Show comment
Hide comment
@kizerkizer

kizerkizer Jun 7, 2018

ADD ipfs daemon TO THE GETTING STARTED GUIDE!!

kizerkizer commented Jun 7, 2018

ADD ipfs daemon TO THE GETTING STARTED GUIDE!!

@Stebalien

This comment has been minimized.

Show comment
Hide comment
@Stebalien

Stebalien Jun 7, 2018

Contributor

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

Contributor

Stebalien commented Jun 7, 2018

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

This comment has been minimized.

Show comment
Hide comment
@rustyx

rustyx Jul 2, 2018

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

rustyx commented Jul 2, 2018

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

@Stebalien

This comment has been minimized.

Show comment
Hide comment
@Stebalien

Stebalien Jul 2, 2018

Contributor

@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?

Contributor

Stebalien commented Jul 2, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@rustyx

rustyx Jul 2, 2018

@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.

rustyx commented Jul 2, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@Stebalien

Stebalien Jul 2, 2018

Contributor

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

Contributor

Stebalien commented Jul 2, 2018

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

@rustyx

This comment has been minimized.

Show comment
Hide comment
@rustyx

rustyx Jul 2, 2018

I know, weird right!?
ipfs far issue

rustyx commented Jul 2, 2018

I know, weird right!?
ipfs far issue

@whyrusleeping

This comment has been minimized.

Show comment
Hide comment
@whyrusleeping

whyrusleeping Jul 2, 2018

Member

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

Member

whyrusleeping commented Jul 2, 2018

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

@Stebalien

This comment has been minimized.

Show comment
Hide comment
@Stebalien

Stebalien Jul 2, 2018

Contributor

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?

Contributor

Stebalien commented Jul 2, 2018

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

This comment has been minimized.

Show comment
Hide comment
@rustyx

rustyx Jul 2, 2018

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.

rustyx commented Jul 2, 2018

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

This comment has been minimized.

Show comment
Hide comment
@whyrusleeping

whyrusleeping Jul 2, 2018

Member

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.

Member

whyrusleeping commented Jul 2, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment