nathanleclaire
commented
8 years ago which machine version is this?
Closed buckett closed 7 years ago
nathanleclaire
commented
8 years ago which machine version is this?
ahmetb
commented
7 years ago @buckett is there any possibility that you were resizing your terminal as docker-machine was running? https://github.com/golang/go/issues/16468
buckett
commented
7 years ago @nathanleclaire docker-machine 0.8.1
@ahmetalpbalkan I don't think so, I'm not able to reliably reproduce it, although when running dm status in a loop I did just get another stack trace (docker-machine 0.8.1 and macOS 10.12.1):
fatal error: unexpected signal during runtime execution
[signal 0xb code=0x1 addr=0xb01dfacedebac1e pc=0x12e8b]
runtime stack:
runtime.throw(0x18c89c0, 0x2a)
/usr/local/go/src/runtime/panic.go:547 +0x90
runtime.sigpanic()
/usr/local/go/src/runtime/sigpanic_unix.go:12 +0x5a
runtime.unlock(0x22d24e0)
/usr/local/go/src/runtime/lock_sema.go:107 +0x14b
runtime.(*mheap).alloc_m(0x22d24e0, 0xb, 0x100000000, 0x22d3cf0)
/usr/local/go/src/runtime/mheap.go:492 +0x314
runtime.(*mheap).alloc.func1()
/usr/local/go/src/runtime/mheap.go:502 +0x41
runtime.systemstack(0x7fff5fbfece0)
/usr/local/go/src/runtime/asm_amd64.s:307 +0xab
runtime.(*mheap).alloc(0x22d24e0, 0xb, 0x10100000000, 0x1883c)
/usr/local/go/src/runtime/mheap.go:503 +0x63
runtime.largeAlloc(0x16000, 0x0, 0xc)
/usr/local/go/src/runtime/malloc.go:766 +0xb3
runtime.mallocgc.func3()
/usr/local/go/src/runtime/malloc.go:664 +0x33
runtime.systemstack(0x22cd500)
/usr/local/go/src/runtime/asm_amd64.s:291 +0x79
runtime.mstart()
/usr/local/go/src/runtime/proc.go:1051
goroutine 1 [running, locked to thread]:
runtime.systemstack_switch()
/usr/local/go/src/runtime/asm_amd64.s:245 fp=0xc820041970 sp=0xc820041968
runtime.mallocgc(0x16000, 0x132f260, 0x0, 0x6c0c)
/usr/local/go/src/runtime/malloc.go:665 +0x9eb fp=0xc820041a48 sp=0xc820041970
runtime.newarray(0x132f260, 0x200, 0x4)
/usr/local/go/src/runtime/malloc.go:798 +0xc9 fp=0xc820041a88 sp=0xc820041a48
runtime.hashGrow(0xdd7fc0, 0xc8200d21e0)
/usr/local/go/src/runtime/hashmap.go:809 +0x82 fp=0xc820041ab8 sp=0xc820041a88
runtime.mapassign1(0xdd7fc0, 0xc8200d21e0, 0x1a8b780, 0x1a8b790)
/usr/local/go/src/runtime/hashmap.go:509 +0x5d2 fp=0xc820041b60 sp=0xc820041ab8
html.init()
/usr/local/go/src/html/entity.go:2154 +0xe8 fp=0xc820041bc8 sp=0xc820041b60
html/template.init()
/usr/local/go/src/html/template/url.go:105 +0x70 fp=0xc820041cc8 sp=0xc820041bc8
net/rpc.init()
/usr/local/go/src/net/rpc/server.go:712 +0x6f fp=0xc820041d30 sp=0xc820041cc8
github.com/docker/machine/libmachine/drivers/rpc.init()
/go/src/github.com/docker/machine/libmachine/drivers/rpc/server_driver.go:227 +0x4c fp=0xc820041d70 sp=0xc820041d30
github.com/docker/machine/libmachine.init()
/go/src/github.com/docker/machine/libmachine/libmachine.go:188 +0x63 fp=0xc820041d78 sp=0xc820041d70
github.com/docker/machine/commands.init()
/go/src/github.com/docker/machine/commands/version.go:40 +0x5f fp=0xc820041f48 sp=0xc820041d78
main.init()
/go/src/github.com/docker/machine/cmd/machine.go:215 +0x58 fp=0xc820041f50 sp=0xc820041f48
runtime.main()
/usr/local/go/src/runtime/proc.go:177 +0x27f fp=0xc820041fa0 sp=0xc820041f50
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc820041fa8 sp=0xc820041fa0
goroutine 5 [syscall]:
os/signal.signal_recv(0x0)
/usr/local/go/src/runtime/sigqueue.go:116 +0x132
os/signal.loop()
/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
Segmentation fault: 11To get this error I was running while true; do docker-machine status default; done and can reliably get this error after a short while strangely while the loop is running I'll also get other errors without a stack trace along the lines of:
dial tcp: lookup ?e??W?1: invalid domain name
Segmentation fault: 11
Segmentation fault: 11@buckett Segfault? Smells like cgo. Did you install with Homebrew? Can you retry with the pre-compiled binary from https://github.com/docker/machine/releases?
buckett
commented
7 years ago Precompiled binary https://github.com/docker/machine/releases
$ shasum -a 256 /usr/local/bin/docker-machine
28e07e42024d1f9b94e8d5953751556afe24cdfdc57d14e803506c3af47fe94b /usr/local/bin/docker-machinewhich matches the 0.8.1 release from there.
nathanleclaire
commented
7 years ago Cool, thanks. Mind trying the most recent version (0.9.0-rc2) to see if it fixes the problem? My tentative guess is that it's related to cgo code doing hostname lookups and that it might be resolved in slightly more recent Go versions. To see the panic with some preceding docker-machine --debug info would be useful as well.
buckett
commented
7 years ago Thanks, @nathanleclaire 0.9.0-rc2 works fine.
nathanleclaire
commented
7 years ago cool I'm going to go ahead and close then
Sometimes when running a docker-machine command it blows up, I've got machines (virtualbox, generic and azure):