Hi,
On Sat, 5 Jan 2019 17:48:31 +0100 Vincent Smeets
wrote:
> Hallo,
>
> I want to add that I don't know how to reproduce the SIGSEGV. It
> happends when I am developing containers, but also during my breaks
> (screenlock). Testing a solution will be difficult.
>
> Here are todays SIGSEGVs:
>
> vincent@PC-Vincent:~$ sudo journalctl -b0 | grep SIGSEGV
> jan 05 10:36:18 PC-Vincent dockerd[954]: [signal SIGSEGV: segmentation
> violation code=0x1 addr=0x0 pc=0x564a9d3a2158]
> jan 05 11:13:36 PC-Vincent dockerd[18723]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x555897453158]
> jan 05 12:00:59 PC-Vincent dockerd[32147]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x560bac7a1158]
> jan 05 12:42:33 PC-Vincent dockerd[14174]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x559c2e092158]
> jan 05 13:12:36 PC-Vincent dockerd[29099]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x564e8f238158]
> jan 05 13:42:40 PC-Vincent dockerd[4024]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x56084fc6a158]
> jan 05 14:12:43 PC-Vincent dockerd[13242]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x89727158]
> jan 05 14:42:46 PC-Vincent dockerd[23871]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x55acb4c17158]
> jan 05 15:12:50 PC-Vincent dockerd[30296]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x5599f09e7158]
> jan 05 15:42:53 PC-Vincent dockerd[4545]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x55593e7e2158]
> jan 05 16:12:56 PC-Vincent dockerd[9021]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x5630b39d9158]
> jan 05 16:43:00 PC-Vincent dockerd[13117]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x55f1fe291158]
> jan 05 17:13:03 PC-Vincent dockerd[17369]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x556626f84158]
> jan 05 17:43:06 PC-Vincent dockerd[22316]: [signal SIGSEGV:
> segmentation violation code=0x1 addr=0x0 pc=0x55bc4ddbc158]
> vincent@PC-Vincent:~$
Same pattern here. I've migrated for testing purpose standalone compose
mode containers to a single node swarm, and the docker service now
segfaults every 30 minutes with:
juin 06 21:30:34 serveur dockerd[10190]: panic: runtime error: invalid
memory address or nil pointer dereference
juin 06 21:30:34 serveur dockerd[10190]: [signal SIGSEGV: segmentation
violation code=0x1 addr=0x0 pc=0x55fc93504388]
juin 06 21:30:34 serveur dockerd[10190]: goroutine 1358 [running]:
juin 06 21:30:34 serveur dockerd[10190]:
github.com/armon/go-radix.recursiveWalk(0x0, 0xc003805e08, 0x55fc946a8900)
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/armon/go-radix/radix.go:519
+0x28
juin 06 21:30:34 serveur dockerd[10190]:
github.com/armon/go-radix.recursiveWalk(0xc004ec8f90, 0xc003805e08,
0xc003805c00)
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/armon/go-radix/radix.go:525
+0x7a
juin 06 21:30:34 serveur dockerd[10190]:
github.com/armon/go-radix.recursiveWalk(0xc003379e30, 0xc003805e08,
0xc003805c00)
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/armon/go-radix/radix.go:525
+0x7a
juin 06 21:30:34 serveur dockerd[10190]:
github.com/armon/go-radix.recursiveWalk(0xc004ec8750, 0xc003805e08, 0x19)
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/armon/go-radix/radix.go:525
+0x7a
juin 06 21:30:34 serveur dockerd[10190]:
github.com/armon/go-radix.(*Tree).WalkPrefix(0xc0055ab620, 0xc0062ebaa0,
0x1a, 0xc003805e08)
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/armon/go-radix/radix.go:473
+0xdb
juin 06 21:30:34 serveur dockerd[10190]:
github.com/docker/libnetwork/networkdb.(*NetworkDB).reapTableEntries(0xc005308c60)
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/libnetwork/networkdb/cluster.go:396
+0x3c5
juin 06 21:30:34 serveur dockerd[10190]:
github.com/docker/libnetwork/networkdb.(*NetworkDB).reapState(0xc005308c60)
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/libnetwork/networkdb/cluster.go:362
+0x2d
juin 06 21:30:34 serveur dockerd[10190]:
github.com/docker/libnetwork/networkdb.(*NetworkDB).reapState-fm()
juin 06 21:30:34 serveur dockerd[10190]:
/build/docker.io-X5uIDh/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/libnetwork/networkdb/cluster.go:170
+0x2c
juin 06 21:30:34 serveur dockerd[10190]:
github.com/docker/libnetwork/networkdb.(*NetworkDB).triggerFunc(0xc005308c60,
0x12a05f200, 0xc000cbd1a0, 0xc002703e60)
juin 06 21:30:34 serveur dockerd[10190]:
