IPFS Daemon killed after about 10 minutes

[frogg]

Version information:

go-ipfs version: 0.4.14-
Repo version: 6
System version: 386/linux
Golang version: go1.10

Type:

Bug

Description:

For me, the deamon gets killed after about 10 minutes:

$ ipfs daemon
Daemon is ready
…
Killed

Here are the logs of the crash:

12:21:58.216 DEBUG   addrutil: adding resolved addr:/ip4/0.0.0.0/tcp/4001 /ip4/127.0.0.1/tcp/4001 [/ip4/127.0.0.1/tcp/4001] addr.go:188
12:21:58.261 DEBUG        dht: handleFindPeer: sending back '<peer.ID Qjfb2B>' handlers.go:34
12:21:58.284 DEBUG        dht: handleFindPeer: sending back '<peer.ID QBdnST>' handlers.go:34
12:21:58.339 DEBUG        dht: <peer.ID Xfo2Cd> handleGetProviders(<peer.ID c3CNay>, QmWE34z6J1FGhpdv1yQCQnJLfGVs4jWs63RTUTE7tZUbuE):  begin handlers.go:38
12:21:58.360 DEBUG        dht: <peer.ID Xfo2Cd> adding <peer.ID RztqxT> as a provider for 'QmRSsLxs1WqUCdjSstQ9oD6SYeLnEPknW3DJyuJ4eSbqjQ'
 handlers.go:36
12:21:58.399 DEBUG        dht: <peer.ID Xfo2Cd> handleGetProviders(<peer.ID Y8sS9E>, QmY8sS9EG7UF3g4s2t568fQxzYtv5Hk24YrACwWfa4B6bc):  begin handlers.go:38
12:21:57.137 WARNI  basichost: protocol mux failed: connection reset (took 5.586065ms) basic_host.go:175
12:21:57.158 DEBUG     swarm2: [<peer.ID Xfo2Cd>] network opening stream to peer [<peer.ID QTT2YJ>] basic_host.go:355
12:21:58.536  INFO    connmgr: tried to remove tag from untracked peer: <peer.ID W2d9g2> dht.go:108
12:21:58.575 DEBUG     engine: <peer.ID URr65b> cancel QmbxSsG7ep3x5omb9K9RZvMEefnKXhqrrC3qhohgYJGxVT bitswap.go:365
12:21:58.606 DEBUG        dht: handleFindPeer: sending back '<peer.ID X5FMLN>' handlers.go:34
12:22:03.271 DEBUG net/identi: /ipfs/id/1.0.0 received message from <peer.ID Ve2FW4> /ip6/2001:0:9d38:90d7:1490:fa47:541a:bcc/tcp/52077 id.go:112
12:21:59.493 DEBUG        dht: PEERS CLOSER -- worker for: <peer.ID U6NeD2> added <peer.ID VGX47B> ([]) query.go:208
12:22:01.741 DEBUG        dht: got back nil response from request asm_386.s:1665
Killed

[magik6k]

It might get OOM killed, can you check dmesg when this happens and see if there is anything related?

[whyrusleeping]

Thats really strange. @frogg how much memory does your machine have?

[frogg]

@whyrusleeping the machine this was running on has only 1GB of memory.

[Stebalien]

@frogg it was almost certainly OOM killed. Check dmesg.

You can significantly reduce the amount of memory go-ipfs uses by:

1. Turning of the DHT server (run the daemon with --routing=dhtclient).
2. Reducing the number of connections you keep alive. Try reducing the Swarm.ConnMgr.HighWater and LowWater config options.

[Stebalien]

Closing due to inactivity. This looks like yet another "we need to reduce memory" bug.