What is the contents of your shared-section config file?
Did it even try to look for the Digital Ocean droplets?
Did it fall back to LAN because they are (presumably) unavailable right now?
What is the contents of your shared-section config file?
Did it even try to look for the Digital Ocean droplets?
Did it fall back to LAN because they are (presumably) unavailable right now?
$ cat ~/.config/safe_vault/vault_connection_info.config
"167.172.55.70:12000"
This path also has hyphen underscore inconsistency.
Iām sure thereās a good reason for using both ~/.safe/
and ~/.config/safe_vault/
but it seems a bit spammy, might be worth trying to consolidate into a single directory.
safe networks
has headings Network Name
and Connection info location
(which is a remote https location), might be good to also have a third column Connection info file
which shows the local path to the file�
Am I getting confused here? I see the top two as my local vaults and the bottom two as the remote āproper Maidsafeā vaults
EDIT: Ah I think I understand, the location on your machine where that remote path is stored?
EDIT2: I am trying very hard not to let my OCD get triggered by this underscore inconsistencyā¦
I think the above is telling us that the test-net is no longer accepting vaults, Iām getting the same errors. As mentioned, after the bug is fixed, they will restart, which hopefully fixes this for me too.
Yes, I had this too. The error says files are missing, rather than saying it isnāt installed (and suggesting how to install it and/or installing it).
Is it a good idea to modify the title of this topic and add the status of the network to it?
@maidsafe @moderators
Thank you for the proposal friend, I updete it
Basic question for @maidsafe: What is the version of source code of the vaults running in your DigitalOcean droplets?
I naively thought it was version 0.24.0 because it was delivered 3 days ago, just before the network was launched.
But the problem is that I find some behaviors odd when I build it from source and test it in a local network:
Genesis vault alone becomes an elder and works perfectly
Second vault inserts itself correctly and becomes an elder, but it doesnāt receive any chunks from the first vault
Third vault doesnāt even become an elder
One possible explanation could be that you donāt need a perfectly working network to test for IGD and not all nodes need to store the chunks, but then how were you able to create 7 elders?
The startup process works best by adding nodes until there are some adults. So donāt have a section with data on it until you have 7 elders at least. Well in terms of startign a network proper. @lionel.faber will be the guy for this one though he was beasting away with a few changes at the last minute and was all debug on Friday.
Thanks.
About the vault not becoming elder I think I had a problem of isolation between the processes executed in the same machine (probably config files overwritten by the second vault that prevented the third vault to become elder). Not sure exactly what happened. But if I use multipass to create independent VMs then everything works properly.
Like you said, I have to start all 7 vaults before storing any data, but I suppose this will be corrected later.
Yes, definitely. Sync between Elders is a feature in the pipeline.
It should be sufficient to pass the --root-dir
argument to the vault so that each vaultās data is separated from each other. If you are running all the vaults locally then --local
would be helpful as well. It will use 127.0.0.1
as the IP and disable things like IGD.
Can any of the devs expand on this? Why do we have two locations for config info or is it just a wee detail that needs tidied eventually?
The āConnection info locationā is where to read the contact info from when setting/switching to one of the configured networks, either from a local file or from a remote http/s location. When you decide to switch to any of your configured networks, the content obtained from the file at āConnection info locationā is copied onto ~/.config/safe_vault/vault_connection_info.config
, which is where any client app would read the info from to finally connect to the network.
Currently, I donāt think we have any config within ~/.safe/
tree. The other locations under ~/.config
and ~/.local
are due to apps following the XDG spec: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
New version expected tomorrow or still working on the issues highlighted by this test?
Possibly. The issues highlighted are prob fixed now and will defo be as we impl the crdt/at2 and dkg proper. So a mix of fix that issue and also get more of the correct code in place. We will see though, but I doubt it as we do a few tests among the team and have not today.
Hi Maidsafe and greetings to all the community here,
This is great news about the test vault, congratulations.
I havenāt posted for a while so excuse me if Iām behind the times.
I wanted to ask if I can run this test net via Windows. I donāt think so, right? I am planning to change to Linux, so Iām guessing once Iāve done that (Debian) and got used to it, will I be able to participate and help Maidsafe more in its tests?
Is there anything besides this test net that I might be able to do to help out with a standard Windows 10 laptop? I do remember a long time go downloading the peruse browser and authenticator and other things, but I deleted all that eventually because I know it was a test phase and Maidsafe moved on.
Reading through this thread I guess I have a lot to learn because I saw ābootstrappingā and I thought, āhmmmā thatās where I get lost.
However this doesnāt diminish good intentions, so do let me know anyone where participation can be of use, and if not at the moment, assure me that there will be a chance later.
I also have a separate question; Iāll make a topic for that now.
Thanks everyone!
I wanted to ask if I can run this test net via Windows. I donāt think so, right? I am planning to change to Linux, so Iām guessing once Iāve done that (Debian) and got used to it, will I be able to participate and help Maidsafe more in its tests?
You can use Windows, Linux or Mac, all the steps for participating in the testnets are done with the SAFE CLI, if you havenāt read it yet Iād recommend you take a look at the CLI User Guide to get a glimpse and a step by step guide of all the things possible with these testnets.
I should probably add that once I have Linux, it should be easy just to follow the instructions given?!
Aha! Great to know, quick to answer and simple. Thanks. Iāll check out that CLI Guide and see what I can do to get it to work!
Not sure from your replies if you realized that there isnāt an active testnet right now. You can however still run your own ābabyā network locally, and there will be more public testnets to come soonā¢