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.

Sign up for GitHub

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

Jump to bottom

You can still start the graphd service if you fill in the wrong locap ip when expanding the service #2932

Closed
dbacyj opened this issue Sep 26, 2021 · 0 comments · Fixed by #3057
Closed

You can still start the graphd service if you fill in the wrong locap ip when expanding the service #2932

dbacyj opened this issue Sep 26, 2021 · 0 comments · Fixed by #3057
Assignees
@CPWstatic
Labels
type/bug Type: something is unexpected
Milestone
v2.6.0

Comments

@dbacyj
Copy link
Contributor

dbacyj commented Sep 26, 2021

image

image

When I expanding graphd and stroraged service on 192.168.8.194, I filled the local ip as 192.168.8.193 in the nebula-graphd.conf and can start the graphd service, so show hosts graph can not see 192.168.8.194, but why I can use console connect with 192.168.8.194? is this a bug?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CPWstatic CPWstatic

Labels
type/bug Type: something is unexpected
Projects
None yet
Milestone
v2.6.0
Development

Successfully merging a pull request may close this issue.

Fixed an issue where the server still started with a wrong ip/host. CPWstatic/nebula
3 participants
@CPWstatic @dbacyj @Sophie-Xie