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

Expose ”Address already in use“ when start the service #2127

Closed
jude-zhu opened this issue May 14, 2020 · 2 comments
Closed

Expose ”Address already in use“ when start the service #2127

jude-zhu opened this issue May 14, 2020 · 2 comments

Comments

@jude-zhu
Copy link
Contributor

when start the service using "nebula.service", it says done. However, when I check the log, "Address already in use"

@dutor
Copy link
Contributor

dutor commented May 20, 2020

I don't think it's necessary to make nebula.service start do what nebula.service status does. The daemons work in a kind of async way, that says launch a process, do some simple sanity checks, fork a child process then exit(sucessfuly). The actual service runs in the child process.

So, the nebula.service script cannot tell if the child process was properly launched.

FYI. You could refer to the way how systemctl works.

@jude-zhu jude-zhu added v2.0 and removed v2.0 labels May 26, 2020
@jude-zhu
Copy link
Contributor Author

relate to #1304

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