zeus: Go-related panic all of a sudden

I had a zeus instance humming along flawlessly for over 6 hours of development time (love it, by the way!) and then all of a sudden for seemingly no reason it started throwing this error:

panic: open /dev/ptmx: device not configured

goroutine 1 [running]:
github.com/burke/zeus/go/zeusclient.doRun(0x1, 0x1000000000, 0x23ff, 0x7fff5fbff901)
    /Users/burke/go/src/github.com/burke/zeus/go/zeusclient/zeusclient.go:47 +0x221
github.com/burke/zeus/go/zeusclient.Run(0x7fff5fbff901, 0xf800000001)
    /Users/burke/go/src/github.com/burke/zeus/go/zeusclient/zeusclient.go:25 +0x23
main.main()
    /Users/burke/go/src/github.com/burke/zeus/go/cmd/zeus/zeus.go:46 +0x3ff

goroutine 2 [syscall]:
created by runtime.main
    /private/tmp/bindist454984655/go/src/pkg/runtime/proc.c:221

goroutine 3 [syscall]:
os/signal.loop()
    /usr/local/go/src/pkg/os/signal/signal_unix.go:20 +0x1c
created by os/signal.init·1
    /usr/local/go/src/pkg/os/signal/signal_unix.go:26 +0x2f

Happens on every zeus <command> now. I don’t know what caused it; I’m fairly certain a reboot will fix it, but I don’t want to reboot just yet.

OSX, Zeus 0.11.0

About this issue

Original URL
State: closed
Created 12 years ago
Comments: 17 (3 by maintainers)

Most upvoted comments

This happened due to a syntax error in my code. Maybe that will help someone reading this

nulty on Sep 24, 2014

I experienced the same. After a while I figured out that I forgot to “bundle install” the application. So, to recap:

add new gem to Gemfile
zeus start -> panic: runtime error: invalid memory address or nil pointer dereference in goroutine, permanently

Problem solved after “bundle install”

pic on Dec 11, 2012