User run network based on test 12b binaries

safe://eeek.southside/

1 Like

hiya,

am i missing something?

doesn’t seem to be anyone to bootstrap too…

is anybody running?

rup

Yes it’s up. Routing table size is 13. What config file are you using?

1 Like

lol… obviously the wrong one!!

can you pop me the latest?

also once its up i’ll leave so the ip can be added as a bootstrap vault.

185.16.37.149

rup

1 Like

No probs. I haven’t tried starting again since yesterday though. Hopefully this still works

{
“hard_coded_contacts”: [
“86.184.57.178:5483”,
“13.80.119.160:5483”,
“85.93.19.51:5483”,
“35.157.162.33:5483”,
“35.156.220.253:5483”
],
“bootstrap_whitelisted_ips”: ,
“tcp_acceptor_port”: null,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_feb_2017”
}

1 Like

ah, network name has changed…

now running with 14 peers…

please add my ip to the list as it will be up now til something changes

{
“hard_coded_contacts”: [
“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”: null,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_feb_2017”
}

rup

3 Likes

Welcome aboard 8a5cb9!

1 Like

thanks!!

anyone seen bluebird? he was my partner running vaults last year…

nice to put something back…

rup

1 Like

Didn’t know a network was up yesterday so I tried with 10 droplets but couldn’t bootstrap somehow.

I’m now at work and try to join community network this evening.

Any idea what I did wrong?

  • 10 droplets public ip’s:5483 put in hard_coded_contracts
  • open firewall ports 5483 5484
  • boot first vault with option -f
  • same network name in config file for every vault

Now I see above that service_discovery_port is null ??

It wasn’t working for most people at first yesterday. If you try again with the config file above you might have more luck. Don’t use the -f option though.

Check you have the latest IPs from posts above

No need for this - the network is running[quote=“4M8B, post:300, topic:12487”]

  • same network name in config file for every vault
    [/quote]
    Make sure you are using community_network_feb_2017

EDIT @JPL beat me to it :slight_smile:

1 Like

What was in your log? This one?

1 Like

I’ll take a look this evening to see if it was this error.

1 Like

this defo works as i type this:

{
“hard_coded_contacts”: [
“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”: null,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_feb_2017”
}

INFO 11:41:09.814440873 [routing::states::node node.rs:277] ---------------------------------------------------------------
INFO 11:41:09.814461559 [routing::states::node node.rs:278] | Node(8a5cb9…()) PeerId(ecca0561…) - Routing Table size: 15 |
INFO 11:41:09.814466850 [routing::states::node node.rs:279] ---------------------------------------------------------------
INFO 11:41:09.814517185 [safe_vault::personas::maid_manager maid_manager.rs:256] Managing 4 client accounts.

everything seems very stable and happy…

rup

1 Like

You have a double dot in “185.16…37.149:5483” :frowning:

I’m doing some tests with @polpolrene and @Viv

I’m using my 35.157.162.33 AWS node so best that it gets removed from the seed nodes for now.

35.156.100.37
and
35.156.220.253

are stll OK though

Except that screen retains output from the process… and & perhaps loses content. I suggest Screen well worth learning for remote server… it is simple as knowing if you are in the screen or not and Ctrl-A + D to exit and leave it running.

Incidentally the other ‘trick’ I learned is for programs that might fall over there’s the option of putting to a do while loop that sees them rise again… though I doubt we need that for SAFE; unless the way droplets reboots does something I’m not familiar with and needs that.

eg (perhaps Linux only)
while true; do ./SOMETHING; done;

2 Likes

Screen is worth learning of course.
Indeed
./safe_output&
could loose output, but not
nohup ./safe_output&

I was the last days also thinking of an infinite loop, in case safe_vault stops.

3 Likes

Ok I will take my vaults down one at a time so I can try

nohup ./safe_vault

I’m in also from coming from digitalOcean. (67.205.129.163)

First I got this error

  `Running safe_vault v0.13.0
==========================
ERROR 19:26:24.403888901 [crust::main::bootstrap mod.rs:184] Failed to Bootstrap: (FailedExternalReachability) Bootstrapee node could not establish connection to us.
INFO 19:26:24.404576934 [routing::states::bootstrapping bootstrapping.rs:201] Bootstrapping(11a7cd..) Failed to bootstrap. Terminating`

Just by disabling the firewall everything went smooth.

Running safe_vault v0.13.0
==========================
INFO 19:30:48.691298844 [routing::states::node node.rs:1240] Node(54b034..()) Requesting a relocated name from the network. This can take a while.
INFO 19:30:49.114250743 [routing::states::node node.rs:1890] Node(51f10a..()) Received relocated name. Establishing connections to 18 peers.
INFO 19:30:49.275644816 [routing::states::node node.rs:1031] Node(51f10a..()) Starting approval process to test this node's resources. This will take at least 300 seconds.
INFO 19:30:49.600789256 [routing::states::common::base base.rs:73] Node(51f10a..()) Connection to PeerId(9171505e..) failed: PeerNotFound(PeerId(9171505e..))
INFO 19:30:49.601850244 [routing::states::common::base base.rs:73] Node(51f10a..()) Connection to PeerId(9171505e..) failed: PeerNotFound(PeerId(9171505e..))
INFO 19:30:49.602464063 [routing::states::node node.rs:2769] Node(51f10a..()) Dropped a210fd.. from the routing table.
INFO 19:31:19.114452179 [routing::states::node node.rs:2316] Node(51f10a..()) 0/17 resource proof response(s) complete, 35% of data sent. 380/410 seconds remaining.
INFO 19:31:49.114614680 [routing::states::node node.rs:2316] Node(51f10a..()) 2/17 resource proof response(s) complete, 79% of data sent. 350/410 seconds remaining.
INFO 19:32:19.115229545 [routing::states::node node.rs:2316] Node(51f10a..()) 15/17 resource proof response(s) complete, 93% of data sent. 320/410 seconds remaining.
INFO 19:32:49.115605249 [routing::states::node node.rs:2316] Node(51f10a..()) 16/17 resource proof response(s) complete, 94% of data sent. 290/410 seconds remaining.
INFO 19:33:19.116584675 [routing::states::node node.rs:2316] Node(51f10a..()) 16/17 resource proof response(s) complete, 94% of data sent. 260/410 seconds remaining.
INFO 19:33:49.116731598 [routing::states::node node.rs:2316] Node(51f10a..()) 16/17 resource proof response(s) complete, 94% of data sent. 230/410 seconds remaining.
INFO 19:34:19.117090665 [routing::states::node node.rs:2316] Node(51f10a..()) 16/17 resource proof response(s) complete, 94% of data sent. 200/410 seconds remaining.
INFO 19:34:49.117418745 [routing::states::node node.rs:2316] Node(51f10a..()) 16/17 resource proof response(s) complete, 94% of data sent. 170/410 seconds remaining.
INFO 19:35:19.117804766 [routing::states::node node.rs:2316] Node(51f10a..()) 16/17 resource proof response(s) complete, 94% of data sent. 140/410 seconds remaining.
INFO 19:35:49.121802528 [routing::states::node node.rs:2316] Node(51f10a..()) 16/17 resource proof response(s) complete, 94% of data sent. 110/410 seconds remaining.
INFO 19:35:49.205122001 [routing::states::node node.rs:1001] Node(51f10a..()) Resource proof challenges completed. This node has been approved to join the network!
INFO 19:35:49.205405731 [routing::states::node node.rs:277]  --------------------------------------------------------------- 
INFO 19:35:49.205538604 [routing::states::node node.rs:278] | Node(51f10a..()) PeerId(a22ae0bb..) - Routing Table size:  17 |
INFO 19:35:49.205689333 [routing::states::node node.rs:279]  --------------------------------------------------------------- 
INFO 19:35:49.237404605 [safe_vault::personas::maid_manager maid_manager.rs:221] Managing 1 client accounts.
INFO 19:35:49.282497172 [safe_vault::personas::maid_manager maid_manager.rs:221] Managing 2 client accounts.
INFO 19:35:49.470632217 [safe_vault::personas::maid_manager maid_manager.rs:221] Managing 3 client accounts.
INFO 19:35:49.483434856 [safe_vault::personas::maid_manager maid_manager.rs:221] Managing 4 client accounts.
INFO 19:35:49.617828049 [safe_vault::personas::data_manager data_manager.rs:751] This vault has received 0 Client Get requests. Chunks stored: Immutable: 1, Structured: 0, Appendable: 0. Total stored: 411 bytes.
3 Likes