User run network based on test 12b binaries


#402

Oo we might get a more stable network if too many people are going down that road Oo …:confused:

@polpolrene how did you resolve:

?


#403

What system do you use to compile?


#404

ubuntu 16.04 - and simply cloned the master branch


#405

I did it on win10/64 and didn’t had that problem some hours ago. No clue what this is about, quite new to compiling stuff.


#406

@polpolrene René, this is a tiny step away from creating an app. Be great to see you joining @jm5 @dask @beekeeper and others in their beginners coding club:

Lots of people able to help here! :slight_smile:


#407

okay - i’ll look into that later :slight_smile: probably just me being a little bit stupid or a temporary problem Oo


#408

Ha, great Mark. Can confirm I’m on codeacademy already, trouble is not being able to focus long enough on a screen for health reasons. Most of the time it’s trouble within 20 mins. But will try in a way that fits after all. And will have an app on SAFE for sure one day :+1:.


#409

I’m having comparable difficulties. I too registered at codeacademy but didn’t really work. Will have to figure out a way sooner or later…


#410

chugging along very nicely…

INFO 07:45:27.159423086 [routing::states::node node.rs:277] ----------------------------------------------------------------
INFO 07:45:27.160558799 [routing::states::node node.rs:278] | Node(8a5cb9…(1)) PeerId(ecca0561…) - Routing Table size: 27 |
INFO 07:45:27.161092282 [routing::states::node node.rs:279] ----------------------------------------------------------------
INFO 10:11:57.726699804 [safe_vault::personas::data_manager data_manager.rs:862] This vault has received 8710 Client Get requests. Chunks stored: Immutable: 403, Structured: 88, Appendable: 0. Total stored: 505574295 bytes.

rup


#411

I run into the exact same problem under Windows. Couldn’t figure out what the problem is so far. Let me know if you make progress on this.

EDIT: @riddim I finally solved the stated problem by editing the cargo.toml file. Try changing
routing = { git = “https://github.com/maidsafe/routing” }
to
routing = “~0.28.1”

Also had to change the rust toolchain from MSVC to GNU:
rustup install stable-gnu
rustup default stable-x86_64-pc-windows-gnu


#412

Does anybody know a good tool to test bandwidth from bash? Outgoing traffic :traffic_light:


#413

speedtest-cli to test bandwidth (ping, download and upload).
After some googling I found this article that compares 18 linux cmdline tools to monitor network bandwidth.


#414

Yes, this is it. I had trouble for some time while trying on MSVC. Ik removed it from my system. Viv was a great help.


#416

Fixed my issue :smiley:

Thanks @rand_om !! This is what worked for me:

{
“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”,
“104.207.131.126:5483”
],
“bootstrap_whitelisted_ips”: [],
“tcp_acceptor_port”: 5483,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_feb_2017”
}


#417

My vault just crashed and can’t be restarted. All logs are gone…?


#418

As an experiment I closed my vault then tried to connect again:

INFO 23:49:11.213488800 [safe_vault safe_vault.rs:95] 

Running safe_vault v0.13.0
==========================
DEBUG 23:49:11.215001500 [crust::main::service service.rs:462] Network name: Some("community_network_feb_2017")
TRACE 23:49:16.416736800 [routing::states::bootstrapping bootstrapping.rs:121] Bootstrapping(fa696d..) Listener started on port 5483.
ERROR 23:49:17.660035100 [crust::main::bootstrap mod.rs:184] Failed to Bootstrap: (FailedExternalReachability) Bootstrapee node could not establish connection to us.
INFO 23:49:17.660529000 [routing::states::bootstrapping bootstrapping.rs:201] Bootstrapping(fa696d..) Failed to bootstrap. Terminating.
DEBUG 23:49:17.660529000 [routing::state_machine state_machine.rs:267] State::Bootstrapping(fa696d..) Terminating state machine

EDIT: scratch that, my VPN was on. Seems to be connecting again fine now


#419

thanks - with changing the dependency the error message changed too Oo … but nonetheless i’m too stupid to compile the code via “cargo build” Oo

i mean … routing is at 0.28.1 at github … so … (i wonder how he can find it on github when it works - since i don’t see the location specified somewhere Oo )


#420

I had the same error. Turned out I had installed two separate versions of Rust and the PATH variable pointed to the older version which is incompatible for compiling the vault.
Try typing rustc --version
That should give you “rustc 1.15.1”. If not, uninstall all rust instances and reinstall using rustup:
https://www.rustup.rs/


#421

Failed to get approval from the network. All 15 resource proof responses fully sent. Terminating node.

I havent seen this error before - or did just not read the thread thoroughly? - any hints welcome

ubuntu@ip-172-31-19-24:/maidsafe/safe_vault-v0.13.0-linux-x64$ sudo ./safe_vault
INFO 21:34:12.687909176 [safe_vault safe_vault.rs:95]

Running safe_vault v0.13.0
==========================
INFO 21:34:19.111191443 [routing::states::node node.rs:1240] Node(fc2b90..()) Requesting a relocated name from the network. This can take a while.
INFO 21:34:19.856792677 [routing::states::node node.rs:1890] Node(b66a45..()) Received relocated name. Establishing connections to 16 peers.
INFO 21:34:19.877514649 [routing::states::node node.rs:1031] Node(b66a45..()) Starting approval process to test this node's resources. This will take at least 300 seconds.
INFO 21:34:49.856897789 [routing::states::node node.rs:2316] Node(b66a45..()) 5/15 resource proof response(s) complete, 61% of data sent. 380/410 seconds remaining.
INFO 21:35:19.857080305 [routing::states::node node.rs:2316] Node(b66a45..()) 7/15 resource proof response(s) complete, 81% of data sent. 350/410 seconds remaining.
INFO 21:35:49.857232809 [routing::states::node node.rs:2316] Node(b66a45..()) 12/15 resource proof response(s) complete, 91% of data sent. 320/410 seconds remaining.
INFO 21:36:19.857387703 [routing::states::node node.rs:2316] Node(b66a45..()) 12/15 resource proof response(s) complete, 96% of data sent. 290/410 seconds remaining.
INFO 21:36:49.857558719 [routing::states::node node.rs:2316] Node(b66a45..()) 13/15 resource proof response(s) complete, 98% of data sent. 260/410 seconds remaining.
INFO 21:37:19.857714061 [routing::states::node node.rs:2316] Node(b66a45..()) 13/15 resource proof response(s) complete, 101% of data sent. 230/410 seconds remaining.
INFO 21:37:49.857888109 [routing::states::node node.rs:2316] Node(b66a45..()) 14/15 resource proof response(s) complete, 98% of data sent. 200/410 seconds remaining.
INFO 21:38:19.858030496 [routing::states::node node.rs:2316] Node(b66a45..()) 14/15 resource proof response(s) complete, 99% of data sent. 170/410 seconds remaining.
INFO 21:38:49.858221630 [routing::states::node node.rs:2316] Node(b66a45..()) All 15 resource proof responses fully sent. 140/410 seconds remaining.
INFO 21:39:19.858378322 [routing::states::node node.rs:2316] Node(b66a45..()) All 15 resource proof responses fully sent. 110/410 seconds remaining.
INFO 21:39:49.858557301 [routing::states::node node.rs:2316] Node(b66a45..()) All 15 resource proof responses fully sent. 80/410 seconds remaining.
INFO 21:40:19.858745562 [routing::states::node node.rs:2316] Node(b66a45..()) All 15 resource proof responses fully sent. 50/410 seconds remaining.
INFO 21:40:49.858925496 [routing::states::node node.rs:2316] Node(b66a45..()) All 15 resource proof responses fully sent. 20/410 seconds remaining.
INFO 21:41:09.856932277 [routing::states::node node.rs:2350] Node(b66a45..()) Failed to get approval from the network. All 15 resource proof responses fully sent. Terminating node.

#422

Different error now

INFO 22:13:50.502452135 [routing::states::node node.rs:2344] Node(5ea36b..()) All 15 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.