I’ve got it also with one vault last week. Just restarted the vault and it did the process again and worked out correctly. Somewhat strange for me too. 
I’m seeing it several times now.
We need to remember that this IS buggy code and 12_b got stopped for a reason.
Dunno how many nodes we have on the community network now (30-35?) but possibly we are hitting a limit that was uncovered last week.
Or I could be talking crap and guessing wildly? Its never held back my IT career before…
2 Likes
I got the same a couple of hours ago:
INFO 20:39:06.601429600 [routing::states::node node.rs:2350] Node(6997d9…()) Failed to get approval from the network. All 16 resource proof responses fully sent. Terminating node.
DEBUG 20:39:06.601429600 [routing::state_machine state_machine.rs:267] State::Node(6997d9…()) Terminating state machine
Previous messages mentioned connection attempts timing out, e.g.
DEBUG 20:33:16.847678100 [crust::main::connect mod.rs:217] Connect to peer PeerId(6f4654ca..) timed out
1 Like
Here’s a new one:
INFO 23:01:22.372388100 [routing::states::node node.rs:2316] Node(84b8c5..()) 14/16 resource proof response(s) complete, 102% of data sent. 20/410 seconds remaining.
…
Failed to get approval from the network. 14/16 resource proof response(s) complete, 102% of data sent. Terminating node.
My node’s given 102% and still been terminated. Life is so unfair!
2 Likes
We feel your pain. Have a manly hug.
1 Like
Looks like shit happened
INFO 23:12:00.907273273 [routing::states::node node.rs:2316] Node(7f47ac..()) 14/15 resource proof response(s) complete, 96% of data sent. 20/410 seconds remaining.
INFO 23:12:13.941679040 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 6248c8.. from the routing table.
INFO 23:12:13.952174022 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 04117f.. from the routing table.
INFO 23:12:13.953737187 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 712694.. from the routing table.
INFO 23:12:13.966090720 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 1bd1a4.. from the routing table.
INFO 23:12:13.980410340 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 575945.. from the routing table.
INFO 23:12:13.989321252 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 6a4d7e.. from the routing table.
INFO 23:12:14.005389804 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 3f3e16.. from the routing table.
INFO 23:12:14.032630137 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 45efef.. from the routing table.
INFO 23:12:14.070019678 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 57d387.. from the routing table.
INFO 23:12:14.121612375 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 01c346.. from the routing table.
INFO 23:12:14.125106522 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 139ca4.. from the routing table.
INFO 23:12:14.135429739 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 188d01.. from the routing table.
INFO 23:12:14.138735671 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 1f0afb.. from the routing table.
INFO 23:12:14.154157223 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 08f4a2.. from the routing table.
INFO 23:12:14.190734634 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 6f21d3.. from the routing table.
INFO 23:12:14.761153495 [routing::states::node node.rs:2769] Node(7f47ac..()) Dropped 498bae.. from the routing table.
WARN 23:12:14.761772863 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 23:12:20.977716457 [routing::states::node node.rs:1240] Node(ff4d87..()) Requesting a relocated name from the network. This can take a while.
INFO 23:12:21.919290796 [routing::states::node node.rs:1890] Node(cb7241..()) Received relocated name. Establishing connections to 16 peers.
INFO 23:12:21.952189045 [routing::states::common::base base.rs:73] Node(cb7241..()) Connection to PeerId(59c5ada6..) failed: PeerNotFound(PeerId(59c5ada6..))
INFO 23:12:21.952628113 [routing::states::common::base base.rs:73] Node(cb7241..()) Connection to PeerId(59c5ada6..) failed: PeerNotFound(PeerId(59c5ada6..))
INFO 23:12:21.953071485 [routing::states::common::base base.rs:73] Node(cb7241..()) Connection to PeerId(59c5ada6..) failed: PeerNotFound(PeerId(59c5ada6..))
INFO 23:12:21.953470788 [routing::states::common::base base.rs:73] Node(cb7241..()) Connection to PeerId(59c5ada6..) failed: PeerNotFound(PeerId(59c5ada6..))
INFO 23:12:21.953662409 [routing::states::node node.rs:2769] Node(cb7241..()) Dropped 9a50e6.. from the routing table.
WARN 23:12:21.954123909 [safe_vault::vault vault.rs:181] Restarting Vault
INFO 23:12:27.969353225 [routing::states::node node.rs:1240] Node(4ad1f4..()) Requesting a relocated name from the network. This can take a while.
Did a complete section drop out?
1 Like
Awww thanks man. Needed that.
The end is nigh. We’re doomed…
I’ll leave them on and watch tomorrow what’s left.
Now 
I’m wanting to try running a user vault. Is 12b dead now? Should I wait for 12c?
No you can use the vault with the community settings, like in this thread
I think this test is over. Impossible to join, sometimes stuck in the resource proof or, if pass, don’t join.
And stranger behaviour…
It’s not over while data is accessible… something of it is still working well - safe://hello/ is up and user account for that is still accessible too. Surely the resource proof is relative to your node? Perhaps your bandwidth is fluxing relative to other activity at host??
1 Like
All my vaults are in a loop I think… Same time out as this night and still communicating 100-200 Kbits/s
The Launcher connect and even can download the files uploaded Monday night, but the problem is join as Vault.
I try more than 20 times and my connection is very fast, so don’t think is the problem. Besides, the vault send strangers messages of dropped nodes.
This morning the Vault was running but the messages was different that other days. Unfortunately the Vault reset the Logs.
Maybe a new crust config can help, but the network behaviour is different that other days.
2 Likes
hmmmm - my node is still up and running
INFO 11:14:07.300819145 [routing::states::node node.rs:278] | Node(04117f..(0)) PeerId(2ca70096..) - Routing Table size: 27 |
INFO 11:14:07.300878027 [routing::states::node node.rs:279] ----------------------------------------------------------------
INFO 11:14:23.739927295 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 2, cumulative: 28
INFO 11:14:24.519108686 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 3, cumulative: 29
INFO 11:14:24.525775353 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 4, cumulative: 30
INFO 11:14:31.012573502 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 5, cumulative: 31
INFO 11:14:31.080412784 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 4, cumulative: 31
INFO 11:14:31.087095233 [safe_vault::personas::data_manager data_manager.rs:415] This vault has received 2502 Client Get requests. Chunks stored: Immutable: 401, Structured: 94, Appendable: 1. Total stored: 314482063 bytes.
INFO 11:14:31.438737178 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 5, cumulative: 32
INFO 11:14:31.820015484 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 4, cumulative: 32
INFO 11:14:31.963315476 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 5, cumulative: 33
INFO 11:14:32.451608289 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 4, cumulative: 33
INFO 11:14:48.339602690 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 5, cumulative: 34
INFO 11:14:53.919692668 [routing::states::node node.rs:2112] Node(04117f..(0)) Update on RoutingTableResponse completed. Prefixes: {Prefix(0), Prefix(1)}
INFO 11:14:54.933573343 [routing::states::node node.rs:242] Node(04117f..(0)) - Connected clients: 4, cumulative: 34
INFO 11:15:56.825270104 [routing::states::node node.rs:2112] Node(04117f..(0)) Update on RoutingTableResponse completed. Prefixes: {Prefix(0), Prefix(1)}
INFO 11:17:44.697838866 [routing::states::node node.rs:2112] Node(04117f..(0)) Update on RoutingTableResponse completed. Prefixes: {Prefix(0), Prefix(1)}
INFO 11:20:24.609598714 [routing::states::node node.rs:1952] Node(04117f..(0)) Expecting candidate 3c72c6.. via Client { client_name: a3de60.., proxy_node_name: 04117f.., peer_id: PeerId(eb596648..) }.
INFO 11:20:24.812612186 [routing::states::node node.rs:1988] Node(04117f..(0)) Our section with Prefix(0) accepted 3c72c6.. as a candidate.
INFO 11:20:25.676634817 [routing::states::node node.rs:1363] Node(04117f..(0)) Sending resource proof challenge to candidate 3c72c6..
INFO 11:20:25.871853541 [routing::states::node node.rs:1134] Node(04117f..(0)) Candidate 3c72c6.. passed our challenge in 1 seconds. Sending approval to our section with Prefix(0).
INFO 11:20:25.872435371 [routing::states::node node.rs:2402] Node(04117f..(0)) Resource proof duration has finished. Voting to approve candidate 3c72c6...
INFO 11:22:05.118262638 [routing::states::node node.rs:2112] Node(04117f..(0)) Update on RoutingTableResponse completed. Prefixes: {Prefix(0), Prefix(1)}
routing table at 27 - so still pretty large our network
2 Likes
same here, looking good as far as I can see. It took me quite some attemps to be able to join last time ( 2 days ago ), though.
I see a lot of :
Candidate xxxxxx.. has not passed our resource proof challenge in time. Not sending approval vote to our section with Prefix(0)
3 Likes
are to be expected?..
From the little I know, joining might be more difficult at times where the network nodes are busy and haven’t time to verify newcomers. Suggested I think before - in the OP to 12b, that might need to keep trying.
1 Like
hmmm - yeah - this seems to be the problem of our current testnet - at some point the joining procedure seems to escalate slightly Oo
but 12c will be on the horizon soon i think 
and the current nodes might be able to keep it alive until that release 
2 Likes
Testing continuously but none.
My crust config is the following. Maybe trying different contacts can help.
{
“hard_coded_contacts”: [
“35.167.139.205:5483”,
“108.61.165.170:5483”,
“52.65.136.52:5483”,
“206.116.50.52:5483”,
“99.199.170.208:5483”,
“31.151.192.2:5483”,
“86.184.57.178:5483”,
“13.80.119.160:5483”,
“85.93.19.51:5483”,
“35.157.162.33:5483”,
“185.16.37.149:5483”,
“35.156.220.253:5483”
],
“bootstrap_whitelisted_ips”: ,
“tcp_acceptor_port”: 5483,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_feb_2017”
}
1 Like