You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Run two visors on two different machines with public IP's
Set up a sudph transport from one to another
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.
The text was updated successfully, but these errors were encountered:
Describe the bug
The
sudph
transport creation errors while setting up transport between two visors with public ip's.Environment information:
From:
To:
Steps to Reproduce
Steps to reproduce the behavior:
sudph
transport from one to anotherActual 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 withthis error on the second visor.
Possible implementation
Hints to fix the bug.
The text was updated successfully, but these errors were encountered: