zeus: Crash on 'zeus start'

uname -a

Darwin MyMacBookPro.local 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64
ruby -v

ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-darwin13.0.0]
\zeus start

Starting Zeus server
[ready] [crashed] [running] [connecting] [waiting]
[ready] [crashed] [running] [connecting] [waiting]
boot
└── default_bundle
    ├── development_environment
    │   └── prerake
    └── test_environment
        ├── test_helper
        └── cucumber_environment

Available Commands: [waiting] [crashed] [ready]
zeus rake [run to see backtrace]
zeus dbconsole [run to see backtrace]
zeus server (alias: s) [run to see backtrace]
zeus runner (alias: r) [run to see backtrace]
zeus console (alias: c) [run to see backtrace]
zeus destroy (alias: d) [run to see backtrace]
zeus generate (alias: g) [run to see backtrace]
zeus test (alias: rspec, testrb) [run to see backtrace]
zeus cucumber [run to see backtrace]

About this issue

  • Original URL
  • State: open
  • Created 10 years ago
  • Comments: 23

Most upvoted comments

This might help with debugging: zeus --log ZEUS.LOG start cat ZEUS.LOG

Uninstalling the current version and running,

$ gem install zeus -v 0.15.4

solved it for me.

Had the same problem on:

  • Darwin MacBook-Pro-van-Wouter.local 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64
  • ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-darwin17]

Crash:

Available Commands: [waiting] [crashed] [ready]
zeus generate (alias: g) [run to see backtrace]
zeus destroy (alias: d) [run to see backtrace]
zeus dbconsole [run to see backtrace]
zeus lv [run to see backtrace]
zeus rake [run to see backtrace]
zeus runner (alias: r) [run to see backtrace]
zeus console (alias: c) [run to see backtrace]
zeus server (alias: s) [run to see backtrace]
zeus cucumber [run to see backtrace]
zeus test (alias: rspec, testrb) [run to see backtrace]
slavenode.go:226: [default_bundle] read unix ->: EOF

Log did not mention anything special.

Solution (but did not investigate potential risks):

$> export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

Our team is using Zeus version 0.13.3.rc2. The reason i was getting exit status 1 is I was missing a version of json (1.8.2) in my global gem set. So in my home directory, running gem install json -v 1.8.2 brought my global gemset for json to json (1.8.3, 1.8.2, 1.7.7). That fixed the issue for me somehow…

Have you tried on ruby 1.9.3? BTW zeus is free software, hence it is not guarantee the developers might get on the bug and fix it right away. If it is so important to you, you should actually contribute to it…