MaidSafe Dev Update :safe: 21st April 2016

This was basically a “what happens when a mass of people all join ad the same time, and what does it break?” test. They’ll fix what they think needs to be fixed and we’ll try it again. Productive regardless initial result.

4 Likes

I couldn’t get it to work. But like they said, it was for the geeks out here to try it out first. Probably a better test as well instead of hundreds of Vault coming online at once. According to David they go some great insights. So that sounds great. I’ll wait for the MVP to join the network.

7 Likes

This was for the capable to help test vaults. Rather than for normal use. As @polpolrene said [quote=“polpolrene, post:156, topic:8826”]
it was for the geeks out here to try it out first. Probably a better test as well instead of hundreds of Vault coming online at once.
[/quote]

4 Likes

Can’t get it to work at all.

TPGs-Mac-Pro:safe_vault-v0.6.0-osx-x64 tpg$ RUST_LOG=routing=info ./safe_vault
WARN 18:33:21.870952000 [w_result lib.rs:288] Error mapping external address and port through IGD gateway at address 192.168.192.1:80. igd::Gateway::get_any_address returned an error: Request error. HTTP error. connection reset
WARN 18:33:22.221132000 [w_result lib.rs:288] Error mapping external address and port through IGD gateway at address 192.168.192.1:80. igd::Gateway::get_any_address returned an error: Request error. HTTP error. connection reset
WARN 18:33:22.579385000 [w_result lib.rs:288] Error mapping external address and port through IGD gateway at address 192.168.192.1:80. igd::Gateway::get_any_address returned an error: Request error. HTTP error. connection reset
WARN 18:33:22.601859000 [crust::connection connection.rs:163] TCP direct connect failed: Connection refused (os error 61)
WARN 18:33:22.601893000 [crust::bootstrap bootstrap.rs:121] Error connecting to bootstrap peer: Connection refused (os error 61)
WARN 18:33:22.623253000 [crust::connection connection.rs:163] TCP direct connect failed: Connection refused (os error 61)
WARN 18:33:22.623272000 [crust::bootstrap bootstrap.rs:121] Error connecting to bootstrap peer: Connection refused (os error 61)
WARN 18:33:22.647629000 [crust::connection connection.rs:163] TCP direct connect failed: Connection refused (os error 61)
WARN 18:33:22.647646000 [crust::bootstrap bootstrap.rs:121] Error connecting to bootstrap peer: Connection refused (os error 61)
WARN 18:33:58.641725000 [crust::connection connection.rs:163] TCP direct connect failed: Connection refused (os error 61)
WARN 18:33:58.641739000 [crust::bootstrap bootstrap.rs:121] Error connecting to bootstrap peer: Connection refused (os error 61)
WARN 18:33:58.661668000 [crust::connection connection.rs:163] TCP direct connect failed: Connection refused (os error 61)
WARN 18:33:58.661688000 [crust::bootstrap bootstrap.rs:121] Error connecting to bootstrap peer: Connection refused (os error 61)
WARN 18:33:58.681862000 [crust::connection connection.rs:163] TCP direct connect failed: Connection refused (os error 61)
WARN 18:33:58.681894000 [crust::bootstrap bootstrap.rs:121] Error connecting to bootstrap peer: Connection refused (os error 61)
WARN 18:33:59.292067000 [w_result lib.rs:288] Error mapping external address and port through IGD gateway at address 192.168.192.1:80. igd::Gateway::get_any_address returned an error: Request error. HTTP error. connection reset
INFO 18:33:59.292212000 [routing::core core.rs:1231] Running listener.

Opened port in config and router. Even restarted router.

1 Like

The rest of the network is not up and running right now. The test only lasted a few hours. Bootstrap nodes have been taken down. Looks like some time next week (subject to change) we should have another test and it might last longer - depending on how the changes made from this experiment work out.

7 Likes

@Ross how about putting up a testnet status page people can monitor?

If so, I suggest that when it is live it includes a link to “how to join this testnet” as well as an expected duration / end time, the relevant vault & launcher versions, and a short description of the testnet purpose, plus summary of capabilities and limitations.

When it is not live, it can include an estimate of when the next testnet will begin ď if you’re really ambitious :slight_smile:, with suitable caveat!)

14 Likes

Yes, yes. Exactly.

So to put it in plain English for everyone to realize, right here, right now:

THE FIRST VAULT TEST HAS COMPLETED SUCCESSFULLY. DO NOT ATTEMPT TO FOLLOW THE ORIGINAL POST ANYMORE / I.E. CONNECT YOUR VAULT TO THE NETWORK.

Wait for the next update before continuing. (Unless you just want to mess around with this one 4 no reason.)

The next update, you will not have to jump through complicated hoops to connect your vaults to everyone’s! (I may be wrong on that. But everything so far has pointed to the fact that the next update will provide easy, instant interconnected Vaults for most people.) This thread’s update was a necessary albeit complicated step to test the waters for field bugs. Or water bugs.

5 Likes

@happybeing this makes a lot of sense - I will raise it at our morning catch-up tomorrow morning.

10 Likes

(safe_launcher-v0.4.2-win-x64 ) i downloaded it on my windows 10 from yesterday till now is still on ( Trying to connect with SAFE Network )

2 Likes

sometime this week can try again; check here and it will be announced; welcome to the forum btw @DONWISE

3 Likes

@dirvine @anon86652309 Any chance you could update http://apt-alpha.maidsafe.net/ ?

I’d have thought sticking UnattendedUpgrades - Debian Wiki on your boxes and upgrading that repo would simplify upgrading your test network in any case?

Thanks

Sam

1 Like

Doesnt resolve even on dns level atm.

http://apt.maidsafe.net/ :wink:

[EDIT - to confirm this does not yet contain the updated vaults, it will very soon though ]

10 Likes

There is the old Network Visualiser - Testnet Status page that could be recycled for this purpose.

4 Likes

There is already a plan for another form of this, but it will be extremely dev focussed and nowhere near as pretty. Should help a lot to explain and show what happens though for very interested folks.

5 Likes

I had found http://yum.maidsafe.net/, too

2 Likes

The apt package is cool. However, I just cannot connect it to the server. Also, why does it require root to run?

This is not the vaults to use for now, just packages in readiness. Please do not expect these to work just now or we would be launched :slight_smile: This is to show we are preparing for general availability :wink: Cheers folks

9 Likes

I decided to see how this essential work is progressing since I tried it out in February.
I downloaded the latest safe_launcher-v0.4.2-linux-x64.tar.gz to use with my latest Ubuntu 16.04.
I followed the same steps as before, but now the launcher just says “Trying to connect with SAFE Network”.
I see others have also had this problem. I’m located in Toronto Canada.
Is there a resolution to this problem?
Thanks.

Simple answer. There is no network to connect to.

see

3 Likes