No. I saw no info on where the log dir was.
3 Likes
I did this and checked wallet balance after and I did not pay twice. But curious why it did the whole upload and download (verify) a second time when it knew it was already uploaded (as payment for those chunks had already been made)? What am I misunderstanding about the process?
4 Likes
17 of the little darlings now.
But a few errors uploading Southside’s Stones collection, eg:
Storing file '09 Mother's Little Helper.m4a' of 2456976 bytes (6 chunk/s)..
Did not store all chunks of file '09 Mother's Little Helper.m4a' to all nodes in the close group: Network Error Could not retrieve the record after storing it: Key(b"\xf4\x95xX~S\x8b\x84t\xd9\xc3.\xd9y\xebc\xbe\xfc\x88\xe7\xe7\xf9\x8d\xc8+\xde\xa86\xd1\xf9\xc6\xa9").
6 Likes
Thank you for the really easy instructions.
I’m running a VM on a home proxmox server. No port forwarding.
Receiving payment works well.
safe files download bbb915a0756c69ee6d2af0eaea69b54b7a110cc6a5f3891801ad162650c879c9
I also managed to download my file.
I’ve included the output from --help because I am really happy with the command line tool,
and its detailed help.
This was a painless, pleasant testnet experience. No waiting around to wait to be connected, this was all instant. None of that ancient blockchain technology sync waiting time.
Receiving payment, spending payment to upload a file, and a successful file download.
This is very exciting.
Thank you Maidsafe.
17 Likes
My output:
$ SN_LOG=all safe --log-output-dest data-dir files upload hello.txt
Logging to directory: “/root/.local/share/safe/client/logs”
Using SN_LOG=all
Built with git version: 1262368 / main / 1262368
Instantiating a SAFE client…
5 Likes
ahh!, you are right, I just missed it. Tired.
2 Likes
How long did this take @JPL, I have 3 with zero and need to get moving, got up at 4.30am to get a early start on my day but now I am sitting at my pc looking for records instead. 
6 Likes
30 mins to an hour I guess. Not more than an hour.
4 Likes
Ahhh ok. Thanks!
3 Likes
You cannot be left alone for a moment! 
What a test this will be! 
When connecting from your home computer, will the NAT status still be set to private?
3 Likes
Should be, yep!
A note on current status:
We’ve thus far lost 0 nodes. Which is a great place to be again (the last few testnets had dropped nodes before I even got the post up!). Let’s see how it holds up over a few days, but that’s certainly a better start.
Here’s the stats from a randomly chosen “newer” node (ie, one of the last 50 i put up, that would have less chunks than those I started + tested with):
Node PeerId PID Memory (MB) CPU (%) Record Count
12D3KooWQKLwiHme3Ux4pFJBdf6C1bVhLA7uVWKU83XuykyHbZkY 8964 36.543 13.3 48
12D3KooWCwMnLSWpTobV2vod6vXid2okRtugYnjn3tjpLwVN3aDB 9101 90.8477 0.0 83
12D3KooWPPR5JWkJLtoTC1G7N13FWTwGoM3mQaPypE5cPyrtfKWD 9012 54.0273 20.0 122
12D3KooWAsdgfnDxTdkFtvVkC9hrfnGVTBygkhfbfEtN5VQwr6sc 8924 64.9766 0.0 67
12D3KooWKkLSJK1xspMj6hrTJHPUSC1rV23sNdWX7Kgix6nTGde1 9022 68.625 0.0 52
12D3KooWLcuuA81YT6AtEm6GAEZxpqPFDXYRePQ3xq85cvwGWR83 9032 42.4023 0.0 64
12D3KooWKGw5NeVseWrMoht5hJCiUu2aWeX3pQAeueTGbVKQq6Dq 9052 62.1875 0.0 127
12D3KooWJ37QqTvtqSrMUQfGMorbUE8fRLqZWjjkGx5ZaQBLNvah 8983 62.3125 0.0 106
12D3KooWHbXmwAFMK6gf5u7rtKberSiyAoRPNEjCQULRSHYYEHPB 8974 41.0664 0.0 78
12D3KooWCXvZUWcuMX2439TPDbaM7XEvR3J1tTLmiiziPTkx4Pnn 8934 83.5156 0.0 88
12D3KooWDNCQFwQ67ufzHX92dFXeP8DDka8M9BspuXTo9msPVgqP 9081 129.477 0.0 50
12D3KooWBS9kvRWCKCWVost285yHsEwbvtfkizqmB1Buso8YKcBv 9042 42.1016 0.0 44
12D3KooWNux7VhJQ9f1tW4wt3AyPiJmiALrQWXL7Ks9jZ1qf81MC 9062 37.5781 0.0 37
12D3KooWLR7sWPpqLhCTtaqyB6ikMU6bNhRYKZRoxgtzyJjWoPKs 8944 96.7695 0.0 107
12D3KooWBxxUB5RYEi9bHFQcEXuBJ1MWs86N8YUVBiqGmgK5kP66 9091 40.1133 0.0 27
12D3KooWHG1xArAhE4GTKzsHUi1oUFvHxF3mXKU9MdnDA8KqsR9S 9111 43.9844 0.0 84
12D3KooWJQYpM5pMJiLhpJmAtFUYNcYEZ93Qjx9e7n7GSdxigzwD 9071 76.9297 25.0 75
12D3KooWSNqR1sdCmZ8nt2B9eePWXPRXn97r3jHK63e4BLznAoDT 8954 41.9766 0.0 41
12D3KooWCzLDtNS6pXVQtfpN4dq8zG2wSPduoKLH8f6mnDb68W5P 8992 87.8047 0.0 164
12D3KooWGPyCuLkZMBVTcRTv59LTDmW5K1rACtxJ4qV3fXxGBYqa 9002 76.082 0.0 109
19 Likes
You guys are getting closer… Can you feel it? That gut feeling there?
13 Likes
No but happy to see first time? Payment testing, but still skeptical or in better words: still expect long time to finish
2 Likes
All we can do is see progress and individually all make conclusions on how long and are we there yet.
In my mind and I have said this in many meetings recently (board, foundation etc.) I believe we no longer have a technical issue, it’s all positioning, messaging, partnerships and economics. I think those are easily solved, but the positioning and messaging are gonna be vital, but we are well through a project to establish the route there.
35 Likes
Its getting closer!
10 Likes
Hmm, upload fail
root@localhost:~# SN_LOG=all safe --log-output-dest data-dir files upload logsjune15.tar.gz
Logging to directory: "/root/.local/share/safe/client/logs"
Using SN_LOG=all
Built with git version: 1262368 / main / 1262368
Instantiating a SAFE client...
⠐ 0/20 initial peers found. The client still does not know enough network nodes.
🔗 Connected to the Network Preparing (chunking) files at 'logsjune15.tar.gz'...
memory allocation of 2132480841 bytes failed
Aborted (core dumped)
EDIT chunking/encryption too much for a small (1G) vm maybe?
2 Likes
@joshuef is this one of the multiple nodes per droplet, as in a certain risk of early loss despite the good start?
I have a couple of scripts that rely on a hard-coded peer to automate periodic uploads/downloads, so a loss will mess me up.
I can probably loop some peers or run a node of my own with enough resources to reduce the risk of loss.
I see some benefit in Maidsafe having one such stable node to help prevent the need to update the OP after a loss.
Either way, I am happy to do whatever I need for my stuff to work but if the posted peer has reasonable chance of staying up I would rather not bother.
6 Likes
yeh, 20 nodes per droplet.
the first node is solo on the same machine as the faucet. Won’t get much more stable than that one: /ip4/178.62.79.112/tcp/46803/p2p/12D3KooWJnPhTVEnv7rx9ZCZZZRgTxrts33m33sKWfDdFH4jBcGo
(Although i just checked again and we’ve still got all nodes alive, so so far so good!)
9 Likes
What do you mean?
No bugs? No critical bugs? No possibility for critical bugs?
1 Like
I have a cloud node running 
and beginning to PUT/GET (one of each so far).
Laptop and cloud got tokens from fawcet
Laptop uploading
Cloud uploading
EDIT: earlier issue was wrong SAFE_PEERS value! 
9 Likes