-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Intermittent "context deadline exceeded" when no deadline set #138
Comments
@parkan roughly how long are the timeouts? Having an approximate number would help narrow this down significantly |
The timeouts appear to be quite short in the occasions I observed -- maybe a couple seconds? A little more detail about the specifics in what I have observed:
|
Another data point, this time with an actual timeout measurement.
All this is happening with the nodes involved (icmp) pinging happily and no unusual network conditions. |
Also verified that I can connect to the node with telnet and get the go-multistream header back. |
I also restarted the node I am trying to connect, and I still can't connect. |
Digging further, seems there is a legitimate networking problem with the node in this case (ssh yes, but no pings or telnet to the multistream port from my network location). |
I think we can ascribe my problems today at legitimate networking issues. |
We are seeing intermittent
dial attempt failed: context deadline exceeded
with no deadline set. This is with local/nearby nodes and no suspicious network weather.The error happens here: https://github.com/mediachain/concat/blob/3a07b2cb8d7104b570fd5bcccb5c8f48f429cc38/mcnode/proto.go#L359
The context is a plain
Context
.@vyzo can provide more details -- happens every few restarts. Any clue where to look?
The text was updated successfully, but these errors were encountered: