Fleming Testnet v3 Release - * NOW OFFLINE - v4 RELEASED*

tail -f $HOME/.safe/node/local-node/sn_node.log

Yes that should be in the OP as well

IF - and its a big IF - I get time I will refresh the post I did a couple of days back where all the “start from scratch” instructions re in the one place Testnet - How to get started

6 Likes

Thanks @Southside

I think I’m in! no op from node duty (uncertain what that entails) but it says I’m storing chunks and storage space used. What is the directory to see the chunks being stored?

This is awesome!!!

4 Likes

from memory ~/.safe/node/local-node/chunks/immutable

furtle around in ~/.safe/node/ and it will be obvious

tree is your friend here :slight_smile:

image

7 Likes

wow this feels so much more responsive than V1…
WELL DONE GUYS!!
I’m still afraid I might have IGD problems with my router…I’ll keep an eye on the node log and see if I get killed when/if promoted to elder

6 Likes

Trying to upload a map with some pics. Nothing happens…When should I get a response? When every file is uploaded or per single file?

Safe-the-planet.png download success!

4 Likes

I updated this a little earlier as per here so hopefully was just your page needed refreshed - let me know if I missed it somewhere else though.

6 Likes

Getting a connection from your node to an other public node should be pretty easy (if there’s no firewall etc blocking it), the other way around through NATs is the hard part.

1 Like

I use a local firewall on my machine … I expect that SN wouldn’t like that, so I am using (successfully so far) “proxychains” to push all connections through Tor (which my firewall allows) … and amazingly seems to be working fine.

1 Like

Once the whole lot have uploaded - no feedback at the moment is a sign that it’s running.

Much UX improvement required here, we know. It’s on the to do list :slight_smile:

9 Likes

Created a couple of Keypairs and have been successfully sending SNT between them.

I tried sending some SNT to my Nodes Reward Public key but it failed is that to be expected?

1 Like

40MB for me:

$ du -ch --max-depth=1 .safe/node/root_dir/chunks/
40M     .safe/node/root_dir/chunks/immutable
40M     .safe/node/root_dir/chunks/
40M     total
2 Likes

It seems to be returning requested chunks too, which presumably are incoming, e.g.

[sn_node] INFO 2021-04-15T13:58:43.566779857+01:00 [src/node/handle.rs:27] Handling NodeDuty: ReadChunk
[sn_node] INFO 2021-04-15T13:58:43.566954768+01:00 [src/chunks/mod.rs:65] Checking used storage
[sn_node] INFO 2021-04-15T13:58:43.567027233+01:00 [src/chunk_store/mod.rs:149] Used space: 20376114
[sn_node] INFO 2021-04-15T13:58:43.567105134+01:00 [src/chunk_store/mod.rs:150] Total space: 2147483648
[sn_node] INFO 2021-04-15T13:58:43.567166226+01:00 [src/chunk_store/mod.rs:151] Used space ratio: 0.009488367475569248
[sn_node] INFO 2021-04-15T13:58:43.567237251+01:00 [src/node/handle.rs:27] Handling NodeDuty: Send [ msg: OutgoingMsg { msg: QueryResponse { response: QueryResponse::GetBlob(Success), id: MessageId(dc88ab..), correlation_id: MessageId(f3e8c9..), target_section_pk: None }, dst: EndUser(Client { public_key: PublicKey::Ed25519(bf65070bbe2426d4aace6144672eb1be622d70584172df459e576fbb947d4e4d), socket_id: 4d1c91.. }), section_source: false, aggregation: None } ]
1 Like

YOu did Stephen, thank you - I just needed to refresh the page - sorry

1 Like

Node fired up. Chunks coming in. Wooooo :tada: Love it. Nice work @maidsafe !!

17 Likes

safe wallet balance safe://hyryyyydicrwuyrta8ari4xubsy1w71q6a7rj6z1d4omxc4yrd5o4yb7i6c
Error: ContentError: Failed to read balances from Wallet: NetDataError: Failed to get Sequenced Map. ErrorMessage(NoSuchData)

Also unable to use XorURL to check balance. Works ok if i use the secret key though

1 Like

That one is already in the OP - see the “Where are my node logs?” section under “Further Information”, and also mentioned a few paragraphs above that where we explain that nodes now retry automatically :sweat_smile:

2 Likes

Sorry I admittedly skipped some of that in my rush to start a node before rushing into work @StephenC . I got a node going and chunks storing in record time only a few minutes! So you guys are doing great! My bad

3 Likes

Is anyone else experiencing slow cats? I’m not getting any errors, but it seems to be taking a long time.

e.g. this has been going for about 45m (so far - still running):

safe cat safe://hygoygyjm9prgk48q9eoo8zc53bck97c9faicgnkxz4ezm3af4aotzfa91o > tmp/newlazydog.jpg

this about 30m (so far - still running):

safe cat safe://hyryyyymmy7wefy4qn5fjiuea4wwkdbg5j8ibxqiqmi8hi5bij4pte56ppa > 1.flac

this about 15m (so far - still running):

safe cat safe://hygoygyenxp3e516x1uktohmzxd3w8ubcnr9rhcd97xrjfsf4pztn5gbynw > Toivo_through_bottle.jpg

Creating an NRS map is also taking a long time (about 10m so far).

I’m on Ubuntu and my node seems to be running fine. Bandwidth doesn’t seem too contended either and I can see chunk reads and writes coming in fine.

EDIT: Note, I read the genesis image fine (in about 20s). I just tried it again and still fine.

3 Likes

Tried to put a file with 500MB random data on OS X.

safe files put safetestdata
[qp2p::connections] ERROR 2021-04-15T14:46:08.040852000 [/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.8/src/connections.rs:234] Failed reading from a uni-stream for peer 178.62.122.173:58245 with error: Failed to read expected number of message bytes: connection closed: the endpoint encountered an internal error and cannot continue with the connection: endpoint driver future was dropped
[qp2p::connections] ERROR 2021-04-15T14:46:08.042453000 [/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.8/src/connections.rs:234] Failed reading from a uni-stream for peer 138.68.146.170:32859 with error: Failed to read expected number of message bytes: connection closed: the endpoint encountered an internal error and cannot continue with the connection: endpoint driver future was dropped
[qp2p::connections] ERROR 2021-04-15T14:46:08.080362000 [/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.8/src/connections.rs:234] Failed reading from a uni-stream for peer 165.227.229.57:45221 with error: Failed to read expected number of message bytes: connection closed: the endpoint encountered an internal error and cannot continue with the connection: endpoint driver future was dropped
[qp2p::connections] ERROR 2021-04-15T14:46:08.104178000 [/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.8/src/connections.rs:234] Failed reading from a uni-stream for peer 165.227.225.237:60110 with error: Failed to read expected number of message bytes: connection closed: the endpoint encountered an internal error and cannot continue with the connection: endpoint driver future was dropped
[qp2p::connections] ERROR 2021-04-15T14:46:08.145399000 [/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.8/src/connections.rs:234] Failed reading from a uni-stream for peer 165.227.229.148:47735 with error: Failed to read expected number of message bytes: connection closed: the endpoint encountered an internal error and cannot continue with the connection: endpoint driver future was dropped
[qp2p::connections] ERROR 2021-04-15T14:46:08.230220000 [/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.8/src/connections.rs:234] Failed reading from a uni-stream for peer 165.227.229.55:32936 with error: Failed to read expected number of message bytes: connection closed: the endpoint encountered an internal error and cannot continue with the connection: endpoint driver future was dropped