Go-ipfs: ipfs deamon command fail

Created on 23 Feb 2018  路  15Comments  路  Source: ipfs/go-ipfs

the command failed
~
ipfs deamon
~

with log:

~
Initializing daemon...
Swarm listening on /ip4/10.66.66.41/tcp/4001
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmXYxadGxRcKikecQzsR2V8cukCaebLUWzphjaSXhB3drm
Swarm announcing /ip4/10.66.66.41/tcp/4001
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
Error: serveHTTPApi: manet.Listen(/ip4/127.0.0.1/tcp/5001) failed: listen tcp4 127.0.0.1:5001: bind: address already in use
~

but i check the network port, the 5001 is not used.

~
STONEDONG-MB4 :: Application Support/ipfs-desktop/logs % lsof -i tcp:5001
STONEDONG-MB4 :: Application Support/ipfs-desktop/logs %
~

All 15 comments

小锌褋 邪 褌械锌械褉褜 锌芯 褉褍褋褋泻懈

@yishuiliunian could you also paste the output of ipfs version --all?

@Mehcta Please use english on this issue tracker / 袩芯卸邪谢褍泄褋褌邪, 懈褋锌芯谢褜蟹褍泄褌械 邪薪谐谢懈泄褋泻懈泄 薪邪 褝褌芯屑 褌褉械泻械褉

@VictorBjelkholm

it may the newest
~
go-ipfs version: 0.4.13-
Repo version: 6
System version: amd64/darwin
Golang version: go1.9.2
~

@yishuiliunian thanks. Can you also check with running lsof with sudo? Might be some process that is listening that you don't own.

I'm getting this as well.

$ sudo lsof -i tcp:5001
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
ipfs    2109 root   11u  IPv4  62213      0t0  TCP localhost:5001 (LISTEN)

I used ipfs shutdown which then returns nothing for sudo lsof -i tcp:5001 however when I try and start back up the daemon it catches on the port error again.

Error: serveHTTPApi: manet.Listen(/ip4/127.0.0.1/tcp/5001) failed: listen tcp4 127.0.0.1:5001: bind: address already in use

@tyvdh can you try running the daemon with IPFS_REUSEPORT=false ipfs daemon? (reboot might be needed)

@magik6k Definitely seems to be working better!

That should have absolutely nothing to do with this issue... Could you try running without the IPFS_REUSEPORT again (just to make sure)?

@tyvdh Were you able to resolve this? Apparently IPFS_REUSEPORT=false ipfs daemon didnt work for me. And I am doing this on Azure VM. Any pointers?

@singhswg what's the exact error message you're getting?

@magik6k I am trying to run a IPFS deamon on a Azure VM, and I get this error

Error: serveHTTPApi: manet.Listen(/ip4/<---IP--->/tcp/5001) failed: listen tcp4 <---IP--->:5001: bind: cannot assign requested address

Nothing is running on this port, I confirmed doing lsof -i tcp:5001 as root. I am using a static Azure IP.

@singhswg Can you confirm that the address you are trying to assign actually exists on the machine (check ip addr)?

Btw, exposing unfiltered :5001 to the internet is probably a bad idea since it's the admin port which allows you to execute every command you can with the ipfs [...]

@magik6k Yes i am aware but thanks for the heads up!

No I cant see the IP, neither does ping work. I guess maybe it's something with Azure VMs...

Check the Addresses.API config option. It looks like your machine's IP may not match it.

I'm going to close this for now as I don't think there's anything we can do on our side. Feel free to ask follow up questions or reopen this issue if you feel otherwise.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

whyrusleeping picture whyrusleeping  路  4Comments

daviddias picture daviddias  路  3Comments

Mikaela picture Mikaela  路  3Comments

slrslr picture slrslr  路  3Comments

whyrusleeping picture whyrusleeping  路  4Comments