-
Notifications
You must be signed in to change notification settings - Fork 45
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
Behavior on connection loss #1789
Comments
a transport from machine 1 was established to machine 2
The machine 1 was left alone, and machine 2 was shut down, gracefully. Upon returning to machine 1, the transport which had been established still existed (see above) However, the entry for that transport did not exist in TPD and had been removed, apparently at the time the other machine was shut down. No indication of any error or change in the visor debug logging for machine 1 was observed
|
Something we rarely look at is what happens on internet connection loss.
A visor with a running proxy server and the following transports was used
The network was disconnected temporarily via NetworkManager Applet on linux in order to observe the visor debug logging, and then the network was reconnected
The following visor debug logging was produced:
Observations
All transports were removed from the visor immediately on disconnect. (Is this desired behavior?)
Further Examination
Attempt to re-establish the same transport type to the same visor succeeded
Deleting the transport also worked
Deleting transports that TPD says this visor has but which this visor does not have does not work
Further observation of the behavior of remote visors when transports fail is needed
The text was updated successfully, but these errors were encountered: