My experience for this test so far is : download, unzip, run. Watch it working. period
8 Likes
As well as those beers that @dirvine mentioned, the following`: The SAFE Network Release Cycle. As you may have gathered from the even… | by MaidSafe | safenetwork | Medium
14 Likes
I can confirm it all runs on Mac OSX, too.
Don’t see any safe-vault files in my /tmp though (are they stored somewhere else on mac?) and I get many (every couple of seconds or so) Failed to connect to Peer-warnings like this:
INFO 19:22:49.855046000 [routing::core core.rs:392] Node(fcd1..) - Indirect connections: 4, tunneling for: 0
WARN 19:23:06.106169000 [routing::core core.rs:598] Node(fcd1..) Failed to connect to peer PeerId(8da7..): Error { repr: Custom(Custom { kind: TimedOut, error: StringError("Connect failed. errors: (1 of 5) Tcp direct connect failed: Zero byte read - EOF reached, graceful exit. (2 of 5) Tcp hole punching failed: Tcp hole punching timed out without making a successful connection. The following warnings were raised during hole punching: 20 warning(s): (1 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Connection refused (os error 61) (2 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (3 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (4 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (5 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (6 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (7 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (8 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (9 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (10 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (11 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (12 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (13 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (14 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (15 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (16 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (17 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (18 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (19 of 20) Connecting to endpoint 127.0.0.1:46331 failed: Invalid argument (os error 22) (20 of 20) Connecting to endpoint 50.98.55.159:46331 failed: Address already in use (os error 48) (3 of 5) Tcp direct connect failed: Operation timed out (os error 60) (4 of 5) Tcp direct connect failed: Operation timed out (os error 60) (5 of 5) Tcp direct connect failed: Operation timed out (os error 60)") }) }.
INFO 19:23:06.125183000 [routing::core core.rs:392] Node(fcd1..) - Indirect connections: 5, tunneling for: 0
Inlcuding some that reference 127.0.0.1:
INFO 19:25:15.239339000 [routing::core core.rs:2505] Dropped ecbd.. from the routing table.
INFO 19:25:15.240559000 [routing::core core.rs:407] -------------------------------------------------------
INFO 19:25:15.240587000 [routing::core core.rs:409] | Node(fcd1..) PeerId(3014..) - Routing Table size: 46 |
INFO 19:25:15.240614000 [routing::core core.rs:410] -------------------------------------------------------
WARN 19:25:32.670487000 [routing::core core.rs:598] Node(fcd1..) Failed to connect to peer PeerId(200e..): Error { repr: Custom(Custom { kind: TimedOut, error: StringError("Connect failed. errors: (1 of 4) Tcp direct connect failed: Zero byte read - EOF reached, graceful exit. (2 of 4) Tcp direct connect failed: Connection refused (os error 61) (3 of 4) Tcp direct connect failed: Connection refused (os error 61) (4 of 4) Tcp hole punching failed: Tcp hole punching timed out without making a successful connection. The following warnings were raised during hole punching: 37 warning(s): (1 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Connection refused (os error 61) (2 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (3 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (4 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (5 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Connection refused (os error 61) (6 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (7 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (8 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (9 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Connection refused (os error 61) (10 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (11 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (12 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (13 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Invalid argument (os error 22) (14 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (15 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (16 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (17 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Invalid argument (os error 22) (18 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (19 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (20 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (21 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Invalid argument (os error 22) (22 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (23 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (24 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (25 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Invalid argument (os error 22) (26 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (27 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (28 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (29 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Invalid argument (os error 22) (30 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (31 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (32 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (33 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Invalid argument (os error 22) (34 of 37) Connecting to endpoint 127.0.0.1:56419 failed: Invalid argument (os error 22) (35 of 37) Connecting to endpoint 77.243.183.91:56419 failed: Address already in use (os error 48) (36 of 37) Connecting to endpoint 192.168.2.101:56419 failed: Invalid argument (os error 22) (37 of 37) Connecting to endpoint 10.129.6.186:56419 failed: Invalid argument (os error 22)") }) }.
INFO 19:25:32.860847000 [routing::core core.rs:392] Node(fcd1..) - Indirect connections: 7, tunneling for: 0
INFO 19:25:32.863092000 [routing::core core.rs:1553] Node(fcd1..) Added e79e.. to routing table.
I guess that is ok as they are WARN !?! Let me know if I should provide more logs for debugging.
Update: since I started to write this, the frequency of those warnings went down to … well, it doesn’t seem to be happening anymore now.
4 Likes
I’m so unbelievably proud of you guys. My wife and I are so privileged to be apart of this community and will do what we can to accelerate successes. Love you guys <3
5 Likes
Yes that’s all good so far. The logs look fine. Nodes when trying to connect will try every interface on each side, so should fail a lot.
3 Likes
HURRAY!
More progress 
Gotta love the surprise friday updates.
6 Likes
sooooooo - i have to go now 
:-\ i’ll just leave the pc on and 2 vaults running and wait what happens to my vaults till i come back tomorrow Oo …
2 Likes
Please do! I won’t be able to run until I get home from work tonight, but that would be amazing to have. Otherwise I’ll do that myself tonight. Great idea!
P.S. TIL nload
EDIT: I remember my days using the Solarized colorscheme…
3 Likes
Isn’t it nice when things just work 
Very simple to get this working - Linux Mint 17.3 Rosa.
One change I’d like to see is the progress of file uploads made apparent in the app, as atm I know it’s uploading only for having stopped and seen some progress and then watched the text detail for the put success. Progress bar at 0% and I’ll leave that running expecting I’ll hit the upper limit at some point.
A couple of questions while I think of them:
As users, will we know how many nodes exist? Will we know how much is put and get from the network at any one time?
Will the spare capacity and throughput of the network, be apparent to users or is it simple that the network responds to demand evidencing capacity without declaring it?
4 Likes
Everything’s localized, so the best you can do is estimate based on the density of XOR addresses.
3 Likes
During tests/alpha yes you will see some of this, but as we move through beta then the networks in control and won’t ell us We can make estimates based on network density on routing tables, but likely only after the network is many thousands / millions of nodes.
3 Likes
Cpu usage around 25% (no errors in logging). I guess this will improve in time?
2 Likes
You could do that quite easily with GitHub - yudai/gotty: Share your terminal as a web application I think
3 Likes
If I wanted to share it or view it in the browser it looks like that would work. But if I just wanted to open a tmux session in a local terminal that automatically popped up - for instance - a copy of all the programs that you’re running in your scrot then I’d make a tmux-session script that automatically partitioned the terminal with tmux and ran the appropriate programs. In this case, network monitoring tools.
https://wiki.archlinux.org/index.php/Tmux#Start_tmux_with_default_session_layout
CPU usage on my macbook air (1,7GHz, dual-core, 8Gig Mem) is at around 55-65% ongoing (rarely drops below 50%). It is quite the battery eater…
1 Like
how many faults have you running parallel? I have 10 vaults up, cpu is between 20 to 50%
1 Like
one.
I have one vault running only.
I had to reset the vault a couple of times and now it will not connect. It says
[routing::core core.rs:1198] Running listener.
and then stoppes
Any one else seeing this?
sounds like there is still a process/thread running. on linux does ps | grep safe_vault bring anything up (other than grep itself)? then you need to kill (or kill -9) those (supplying the pid of the processes that showed up in the list)
Worked like a charm on first try, 50-70 connections established on safe_vault.exe.
THIS IS AMAZING
Uploaded an mp3, everything worked fine!
A little bluesthingy I did as I started learning some open D stuff: http://music.chris.safenet/
5 Likes