If you mean rob vaults, then wow! If rub vaults, then I’m unclear as to what you mean.
I might have missed the announcement where testnet_4 will be running off of volunteer test machines, so there’s that. Can anyone else confirm this, or still on droplets? If this is true, it’s huge news and should be more prominent in the development update.
I know a big goal in the next testnet or two will be data persistence, but in your case, there are dozens of apps/resources where your machine allocated 500MB to.
on my windows 7, browse to %appdata% in “Windows Explorer” and go to C:\Users\me\AppData\Local\Temp and look for a directory with the words safe at the beginning and check the date for newest create date.
*** me in the path needs to be whatever your user directory in windows is or where the vault software was run from.
What doesn’t kill us makes us stronger. It’s good experience to know the real limits, even if such an event would not be practical in a large network. Worse would be tests that appeared like an illusion that there were no limits.
Hi folks, we will need to restart the network in the morning. There was an error that caused possibly 1200 nodes to start up and stop again. It was done with best intentions and will be a great help moving forward. No malice or attack, but it would have meant it was over 80% possibly and the network then struggles. So we will restart tomorrow and try again. The results so far are very impressive so lets bash it around more, but maybe not with so many nodes going off at once. A few hundred may have been ok, but it was just too much.
Sorry for any inconvenience, lets do it again though. Just a restart and away we go.
Running a win x64 vault on this win7 x64 machine also seems to only connect to the other lan vault (linux x64) and nowhere else and this looks like follows:
INFO 00:48:35.926701200 [safe_vault safe_vault.rs:96]
Running safe_vault v0.9.0
=========================
INFO 00:48:38.195830900 [routing::core core.rs:1032] Client(e0b284..) Running li
stener.
INFO 00:48:41.333010400 [routing::core core.rs:1555] Client(e0b284..) Sending Ge
tNodeName request with: PublicId(name: e0b284..). This can take a while.
INFO 00:49:41.334442300 [routing::core core.rs:1807] Client(e0b284..) Failed to
get GetNodeName response.
WARN 00:49:41.334442300 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:49:43.668575800 [routing::core core.rs:1032] Client(e6e070..) Running li
stener.
INFO 00:49:46.842757300 [routing::core core.rs:1555] Client(e6e070..) Sending Ge
tNodeName request with: PublicId(name: e6e070..). This can take a while.
INFO 00:50:46.844189200 [routing::core core.rs:1807] Client(e6e070..) Failed to
get GetNodeName response.
WARN 00:50:46.844189200 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:50:49.218325000 [routing::core core.rs:1032] Client(186872..) Running li
stener.
INFO 00:50:52.353504300 [routing::core core.rs:1555] Client(186872..) Sending Ge
tNodeName request with: PublicId(name: 186872..). This can take a while.
INFO 00:51:52.355936300 [routing::core core.rs:1807] Client(186872..) Failed to
get GetNodeName response.
WARN 00:51:52.355936300 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:51:54.948084500 [routing::core core.rs:1032] Client(640556..) Running li
stener.
INFO 00:51:57.964257000 [routing::core core.rs:1555] Client(640556..) Sending Ge
tNodeName request with: PublicId(name: 640556..). This can take a while.
INFO 00:52:57.965688900 [routing::core core.rs:1807] Client(640556..) Failed to
get GetNodeName response.
WARN 00:52:57.965688900 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:53:00.461831700 [routing::core core.rs:1032] Client(888d3c..) Running li
stener.
Via procexp (process explorer, sysinternals) or via similar tools, I see the safe_vault.exe having exactly one tcp established to that other lan vault. This second vault is bootstrapping nowhere it seems.
P.S. okay you guys seem to needing a network reboot as whole. Maybe it was all related and the launcher also going nowhere but the lan vault.
So we should standby for a new config file download and then restart the vaults?
Should we go easy this time and only start 1 or 2 vaults per box?
I had 12 running at work on a Win7 box and 8 on the Ubuntu laptop at home.
You should be OK just to restart the vaults now. Config the same but lots of nodes joining right now, so may take time, but will be OK.
Thanks everyone
@Josh if you open a terminal then cd to the directory where you unpack the vault just type ./safe_vault in that dir. don’t miss out the dot forward slash at the start.
would suggest just running a single vault on a machine
Adding more vaults on the same machine doesnt add much to the overall network(it spreads nodes a lot more and data will be dispersed to greater levels), but it effectively reduces the capability of the machine as multiple nodes are now sharing the same bandwidth and are going to throttle each other in terms of throughput while dealing with more hops in the network.
For a rough example, If you say have a 500Kbps upload on your connection and you run 5 vaults, and all vaults are “active” (handling client requests), then each vault is only getting a portion of the 500Kbps capability of the network connection instead of the single vault being able to utilise the full 500Kbps when needed. This is a crude example, but hope that helps.
so lets see how it goes this time 
thanks guys!