User run network based on test 12b binaries

Community
464

My vaults are still running fine, I can still get INFO etc from my logs I noticed today. Last week they just weren’t giving much info, almost only timeouts…

465

of course sir,

pretty bulk standard:

{
“hard_coded_contacts”: [
“86.164.140.138:5483”,
“35.167.139.205:5483”,
“52.65.136.52:5483”,
“138.197.235.128:5483”,
“73.255.195.141:5483”,
“108.61.165.170:5483”,
“185.16.37.149:5483”,
“78.46.181.243:5483”,
“31.151.192.2:5483”,
“52.59.206.28:5483”],

“bootstrap_whitelisted_ips”: ,
“tcp_acceptor_port”: 5483,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”:“community_network_feb_2017”
}

rup

3 Likes
467

Good idea -trying again now with the config from @rupert <—thanks
INFO 00:33:36.726438754 [routing::states::node node.rs:2316] Node(29ccc0..()) 1/8 resource proof response(s) complete, 39% of data sent. 350/410 seconds remaining.

468

nope…

ubuntu@ip-172-31-27-185:/maidsafe/safe_vault-v0.13.0-linux-x64$ sudo ./safe_vault 
INFO 00:32:29.806541810 [safe_vault safe_vault.rs:95] 

Running safe_vault v0.13.0
==========================
INFO 00:32:36.246977740 [routing::states::node node.rs:1240] Node(df3537..()) Requesting a relocated name from the network. This can take a while.
INFO 00:32:36.726184184 [routing::states::node node.rs:1890] Node(29ccc0..()) Received relocated name. Establishing connections to 8 peers.
INFO 00:32:37.106342244 [routing::states::node node.rs:1031] Node(29ccc0..()) Starting approval process to test this node's resources. This will take at least 300 seconds.
INFO 00:33:06.726288189 [routing::states::node node.rs:2316] Node(29ccc0..()) 0/8 resource proof response(s) complete, 19% of data sent. 380/410 seconds remaining.
INFO 00:33:36.726438754 [routing::states::node node.rs:2316] Node(29ccc0..()) 1/8 resource proof response(s) complete, 39% of data sent. 350/410 seconds remaining.
INFO 00:33:37.696091047 [routing::states::node node.rs:2769] Node(29ccc0..()) Dropped 6f21d3.. from the routing table.
INFO 00:34:06.726572204 [routing::states::node node.rs:2316] Node(29ccc0..()) 1/8 resource proof response(s) complete, 54% of data sent. 320/410 seconds remaining.
INFO 00:34:36.726749287 [routing::states::node node.rs:2316] Node(29ccc0..()) 1/8 resource proof response(s) complete, 68% of data sent. 290/410 seconds remaining.
INFO 00:35:06.726949093 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 75% of data sent. 260/410 seconds remaining.
INFO 00:35:36.727152595 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 75% of data sent. 230/410 seconds remaining.
INFO 00:36:06.727364637 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 76% of data sent. 200/410 seconds remaining.
INFO 00:36:36.727587424 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 76% of data sent. 170/410 seconds remaining.
INFO 00:37:06.727772020 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 76% of data sent. 140/410 seconds remaining.
INFO 00:37:36.727947044 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 76% of data sent. 110/410 seconds remaining.
INFO 00:38:06.728138581 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 76% of data sent. 80/410 seconds remaining.
INFO 00:38:36.728320508 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 76% of data sent. 50/410 seconds remaining.
INFO 00:39:06.728499077 [routing::states::node node.rs:2316] Node(29ccc0..()) 6/8 resource proof response(s) complete, 76% of data sent. 20/410 seconds remaining.
INFO 00:39:26.726318828 [routing::states::node node.rs:2350] Node(29ccc0..()) Failed to get approval from the network. 6/8 resource proof response(s) complete, 76% of data sent. Terminating node.
ubuntu@ip-172-31-27-185:/maidsafe/safe_vault-v0.13.0-linux-x64$

This is somewhat similar to what I had been seeing a few days ago - a node would get dropped from the routing table whilst the verification process was ongoing and it would time out with n-1/n resource proof complete.
Except in this case it is n-2/n resource proof complete.

I’ll keep trying :slight_smile:

469

Looking at this, I would say that your node is not powerful enough to complete the resource proof in time.

Otherwise your log would contain lines like All … resource proof responses fully sent.

1 Like
470

But notice that 75% is done in 140 Seg. The same thing happened to me. Most times the resource proof advanced very fast and suddenly stopped. But even if I finished the resource proof the Vault closed with this message:

All 13 resource proof responses fully sent, but timed out waiting for approval from the network. This could be due to the target section experiencing churn. Terminating node.

I think this commit are the fixes for this error…

1 Like
471

In this case the result is different: you completed the resource proof, but the network failed to acknowledge this in time.

But there I understand that your own resource proof completion is also dependent on the network. So, I was probably wrong about the node being not powerful enough and there are probably some conditions depending on the state of the network.

3 Likes