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 error message cryptic. #555

Open
wallclockbuilder opened this issue May 23, 2016 · 2 comments
Open

Zeus error message cryptic. #555

wallclockbuilder opened this issue May 23, 2016 · 2 comments

Comments

@wallclockbuilder
Copy link

Zeus wouldn't start.
It wouldn't tell me why exactly.
I tried rails s and got the cause right away.
Improve zeus to have the same level of error accuracy as rails.
screen shot 2016-05-23 at 9 30 58 am

@kgrz
Copy link
Contributor

kgrz commented May 23, 2016

I think the reason you don't see an error immediately is that zeus simply starts a daemon. It doesn't run any command after running the reloader process. In the case of rails s, you are actually calling the "start the server" command. The equivalent procedure in case of zeus would be a 2-step process: "start zeus; run zeus server". You would've seen the same error if you had run zeus server or any other command.

So the error messages in this case are accurate, just that they are not explicit with zeus daemon process.

@wallclockbuilder
Copy link
Author

Thanks for your response. I appreciate the effort you put in to explain.

I run zeus server and got notified that zeus wasn't running. So I run zeus start and got the cryptic error message. Perhaps we signal: killed.
How can we make zeus give a much more helpful error message like rails did?

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

2 participants