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]
This might help with debugging:
zeus --log ZEUS.LOG start
cat ZEUS.LOG
Uninstalling the current version and running,
solved it for me.
Had the same problem on:
Crash:
Log did not mention anything special.
Solution (but did not investigate potential risks):
Our team is using
Zeus version 0.13.3.rc2
. The reason i was gettingexit status 1
is I was missing a version of json (1.8.2) in my global gem set. So in my home directory, runninggem install json -v 1.8.2
brought my global gemset for json tojson (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…