IPFS Daemon will not start after process abruptly stops

[dondreytaylor]

Version information:

go-ipfs version: 0.4.9-
Repo version: 5
System version: 386/linux
Golang version: go1.8.1

Type:

Bug

Severity:

High

Description:

It appears that my IPFS daemon will not start anymore after running for a few days and abruptly stopping without warning . Any time I attempt to start the IPFS daemon it hangs at Successfully raised file descriptor limit to 2048.

I noticed a repo.lock gets created when this happens, which I delete before attempting to start the daemon again. I can't seem to figure out why this happened all of sudden. My machine has quite a lot of disk space left. If anyone has experienced this issue, would definitely appreciate the help. Screenshot of the point where the IPFS daemon hangs is below.

[Kubuxu]

Can you try reproducing it with setting IPFS_LOGGING=debug environment variable?
It might give us some more insight.

[dondreytaylor]

Okay I'll try it now

[dondreytaylor]

After running it with IPFS_LOGGING=debug it seems to still hang.

Also tried it with the debug flag too. When it gets to the end it drops my ssh connection into the machine.

[Kubuxu]

It might be a problem with router and establishing UPnP mapping. Can you try restarting your router?

[Kubuxu]

(for the IPFS_LOGGING to take place you would have to export it export IPFS_LOGGING but it achieved similar result as IPFS_DEBUG).

[dondreytaylor]

Ah okay, forgot the export. Okay I'm going to restart my router now.

[dondreytaylor]

Wow, you were right on the money with that one. As soon as I restarted my router the IPFS daemon started up perfectly. Thanks.

[Kubuxu]

Another case of #3320 this time bad implementation of UPnP caused the problem. Fault is on the manufacturer's side but we should try not to cause it.

@dondreytaylor would you be possible for you to write down here manufacturer, model, specs and firmware version of your router?

[dondreytaylor]

Oh wow, totally missed this. I kept searching "daemon stopped" which is probably why I missed it. I see, so the implementation of UPnP seems to cause problems at times.

[dondreytaylor]

Sure I'll get my router information now and comment it here.

[Kubuxu]

I have never met this problem before in this form, so this is something completely new (it would be hard to find), It is also a bit other case of #3320 as the router wasn't dying, it just had problem with UPnP and possibly new connections.

[dondreytaylor]

Yeah, this one would have been difficult to replicate in a test environment for sure lol

The router that I'm using is:

Brand: D-Link
Model: DIR-868L
Hardware Version: A1
Firmware Version: 6.0.9.1.86.1.7

[Kubuxu]

If the problem repeats I would try giving it a firmware update (if there is one). Have fun with IPFS.

[dondreytaylor]

Okay, I definitely will. Thanks @Kubuxu for all your help!