"community1" Test Network is Alive, Join Us!

Development
142

@bluebird
When restarting my vault…do I have to clear my node log as well?

143

Probably not. I only do that when the usual restart (via script) does not work.

144

Right now my routing table size is 10… so it seems to be working fine.

1 Like
145

10 here now too. (20 chars)

2 Likes
146

can you paste the config file please?

I want to play too :slight_smile:

147

I PM’d it. (20 chars)

1 Like
148

The community1 network is still running. We could use a few more vaults, if you would like to join. We are open for developers to run their apps. The binary is testnet3 so data is not persistent, but the network it quite stable. We changed ports in order to avoid inadvertent attack by newer binaries, so PM me for the config to use. We will upgrade the binary at the conclusion of testnet4.

1 Like
149

I’m taking the seed vault down for a short time to try something different.

1 Like
150

Hmm, on the seed vault I’m now running a new compile of the latest safe_vault and seeing a flood of “incompatible protocol version” messages, just like before. There is only one other vault on the network (the other hard-coded contact), which is running the testnet3 binary. Conclusion: nothing has changed since I first reported this bug, except to note that it affects new binaries as well as old ones.

1 Like
151

do u want me to do the same of leave alone?

rup

152

If you could load the binary that I sent the link to, we’ll see if we can build the network up.

153

loaded the binary in the OP link with the config posted. Took a minute to info, but this is what I have right now.

mranderson@mranderson-Z68A-D3H-B3:~/Desktop/safe_vault-v0.8.1-linux-musl-x64$ sudo ./safe_vault
[sudo] password for mranderson:
INFO 17:48:30.446161155 [safe_vault safe_vault.rs:96]

Running safe_vault v0.8.1
=========================
INFO 17:50:39.175753849 [routing::core core.rs:1211] Running listener.
`indent preformatted text by 4 spaces``

second vault started and after a few minutes got this:

Running safe_vault v0.8.1
=========================
INFO 17:57:08.415239947 [routing::core core.rs:1211] Running listener.
WARN 17:57:08.417353465 [routing::core core.rs:1345] Connection failed: Proxy node needs a larger routing table to accept clients.
WARN 17:57:08.417525561 [safe_vault::vault vault.rs:134] Received Event::Disconnected. Restarting Vault
154

The OP config is invalid.

I got bored waiting for testnet4 so I have replaced the binary on the seed vault with one that I compiled a couple of hours ago from the latest safe_vault on github (want to see if it runs more efficiently, with more instances). To connect to it, you need to download the binary from here:
http://91.121.173.204//safe_vault

The config to use is:

{
  "hard_coded_contacts": [
    {
      "tcp_acceptors": [
        "91.121.173.204:62000"
      ],
      "tcp_mapper_servers": []
    },
    {
      "tcp_acceptors": [
        "185.16.37.156:62000"
      ],
      "tcp_mapper_servers": []
    }
  ],
  "tcp_acceptor_port": 62000,
  "service_discovery_port": null,
  "bootstrap_cache_name": null,
  "tcp_mapper_servers": [],
  "network_name": "community1"
}

The port was changed to keep incompatible binaries out and if that problem occurs again then we’ll have to change it again, since it seems that Maidsafe have not patched the bug reported two weeks ago.

2 Likes