-
Notifications
You must be signed in to change notification settings - Fork 989
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
🐛 BUG: Unable to reconnect after server crash #1125
Comments
Also worth noting that this issue doesn't occur after a normal reboot. |
On the surface this looks like a nebula IP reuse issue but there's so much redacted that it's hard to understand exactly what is happening.
Both Host A and Host B appear to be attempting to initiate a tunnel with the other but neither logs show a matching handshake despite Host A responding. This means we should see logs on Host A responding to handshakes initiated by Host B. To help can you do the following:
|
Great, I've sent you an email. And there aren't multiple processes running. It's controlled by systemd. |
I was wondering if you found anything noteworthy in the logs? This isn't a big problem but I did want to bring this problem to your attention if it was worth looking at. |
What version of
nebula
are you using? (nebula -version
)1.8.2
What operating system are you using?
Linux
Describe the Bug
One of my servers has been unstable and will sometimes become unresponsive, requiring a hard reset (this is host A,
172.0.3.109
). When it comes back up, it's unable to establish a connection to my node that is a nginx reverse proxy (this is host B,172.0.2.120
). If I manually restart the Nebula service on host A, it fixes the issue and host A can connect to host B.Logs from affected hosts
Lighthouse
Host A
This pattern repeats.
Host B
This pattern repeats
Config files from affected hosts
Host A
Host B
Lighthouse
The text was updated successfully, but these errors were encountered: