Also make sure you have/run latest version, i.e. v0.9.0 of SAFE CLI, you can do this with $ safe -V
, if you have an earlier version just update it with $ safe update
, it will then be fine to run the $ safe vault install
command.
Awesome! Sounds like on to a winner… Will test it soon!
Thanks Maidsafe devs & Safers for making this possible.
Keep it going super ants
@Michael_Hills Note that with macOS you need to add a ./
before safe
to execute it, so the equivalent of $ safe vault install
on macOS would be $ ./safe vault install
.
Same goes for all the other $ safe
commands - change them to $ ./safe
on macOS
and $ ./safe
for all flavours Linux too.
The Github page lists Auth and FFI, above the actual CLI releases at the bottom in assets, which surely are the page’s focus; so, unclear why it has Auth listed, where the CLI will install that. Tripped me to downloading unnecessary copy.
All works ok so far
This actually feels like a good things that it didn’t just jump into a full end user network because as you stated there is now time (with a somewhat more clear timeline) to really attack marketing and the exchange issues that persist.
Wonderful news! Big thanks to the ants and maid team for your continued work and dedication.
Excellent! Thanks for the clear explanations. Can’t wait to try it.
Great info thanks!
Hey, this is really something! Congratulations Maidsafe team and thanks a lot for your hard work!
I’m really interested in the nature of this challenge. What would be the upload time of a say single 5MB photo for now on your setup @Southside ? What parameters affect the memory consumption… file size, section size…? Is this more about uploading or also when downloading?
Another question, does Phantom work already on this release?
I’m also not a tech guy at all, but I’m sure they will release beta and beyond. The question for me is what the network will actually be capable of. I’m quite sure it will deliver the kind of privacy it promises, as well as open and secure access. Now I’m thinking that this memory use thing can be somewhat a problem, if the data traffic becomes slow beacause of it. Nevertheless I’m convinced that even slow network would prove highly useful when it has the aforementioned properties of privacy, access - and working cryptocurrency.
There is huge need for a way to have a data traffic that is not owned and used by anyone else than the actual end users. Many people value their own privacy, but at the moment I’m thinking more about states and such institutions. Think about the possibility of a global communication protocol, that no state or company has more access or control than any other. It would be good platform for those states and companies to develope collaboration and mutual trust.
I’d love to be able to tell you… after 6min 50secs it barfed…
willie@gagarin:~/.safe/vault$ ls -l ~/Downloads/09132.pdf
-rw-r–r-- 1 willie willie 5003571 Jul 4 2015 /home/willie/Downloads/09132.pdf
willie@gagarin:~/.safe/vault$ time safe files put ~/Downloads/09132.pdf
[2020-03-05T21:29:17Z ERROR safe] safe-cli error: [Error] NetDataError - Failed to PUT Sequenced Append Only Data: Error(CoreError(Request has timed out - CoreError::RequestTimeout))
real 6m0.504s
user 0m0.884s
sys 0m0.168s
It did NOT run out of memory, though, I had htop open and was keeping a very close eye on it.
@bochaco @StephenC do you want the logs for this?
I’ll try again and see if this is repeatable. Previously I was attempting to upload a large number of smaller files. I’ll write a wee script later tonight to loop through ~/Photos and upload each pic individually.
TLDR; elderly i5-2500k@3.3GHz 16GB RAM and swap - Ubuntu 18.04
willie@gagarin:~/.safe/vault$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core™ i5-2500K CPU @ 3.30GHz
stepping : 7
microcode : 0x2f
cpu MHz : 3292.523
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 6585.04
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
willie@gagarin:~/.safe/vault$ free
total used free shared buff/cache available
Mem: 16378512 9088160 6069468 151784 1220884 6838908
Swap: 14648316 2061056 12587260
I don’t remember now, but wasn’t this an issue with single vault as well, but just the client timing out with a large file? @lionel.faber do you remember exactly?
I should add I have logging set to DEBUG. Let me try again with it at INFO
DEBUG 2020-03-05T21:48:05.907369555+00:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parsec-0.6.0/src/parsec.rs:364] PublicId(name: 2a4d90..) received gossip request from PublicId(name: e3cd6e..)
DEBUG 2020-03-05T21:48:06.827469118+00:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parsec-0.6.0/src/parsec.rs:340] PublicId(name: 2a4d90..) creating gossip request for PublicId(name: e3cd6e..)
DEBUG 2020-03-05T21:48:07.462284843+00:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parsec-0.6.0/src/parsec.rs:340] PublicId(name: 2a4d90..) creating gossip request for PublicId(name: f9b5e4..)
DEBUG 2020-03-05T21:48:10.165565838+00:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parsec-0.6.0/src/parsec.rs:364] PublicId(name: 2a4d90..) received gossip request from PublicId(name: c82db0..)
DEBUG 2020-03-05T21:48:11.014446486+00:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parsec-0.6.0/src/parsec.rs:340] PublicId(name: 2a4d90..) creating gossip request for PublicId(name: f9b5e4..)
DEBUG 2020-03-05T21:48:11.729925918+00:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parsec-0.6.0/src/parsec.rs:340] PublicId(name: 2a4d90..) creating gossip request for PublicId(name: e3cd6e..)
I approached running baby-fleming and uploading data as a total newbie, following instructions only and trying not using any of my existing knowledge.
I’m very impressed how simple and fast it was to get up and running.
Running safe auth update
(I didn’t realise I didn’t have installed yet)
See error:
[2020-03-05T22:25:49Z ERROR safe] safe-cli error: [Error] AuthdClientError - Failed to execute authd from '/home/ian/.safe/authd/safe-authd': No such file or directory (os error 2)
This error is not as helpful as it could be. Maybe it could say ‘try running safe auth install’ or it might prompt ‘you don’t have safe auth installed, do you want to install it now? [Y/n]’
safe auth create-acc
Is it really worth shortening the word account
? It feels to me like making something needlessly less expressive. I’d prefer this command to be safe auth create-account
since that’s self-documenting. I know acc is not that hard to infer but let’s try to reduce mental load and cater to newcomers…?
Some performance stats
8 vaults running locally
Create a 50 MiB file: dd if=/dev/urandom of=/tmp/rand.dat bs=1M count=50
Upload
$ time safe files put /tmp/rand.dat
It failed after 6 minutes
[2020-03-05T22:38:18Z ERROR safe] safe-cli error: [Error] NetDataError - Failed to PUT Sequenced Append Only Data: Error(CoreError(Request has timed out - CoreError::RequestTimeout))
Maxed out my memory doing this (16 GB) and cpu (Intel i7-8565U CPU @ 1.80GHz 4 cores) but then strangely went to 50% cpu load about midway through the upload.
Only 3 of 8 vaults were running after the error showed. Might explain the cpu load changing.
Killed all vaults and started a new baby fleming network with 8 vaults.
Tried again with 3 MiB file
Ran a high cpu load (>90%) for about 15 seconds. A long period of 0% cpu usage until timeout error after 6m22s, so not sure what that was about but will be good to look into it later.
I’ll be doing some more detailed performance analysis in the future but I don’t have a lot of time just now. Really pleased to see others also probing this and will watch their results with pleasure!
I am seeing almost identical timout figures to you @mav.
Did you have the -y flag set for debug logging?
i will work my way down from 4MB till I get a file successfully put. Any success I have had has been with trivially small sites
No, but this was my newbie attempt. Later I will go full nerd on it.
I tend to use this environment variable for extreme logging:
$ RUST_LOG=trace ./safe_vault > /path/to/this/vault.log
Not sure if this will work with the safe-cli run-baby-fleming option but I will be doing vault start/stop manually anyhow.
I am using this wee script for now
it needs work but saves much typing
#/bin/bash
WD=/home/$USER/.safe/vault
cd $WD
safe vault killall
rm -rf baby-fleming-vaults
safe vault run-baby-fleming
safe networks add my-network
safe networks switch my-network
safe auth restart
safe auth status
safe auth create-acc --test-coins
safe auth login --self-auth
I’ll add a password config file when I can find the docs for its format - a warning to remind you you are about to blow away your existing vaults would help too…
Big thanks to @tobbetj and @Shane for providing some additional context.
And … a massive thanks and congratulations to the whole MaidSafe team for this milestone!
Thank you so much Maidsafe Team!!
A post was merged into an existing topic: Support Issues with Baby Fleming Version 1 (Vaults Phase 2a - single-section network)