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

Error connection with sudph #846

Closed
ersonp opened this issue Jul 16, 2021 · 0 comments
Closed

Error connection with sudph #846

ersonp opened this issue Jul 16, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@ersonp
Copy link
Contributor

ersonp commented Jul 16, 2021

Describe the bug
The sudph transport creation errors while setting up transport between two visors with public ip's.

Environment information:

From:

  • OS: Linux
  • Platform: Linux 5.11.4-arch1-1 x86_64

To:

  • OS: Linux
  • Platform: Linux 5.4.0-72-generic x86_64

Steps to Reproduce
Steps to reproduce the behavior:

  1. Run two visors on two different machines with public IP's
  2. Set up a sudph transport from one to another
  3. See error

Actual behavior
The visor that is used to set up transport throws a nil pointer exception.
from.txt
The other visor gives an error
to.txt

Expected behavior
sudph transport should be established without error.

Additional context
Both the visors were hosted on Linode. Nil pointer exception is shown only on develop, and on master, there is no exception but the sudph transport is initilised in offline state with

[2021-07-16T11:04:00Z] ERROR [sudph]: Failed to resolve UDP address {"02e398f3da0ed1c930f7d295185759c98511c75e112596007e4481b1fe666552cf" "139.162.141.220"} error="address 139.162.141.220: missing port in address"

this error on the second visor.

Possible implementation
Hints to fix the bug.

@ersonp ersonp added the bug Something isn't working label Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants