-
Notifications
You must be signed in to change notification settings - Fork 16
Network test utility #308
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
Network test utility #308
Conversation
It took almost the full 5 minutes to connect to all the dmsg servers. |
|
When attempting to use the dmsghttp-config (the default for dmsg utilities) there is an indication that the dmsg network is ready after a dmsg direct client attempts to establish a session to a dmsg server. Then, that session gets shut down or stops unexpecetedly, but the http client which is configured for the second dmsg client which attempts to reach the dmsg-discovery server over dmsg is still in use by the second dmsg client. So it just sits there giving i/o deadline reached errors This is approximately the same situation for skywire visors. There is an indication that the dmsg network is ready, but the visor is only using the dmsg direct client to bootstrap the connection to dmsg or basically to force interaction with the dmsg-discovery over dmsg (dmsghttp) Here is logging that demonstrates the situation I've attempted to describe: Unfortunately, it's really stuck in that loop. The dial utility is just supposed to start the dmsg client and then stop it, but it's getting stuck. It should time out or re-attempt via a different server, but even when more than 1 session is used / multiple servers are connected to, it still fails to retry via the other dmsg server or other session! |
|
Here, finally, is logging that clearly shows that the dmsg-discovery is not equally accessible via all dmsg servers. but it didn't work through another dmsg server |
|
add utility to test dial remote dmsg client