"community1" Test Network Has Restarted, Join Us!

bluebird · June 24, 2016, 12:59am

This is to announce the “reboot” of community1 test network, now that testnet4 is winding down. The theme of community1 is now “The Bleeding Edge Community Network” and its distinction will be to host the very latest builds of the SAFE network software.

The configs are here: http://91.121.173.204/configs/

I have nightly builds of the binary at the links below (they include the libsodium library):
http://91.121.173.204/amd64/safe_vault
http://91.121.173.204/armv7/safe_vault

Those are fresh builds from the repo, automatically generated late every night.

…just AMD64 and ARMV7 for now, but other platforms will soon be supported.

…or you can use the release from Testnet4:
https://github.com/maidsafe/safe_vault/releases/tag/0.9.0

Please put the appropriate binary, safe_vault.crust.config and log.toml in a folder, open a terminal session in that folder and give the command ./safe_vault

Important Addition:

For the convenience of participants, I have assembled the configs and binaries into four variations (for now), at the link below Please download one, probably “community1-amd64-release” if your computer is a regular PC running 64-bit Linux, and run one or two instances of it (i.e., separate folders). No modifications or additions are required!

“Release” is the official binary as used in testnet4, while “latest” is one that I compile nightly straight from the github repo.

Packages: http://91.121.173.204/packages/

Blindsite2k · June 24, 2016, 7:49am

I’m having trouble configuring everything and getting the vault/launcher to work. I copied the files given but the vaults keep giving me error messages.

Running safe_vault v0.9.0
=========================
INFO 23:58:43.180699000 [routing::core core.rs:1032] Client(684f94..) Running listener.
INFO 23:58:43.544698839 [routing::core core.rs:1555] Client(684f94..) Sending GetNodeName request with: PublicId(name: 684f94..). This can take a while.
INFO 23:59:43.544176019 [routing::core core.rs:1807] Client(684f94..) Failed to get GetNodeName response.
WARN 23:59:43.544279697 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 23:59:46.232271032 [routing::core core.rs:1032] Client(840953..) Running listener.
INFO 23:59:46.574308205 [routing::core core.rs:1555] Client(840953..) Sending GetNodeName request with: PublicId(name: 840953..). This can take a while.
INFO 00:00:46.574208547 [routing::core core.rs:1807] Client(840953..) Failed to get GetNodeName response.
WARN 00:00:46.574407489 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:00:49.269388201 [routing::core core.rs:1032] Client(cfaa37..) Running listener.
INFO 00:00:49.609924477 [routing::core core.rs:1555] Client(cfaa37..) Sending GetNodeName request with: PublicId(name: cfaa37..). This can take a while.
INFO 00:01:49.630257641 [routing::core core.rs:1807] Client(cfaa37..) Failed to get GetNodeName response.
WARN 00:01:49.630351668 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:01:52.357139518 [routing::core core.rs:1032] Client(f8b88e..) Running listener.
INFO 00:01:52.720076611 [routing::core core.rs:1555] Client(f8b88e..) Sending GetNodeName request with: PublicId(name: f8b88e..). This can take a while.
INFO 00:02:52.720083068 [routing::core core.rs:1807] Client(f8b88e..) Failed to get GetNodeName response.
WARN 00:02:52.720278212 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:02:55.455203396 [routing::core core.rs:1032] Client(72fdf1..) Running listener.
INFO 00:02:55.805517023 [routing::core core.rs:1555] Client(72fdf1..) Sending GetNodeName request with: PublicId(name: 72fdf1..). This can take a while.
INFO 00:03:55.805416610 [routing::core core.rs:1807] Client(72fdf1..) Failed to get GetNodeName response.
WARN 00:03:55.805777621 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:03:58.492668355 [routing::core core.rs:1032] Client(78d328..) Running listener.
INFO 00:03:58.830336143 [routing::core core.rs:1555] Client(78d328..) Sending GetNodeName request with: PublicId(name: 78d328..). This can take a while.
INFO 00:04:58.830274402 [routing::core core.rs:1807] Client(78d328..) Failed to get GetNodeName response.
WARN 00:04:58.830394121 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:05:01.570968866 [routing::core core.rs:1032] Client(4ed3d7..) Running listener.
INFO 00:05:01.928000692 [routing::core core.rs:1555] Client(4ed3d7..) Sending GetNodeName request with: PublicId(name: 4ed3d7..). This can take a while.
INFO 00:06:01.927993205 [routing::core core.rs:1807] Client(4ed3d7..) Failed to get GetNodeName response.
WARN 00:06:01.928297489 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:06:04.638768794 [routing::core core.rs:1032] Client(3a0219..) Running listener.
INFO 00:06:04.978944160 [routing::core core.rs:1555] Client(3a0219..) Sending GetNodeName request with: PublicId(name: 3a0219..). This can take a while.
INFO 00:07:04.979010451 [routing::core core.rs:1807] Client(3a0219..) Failed to get GetNodeName response.
WARN 00:07:04.979177204 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:07:07.695023144 [routing::core core.rs:1032] Client(2a6a57..) Running listener.
INFO 00:07:08.032292023 [routing::core core.rs:1555] Client(2a6a57..) Sending GetNodeName request with: PublicId(name: 2a6a57..). This can take a while.
INFO 00:08:08.032309020 [routing::core core.rs:1807] Client(2a6a57..) Failed to get GetNodeName response.
WARN 00:08:08.032574329 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:08:10.764053990 [routing::core core.rs:1032] Client(dac9be..) Running listener.
INFO 00:08:11.101675733 [routing::core core.rs:1555] Client(dac9be..) Sending GetNodeName request with: PublicId(name: dac9be..). This can take a while.
INFO 00:09:11.101610638 [routing::core core.rs:1807] Client(dac9be..) Failed to get GetNodeName response.
WARN 00:09:11.101779083 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:09:13.811788679 [routing::core core.rs:1032] Client(126c83..) Running listener.
INFO 00:09:14.149043898 [routing::core core.rs:1555] Client(126c83..) Sending GetNodeName request with: PublicId(name: 126c83..). This can take a while.
INFO 00:10:14.148729686 [routing::core core.rs:1807] Client(126c83..) Failed to get GetNodeName response.
WARN 00:10:14.148952292 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:10:16.879928232 [routing::core core.rs:1032] Client(aad450..) Running listener.
INFO 00:10:17.220946433 [routing::core core.rs:1555] Client(aad450..) Sending GetNodeName request with: PublicId(name: aad450..). This can take a while.
INFO 00:11:17.220885168 [routing::core core.rs:1807] Client(aad450..) Failed to get GetNodeName response.
WARN 00:11:17.220985973 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:11:19.937746432 [routing::core core.rs:1032] Client(8a03fc..) Running listener.
INFO 00:11:20.282846562 [routing::core core.rs:1555] Client(8a03fc..) Sending GetNodeName request with: PublicId(name: 8a03fc..). This can take a while.
INFO 00:12:20.282848197 [routing::core core.rs:1807] Client(8a03fc..) Failed to get GetNodeName response.
WARN 00:12:20.283058630 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:12:23.005863082 [routing::core core.rs:1032] Client(5f9317..) Running listener.
INFO 00:12:23.363030763 [routing::core core.rs:1555] Client(5f9317..) Sending GetNodeName request with: PublicId(name: 5f9317..). This can take a while.
INFO 00:13:23.363018701 [routing::core core.rs:1807] Client(5f9317..) Failed to get GetNodeName response.
WARN 00:13:23.363117757 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:13:26.055515137 [routing::core core.rs:1032] Client(2d480c..) Running listener.
INFO 00:13:26.391231629 [routing::core core.rs:1555] Client(2d480c..) Sending GetNodeName request with: PublicId(name: 2d480c..). This can take a while.
INFO 00:14:26.391243891 [routing::core core.rs:1807] Client(2d480c..) Failed to get GetNodeName response.
WARN 00:14:26.391426941 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:14:29.136588510 [routing::core core.rs:1032] Client(3efe7c..) Running listener.
INFO 00:14:29.481604547 [routing::core core.rs:1555] Client(3efe7c..) Sending GetNodeName request with: PublicId(name: 3efe7c..). This can take a while.
INFO 00:15:29.481577567 [routing::core core.rs:1807] Client(3efe7c..) Failed to get GetNodeName response.
WARN 00:15:29.481751251 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:15:32.228807009 [routing::core core.rs:1032] Client(bf2b5e..) Running listener.
INFO 00:15:32.579489849 [routing::core core.rs:1555] Client(bf2b5e..) Sending GetNodeName request with: PublicId(name: bf2b5e..). This can take a while.
INFO 00:16:32.579502573 [routing::core core.rs:1807] Client(bf2b5e..) Failed to get GetNodeName response.
WARN 00:16:32.579658206 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:16:35.379774618 [routing::core core.rs:1032] Client(6d04b1..) Running listener.
INFO 00:16:35.736834917 [routing::core core.rs:1555] Client(6d04b1..) Sending GetNodeName request with: PublicId(name: 6d04b1..). This can take a while.
INFO 00:17:35.736706374 [routing::core core.rs:1807] Client(6d04b1..) Failed to get GetNodeName response.
WARN 00:17:35.736905076 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:17:38.444773876 [routing::core core.rs:1032] Client(93621c..) Running listener.
INFO 00:17:38.779650159 [routing::core core.rs:1555] Client(93621c..) Sending GetNodeName request with: PublicId(name: 93621c..). This can take a while.
INFO 00:18:38.779640404 [routing::core core.rs:1807] Client(93621c..) Failed to get GetNodeName response.
WARN 00:18:38.779949351 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:18:41.522666883 [routing::core core.rs:1032] Client(7c5e4d..) Running listener.
INFO 00:18:41.863656647 [routing::core core.rs:1555] Client(7c5e4d..) Sending GetNodeName request with: PublicId(name: 7c5e4d..). This can take a while.
INFO 00:19:41.863396128 [routing::core core.rs:1807] Client(7c5e4d..) Failed to get GetNodeName response.
WARN 00:19:41.863499436 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:19:44.600551278 [routing::core core.rs:1032] Client(a9ee32..) Running listener.
INFO 00:19:44.951148977 [routing::core core.rs:1555] Client(a9ee32..) Sending GetNodeName request with: PublicId(name: a9ee32..). This can take a while.
INFO 00:20:44.950943052 [routing::core core.rs:1807] Client(a9ee32..) Failed to get GetNodeName response.
WARN 00:20:44.951267677 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:20:47.678489654 [routing::core core.rs:1032] Client(285d41..) Running listener.
INFO 00:20:48.014033840 [routing::core core.rs:1555] Client(285d41..) Sending GetNodeName request with: PublicId(name: 285d41..). This can take a while.
INFO 00:21:48.014010324 [routing::core core.rs:1807] Client(285d41..) Failed to get GetNodeName response.
WARN 00:21:48.014196845 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:21:50.745228850 [routing::core core.rs:1032] Client(e01744..) Running listener.
INFO 00:21:51.106722651 [routing::core core.rs:1555] Client(e01744..) Sending GetNodeName request with: PublicId(name: e01744..). This can take a while.
INFO 00:22:51.106329771 [routing::core core.rs:1807] Client(e01744..) Failed to get GetNodeName response.
WARN 00:22:51.106408035 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:22:53.843915761 [routing::core core.rs:1032] Client(b6df3c..) Running listener.
INFO 00:22:54.183503753 [routing::core core.rs:1555] Client(b6df3c..) Sending GetNodeName request with: PublicId(name: b6df3c..). This can take a while.
INFO 00:23:54.183256469 [routing::core core.rs:1807] Client(b6df3c..) Failed to get GetNodeName response.
WARN 00:23:54.183585181 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:23:56.871776408 [routing::core core.rs:1032] Client(6ad1a6..) Running listener.
INFO 00:23:57.212745568 [routing::core core.rs:1555] Client(6ad1a6..) Sending GetNodeName request with: PublicId(name: 6ad1a6..). This can take a while.
INFO 00:24:57.212527776 [routing::core core.rs:1807] Client(6ad1a6..) Failed to get GetNodeName response.
WARN 00:24:57.212684617 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:24:59.960149566 [routing::core core.rs:1032] Client(cd1eba..) Running listener.
INFO 00:25:00.298586111 [routing::core core.rs:1555] Client(cd1eba..) Sending GetNodeName request with: PublicId(name: cd1eba..). This can take a while.
INFO 00:26:00.298300291 [routing::core core.rs:1807] Client(cd1eba..) Failed to get GetNodeName response.
WARN 00:26:00.298510681 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:26:03.047548207 [routing::core core.rs:1032] Client(5ef946..) Running listener.
INFO 00:26:03.408111857 [routing::core core.rs:1555] Client(5ef946..) Sending GetNodeName request with: PublicId(name: 5ef946..). This can take a while.
INFO 00:27:03.407849676 [routing::core core.rs:1807] Client(5ef946..) Failed to get GetNodeName response.
WARN 00:27:03.408016675 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:27:06.145559050 [routing::core core.rs:1032] Client(c3c55a..) Running listener.
INFO 00:27:06.481147287 [routing::core core.rs:1555] Client(c3c55a..) Sending GetNodeName request with: PublicId(name: c3c55a..). This can take a while.
INFO 00:28:06.480900289 [routing::core core.rs:1807] Client(c3c55a..) Failed to get GetNodeName response.
WARN 00:28:06.481002285 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:28:09.223059849 [routing::core core.rs:1032] Client(ab6fc0..) Running listener.
INFO 00:28:09.552912889 [routing::core core.rs:1555] Client(ab6fc0..) Sending GetNodeName request with: PublicId(name: ab6fc0..). This can take a while.
INFO 00:29:09.552893981 [routing::core core.rs:1807] Client(ab6fc0..) Failed to get GetNodeName response.
WARN 00:29:09.553068983 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:29:12.271136316 [routing::core core.rs:1032] Client(352270..) Running listener.
INFO 00:29:12.617004679 [routing::core core.rs:1555] Client(352270..) Sending GetNodeName request with: PublicId(name: 352270..). This can take a while.
INFO 00:30:12.616686218 [routing::core core.rs:1807] Client(352270..) Failed to get GetNodeName response.
WARN 00:30:12.616867769 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:30:15.328938962 [routing::core core.rs:1032] Client(565c01..) Running listener.
INFO 00:30:15.666094208 [routing::core core.rs:1555] Client(565c01..) Sending GetNodeName request with: PublicId(name: 565c01..). This can take a while.
INFO 00:31:15.665984217 [routing::core core.rs:1807] Client(565c01..) Failed to get GetNodeName response.
WARN 00:31:15.666170152 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:31:18.407090603 [routing::core core.rs:1032] Client(05d0f1..) Running listener.
INFO 00:31:18.742787922 [routing::core core.rs:1555] Client(05d0f1..) Sending GetNodeName request with: PublicId(name: 05d0f1..). This can take a while.
INFO 00:32:18.742555997 [routing::core core.rs:1807] Client(05d0f1..) Failed to get GetNodeName response.
WARN 00:32:18.742849802 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:32:21.444826348 [routing::core core.rs:1032] Client(e85c1f..) Running listener.
INFO 00:32:21.774102220 [routing::core core.rs:1555] Client(e85c1f..) Sending GetNodeName request with: PublicId(name: e85c1f..). This can take a while.
INFO 00:33:21.774220563 [routing::core core.rs:1807] Client(e85c1f..) Failed to get GetNodeName response.
WARN 00:33:21.774365862 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:33:24.482724017 [routing::core core.rs:1032] Client(90f4a8..) Running listener.
INFO 00:33:24.833203186 [routing::core core.rs:1555] Client(90f4a8..) Sending GetNodeName request with: PublicId(name: 90f4a8..). This can take a while.
INFO 00:34:24.832898361 [routing::core core.rs:1807] Client(90f4a8..) Failed to get GetNodeName response.
WARN 00:34:24.833076103 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:34:27.560312172 [routing::core core.rs:1032] Client(d56ad8..) Running listener.
INFO 00:34:27.880940759 [routing::core core.rs:1555] Client(d56ad8..) Sending GetNodeName request with: PublicId(name: d56ad8..). This can take a while.
INFO 00:35:27.880940855 [routing::core core.rs:1807] Client(d56ad8..) Failed to get GetNodeName response.
WARN 00:35:27.881227019 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:35:31.094810591 [routing::core core.rs:1032] Client(44c8bf..) Running listener.
INFO 00:35:31.448765301 [routing::core core.rs:1555] Client(44c8bf..) Sending GetNodeName request with: PublicId(name: 44c8bf..). This can take a while.
INFO 00:36:31.448517940 [routing::core core.rs:1807] Client(44c8bf..) Failed to get GetNodeName response.
WARN 00:36:31.448804128 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:36:34.167803879 [routing::core core.rs:1032] Client(ea94e6..) Running listener.
INFO 00:36:34.503957055 [routing::core core.rs:1555] Client(ea94e6..) Sending GetNodeName request with: PublicId(name: ea94e6..). This can take a while.
INFO 00:37:34.503959325 [routing::core core.rs:1807] Client(ea94e6..) Failed to get GetNodeName response.
WARN 00:37:34.504243850 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:37:37.224302929 [routing::core core.rs:1032] Client(0d6af3..) Running listener.
INFO 00:37:37.559774130 [routing::core core.rs:1555] Client(0d6af3..) Sending GetNodeName request with: PublicId(name: 0d6af3..). This can take a while.
INFO 00:38:37.559516989 [routing::core core.rs:1807] Client(0d6af3..) Failed to get GetNodeName response.
WARN 00:38:37.559852367 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:38:40.738399112 [routing::core core.rs:1032] Client(a3badd..) Running listener.
INFO 00:38:41.088259612 [routing::core core.rs:1555] Client(a3badd..) Sending GetNodeName request with: PublicId(name: a3badd..). This can take a while.
INFO 00:39:41.088082631 [routing::core core.rs:1807] Client(a3badd..) Failed to get GetNodeName response.
WARN 00:39:41.088378961 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:39:43.800130111 [routing::core core.rs:1032] Client(7fe251..) Running listener.
INFO 00:39:44.142038068 [routing::core core.rs:1555] Client(7fe251..) Sending GetNodeName request with: PublicId(name: 7fe251..). This can take a while.
INFO 00:40:44.141761594 [routing::core core.rs:1807] Client(7fe251..) Failed to get GetNodeName response.
WARN 00:40:44.142048952 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:40:46.857879607 [routing::core core.rs:1032] Client(7b7bad..) Running listener.
INFO 00:40:47.187365817 [routing::core core.rs:1555] Client(7b7bad..) Sending GetNodeName request with: PublicId(name: 7b7bad..). This can take a while.
INFO 00:41:47.187140803 [routing::core core.rs:1807] Client(7b7bad..) Failed to get GetNodeName response.
WARN 00:41:47.187473034 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:41:49.906109232 [routing::core core.rs:1032] Client(de74e8..) Running listener.
INFO 00:41:50.272785283 [routing::core core.rs:1555] Client(de74e8..) Sending GetNodeName request with: PublicId(name: de74e8..). This can take a while.
INFO 00:42:50.272739865 [routing::core core.rs:1807] Client(de74e8..) Failed to get GetNodeName response.
WARN 00:42:50.272909841 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:42:52.975547009 [routing::core core.rs:1032] Client(483741..) Running listener.
INFO 00:42:53.313717593 [routing::core core.rs:1555] Client(483741..) Sending GetNodeName request with: PublicId(name: 483741..). This can take a while.
INFO 00:43:53.313714832 [routing::core core.rs:1807] Client(483741..) Failed to get GetNodeName response.
WARN 00:43:53.314076421 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:43:56.062231452 [routing::core core.rs:1032] Client(0a5c94..) Running listener.
INFO 00:43:56.390197296 [routing::core core.rs:1555] Client(0a5c94..) Sending GetNodeName request with: PublicId(name: 0a5c94..). This can take a while.
INFO 00:44:56.389975919 [routing::core core.rs:1807] Client(0a5c94..) Failed to get GetNodeName response.
WARN 00:44:56.390271865 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:44:59.119556538 [routing::core core.rs:1032] Client(34529c..) Running listener.
INFO 00:44:59.474970131 [routing::core core.rs:1555] Client(34529c..) Sending GetNodeName request with: PublicId(name: 34529c..). This can take a while.
INFO 00:45:59.474715132 [routing::core core.rs:1807] Client(34529c..) Failed to get GetNodeName response.
WARN 00:45:59.474867708 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:46:02.187489488 [routing::core core.rs:1032] Client(19e859..) Running listener.
INFO 00:46:02.507613392 [routing::core core.rs:1555] Client(19e859..) Sending GetNodeName request with: PublicId(name: 19e859..). This can take a while.
INFO 00:47:02.507388906 [routing::core core.rs:1807] Client(19e859..) Failed to get GetNodeName response.
WARN 00:47:02.507703289 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:47:05.255085924 [routing::core core.rs:1032] Client(564da1..) Running listener.
INFO 00:47:05.580482307 [routing::core core.rs:1555] Client(564da1..) Sending GetNodeName request with: PublicId(name: 564da1..). This can take a while.
INFO 00:48:05.580377973 [routing::core core.rs:1807] Client(564da1..) Failed to get GetNodeName response.
WARN 00:48:05.580554631 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 00:48:08.312902370 [routing::core core.rs:1032] Client(c6fee4..) Running listener.
INFO 00:48:08.674042941 [routing::core core.rs:1555] Client(c6fee4..) Sending GetNodeName request with: PublicId(name: c6fee4..). This can take a while.

And so on. So some help would be appreciated.

bluebird · June 24, 2016, 10:05am

Thank you for your participation!

It’s experimental, of course: we just see what works, and maybe learn something along the way.

To provide a baseline, I have just now restarted the seed vault using the testnet4 binary (link above) since (as far as I know) it has no “one vault per LAN” limit. Which is not to say it might have other limits.

Using the same binary (and config) on two office vaults (same LAN as each other), they connect OK!

However, a third office vault will not connect, despite many restarts:

INFO 11:01:31.766641307 [routing::core core.rs:1555] Client(8bc1f5…) Sending GetNodeName request with: PublicId(name: 8bc1f5…). This can take a while.

So the limit might be two vaults per LAN on that binary? I only ran one local vault on testnet4 so I’m not sure. Then again, there were many bootstrap nodes on testnet4, so perhaps the limit is vaults on the same LAN bootstrapping per bootstrap node.

Blindsite2k · June 24, 2016, 10:07am

Okay so… what can I do to get this thing running?

bluebird · June 24, 2016, 10:11am

Use the testnet4 safe_vault binary + the config and log.toml in the configs folder I link to above. Put them in the same folder. Delete any Node.log already there. Check that the binary is executable. Start it with:

./safe_vault

Blindsite2k · June 24, 2016, 10:56am

Did that and this time deleted the node.log. Still sluggish and I’m starting to get the warns again.

bluebird · June 24, 2016, 11:15am

I don’t know, but the lack of bootstrap nodes is probably a factor. The other seed node is not yet online.

I did some testing from a docker container (remember that they use a different LAN subnet) but it doesn’t connect, so it appears that whatever limit exists applies to any NAT addresses behind the same external IP.

I have to attend to professional matters and won’t be able to spend so much time on community1 as before. If it won’t work because maidsafe have deliberately broken it then that’s just the way it is. I’ll keep it running and look in from time to time.

EDIT: For the convenience of new nodes I have collected the recommended files here:

http://91.121.173.204/test/

wumpus · June 24, 2016, 11:25am

Nothing, not even an error message (built safe_vault from git, 0.9.0 tag, I could connect to 2016_06_14_test_network_4):

$ ./safe_vault 
INFO 11:23:49.791254310 [safe_vault safe_vault.rs:96] 

Running safe_vault v0.9.0
=========================
$

Possible reason could be that both hard coded contacts in the safe_vault config file are unreachable.

bluebird · June 24, 2016, 11:29am

The seed vault was down and I forgot to restart it. Sorry! Please try now.

wumpus · June 24, 2016, 11:41am

Yes, that did it, managed to connect now

bluebird · June 24, 2016, 11:45am

That’s interesting, since I see only my own client vault connected.

wumpus · June 24, 2016, 11:46am

Well I’m new to this, so I don’t know if it is actually doing something, I only know it gets further now than before:

$ ./safe_vault                                                                                                                                
INFO 11:30:30.999290950 [safe_vault safe_vault.rs:96] 

Running safe_vault v0.9.0
=========================
INFO 11:30:33.275527282 [routing::core core.rs:1032] Client(aafbd8..) Running listener.
INFO 11:30:33.338344824 [routing::core core.rs:1555] Client(aafbd8..) Sending GetNodeName request with: PublicId(name: aafbd8..). This can take a while.
INFO 11:30:33.522880842 [routing::core core.rs:1371] Client(126a23..) Added c9a5c0.. to routing table.
INFO 11:30:33.524675422 [routing::core core.rs:411]  --------------------------------------------------------- 
INFO 11:30:33.524706509 [routing::core core.rs:413] | Node(126a23..) PeerId(df1b..) - Routing Table size:   1 |
INFO 11:30:33.524723050 [routing::core core.rs:414]  --------------------------------------------------------- 

WARN 11:32:33.820138469 [routing::core core.rs:1903] Node(126a23..) Prepared connection info for PeerId(41b2..) as fd6313.., but already tried as fd6313...
WARN 11:35:09.220963120 [routing::core core.rs:683] Node(126a23..) Prepared connection info for PeerId(41b2..) as fd6313.., but already tried as fd6313...
WARN 11:43:09.212676349 [routing::core core.rs:683] Node(126a23..) Prepared connection info for PeerId(41b2..) as fd6313.., but already tried as fd6313...

bluebird · June 24, 2016, 11:50am

c9a5c0 is the hard-coded contact alright:

INFO 11:29:05.038652960 [routing::core core.rs:576] Node(c9a5c0..) - Started a new network as a seed node.

bluebird · June 24, 2016, 12:40pm

Something @dirvine mentions on another thread:

Re-enable bootstrap-cache.

I guess that might help for bootstrapping smaller networks such as this. So I’ll keep an eye out for that in the repo. My tentative recommendation going foward is: latest binary with the configs supplied above.

faddat · June 24, 2016, 9:05pm

The network-of-networks thing i shot. Anyone know if this is still operational?

faddat · June 24, 2016, 9:07pm

Mine crashes like this:

~/Downloads/vault$ ./safe_vault
INFO 04:06:15.302274766 [safe_vault safe_vault.rs:96] 

Running safe_vault v0.9.0
=========================
:~/Downloads/vault$ ./safe_vault
INFO 04:06:30.822480931 [safe_vault safe_vault.rs:96] 

Running safe_vault v0.9.0
=========================

All files are in the right folder, I think.

bluebird · June 24, 2016, 9:16pm

Do you mean is Testnet4 finished? The answer is yes: TEST network 4 - complete

This network, community1, is operational but in the sense that the two hard-coded contacts in the config are running (last I checked). But it is not fully functional because of the crippled nature of the test binaries - disabled cache, limitation of number of vaults on a LAN - which make it difficult to achieve a quorum. Without a quorum, newly stated vaults tend to die.

That means that, with a large expenditure of time I might find workarounds to these difficulties and have a fully functional network. But I don’t have that time at present. Things will get better, that’s all I can say for now.

There’s also the developer network (stable droplet network) described elsewhere on the forum, if you just want to run client software.

Blindsite2k · June 24, 2016, 10:26pm

My vault won’t even start.

Running safe_vault v0.9.0

[blindsite@localhost safe_vault-v0.9.0-linux-musl-x64]$ ./safe_vault
INFO 15:24:09.488869307 [safe_vault safe_vault.rs:96]

Running safe_vault v0.9.0

[blindsite@localhost safe_vault-v0.9.0-linux-musl-x64]$

faddat · June 25, 2016, 12:11am

I was talking about community1.

I’ve got the configs in place, but seems that the same thing that’s happening to me is happening to @blindsite2k.

Blindsite2k · June 25, 2016, 12:38am

Well at least I know it’s not just me. Now what do we do about it?

Topic		Replies	Views
"community1" Test Network is Alive, Join Us! Development test_network	152	9196	June 11, 2016
Community1 test network 18-hour run Development test_network	27	3372	July 15, 2016
Join the NEW Community Test Network (Running Now): "community1" Development	244	11039	May 21, 2016
Launch of a community safe network Community	426	15509	March 6, 2020
Dev Update & 2nd Test Network Release :safe: 8th March 2016 Updates	103	10650	March 20, 2016

"community1" Test Network Has Restarted, Join Us!

Important Addition:

Running safe_vault v0.9.0

Running safe_vault v0.9.0

Related topics