Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zeus crash on start in ruby 2.5.0 #651

Open
AndrzejJantos opened this issue Jan 14, 2018 · 7 comments
Open

zeus crash on start in ruby 2.5.0 #651

AndrzejJantos opened this issue Jan 14, 2018 · 7 comments

Comments

@AndrzejJantos
Copy link

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

Available Commands: [waiting] [crashed] [ready]
zeus console (alias: c)
zeus server (alias: s)
zeus generate (alias: g)
zeus destroy (alias: d)
zeus dbconsole
zeus rake
zeus runner (alias: r)
zeus test (alias: rspec, testrb)
exit status 1```

Zeus crash on start in ruby 2.5.0.
@ragesoss
Copy link

Confirmed. My app runs zeus without error on Ruby 2.3.1, but crashes like this on Ruby 2.5.0.

@mcordell
Copy link

Also confirmed. Running with logging shows the below:

2018/01/19 12:23:29.429638 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:149] test_environment/(no PID) entering state SUnbooted
2018/01/19 12:23:29.429666 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:149] development_environment/(no PID) entering state SUnbooted
2018/01/19 12:23:29.429663 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:149] prerake/(no PID) entering state SUnbooted
2018/01/19 12:23:29.429687 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:149] test_helper/(no PID) entering state SUnbooted
2018/01/19 12:23:29.429707 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:149] boot/(no PID) entering state SUnbooted
2018/01/19 12:23:29.429717 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:149] default_bundle/(no PID) entering state SUnbooted
2018/01/19 12:23:29.430329 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:391] boot/(no PID) running the root command now
2018/01/19 12:23:29.527776 [/Users/phil/Source/go/src/github.com/burke/zeus/go/processtree/slavenode.go:402] boot/(no PID) root process exited with an error before it could boot: exit status 1; output was: /Users/michael/.rubies/ruby-2.5.0/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- ubygems (LoadError)
        from /Users/michael/.rubies/ruby-2.5.0/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'

@AndrzejAngryNerds
Copy link

Any update on this?

@yld
Copy link

yld commented Jan 30, 2018

Editing zeus.json according to #237 (comment) resolve the problem. Credits to @skopu

You can also find the source of any other problem occuring using the given command:
ruby -r rubygems -r./custom_plan -eZeus.go

@FelixFortis
Copy link

gem update --system worked for me

@sankalpk
Copy link

Running the following in the terminal worked for me:

export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

@arich55
Copy link

arich55 commented Apr 4, 2018

If anyone is still having issues with this, follow the advise from the comment here: #237 (comment) to properly identify the issue.

zeus --log ZEUS.LOG start then cat ZEUS.LOG

In one case, after running zeus init and updating the command argument in ./custom_plan.rb
from: "command": "ruby -rubygems -r./custom_plan -eZeus.go",
to: "command": "ruby -r rubygems -r ./custom_plan -e Zeus.go",

resolved this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants