This repository has been archived by the owner on Jan 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 102
Failure to send to a routing node on another machine after limited (known) attempts #93
Comments
Can you attach relevant logs of RUDP/Routing please? |
ghost
assigned mmoadeli
Dec 11, 2012
Routing log
|
RUDP log
|
both routing and rudp logs above are only parts of logs, close to failure point (Sending end logs). |
Part of routing log at receiving side
|
All Rudp log at receiving end
|
Migrated to maidsafe-archive/MaidSafe-RUDP#8 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to reproduce:
It seems that all the time the 48th message fails to reach to destination, and after that all messages sent to the same destination also fail to reach.
Changing the datasize seems to be related to the first failing message, however, it does not look like a linear relationship.
The same thing happens on Linux on iteration #67 when source is my system and on iteration #260 when the source is high spec 192.168.0.109 system.
Seems that sending buffer at source gets full.
The text was updated successfully, but these errors were encountered: