-
Notifications
You must be signed in to change notification settings - Fork 102
ManagedConnections::OnConnectionLostSlot() crash while running Vaults #6
Comments
Here is a stack trace for this issue:
|
Case: When node3 bootstraps off node2, GetAvailableEndpoint at node2 doesn't pick up the existing connection and returns a new transport's endpoint. This is resulting in some mismatch & resulting in the assertion on OnConnectionLostSlot(). Routing tests FUNC_ProcessSendDirectEndpoint & FUNC_ProcessSendRecursiveSendOn are intermittently failing due to this issue.
|
The routing tests that Prakash mentioned (ProcessSendDirectEndpoint and ProcessSendRecursiveSendOn) still fail frequently because GetAvailableEndpoint returns rudp::kBootstrapConnectionAlreadyExists. |
In running the extended, proportioned routing tests (where the network is bigger than the routing table capacity), I have seen the following assertion fail; I think it corresponds to the assertion originally mentioned in this issue.
|
W 139706536806144 10:44:12.633625 rudp/connection.cc:229] Failed to connect from 176.58.120.133:57162 / 176.58.120.133:57162 to 192.168.0.26:43752 - timed out.
pd-vault: /home/maidsafe/super/MaidSafe/src/rudp/src/maidsafe/rudp/managed_connections.cc:671: void maidsafe::rudp::ManagedConnections::OnConnectionLostSlot(const maidsafe::NodeId&, maidsafe::rudp::{anonymous}::TransportPtr, bool): Assertion `false' failed.
The text was updated successfully, but these errors were encountered: