MoreStabilityNet [19/07/23 Testnet] [Offline]

[stout77]

A few files for people to check downloads;

Storing file 'samfender.Aye.mp3' of 2990637 bytes (7 chunk/s)..
Successfully stored 'samfender.Aye.mp3' to 0f596b506bc4def921a54ea32c19f61c041cdb732a3f39c48ea817d7bd9ae329
Storing file 'james.sometimes.mp3' of 3852051 bytes (9 chunk/s)..Successfully stored 'james.sometimes.mp3' to 59d264618dd9d75173a79d0eea896e4f97df5fa24e2724104ce6c4d07d3f1053
Storing file 'james.protectme.mp3' of 4180985 bytes (10 chunk/s)..
Successfully stored 'james.protectme.mp3' to 87883ed0c9009475cdcd2bc12189570380d45740b216bf705583fb4b8fa7a40b
Storing file 'james.whatsitallabout.mp3' of 7252985 bytes (16 chunk/s)..
Successfully stored 'james.whatsitallabout.mp3' to 8c4f28add381e8958682345dc9076a4367a0869e64fd6768166160037a7c75f1
Storing file 'Nas&Damian Marley .Patience.mp3' of 5525142 bytes (12 chunk/s)..
Successfully stored 'Nas&Damian Marley .Patience.mp3' to a6cc172526eda9167c77b34c3b650362a1f4ee16f32f0f8d657fe0412a95381c
Storing file 'james.gettingawaywithit.mp3' of 4242007 bytes (10 chunk/s)..
Successfully stored 'james.gettingawaywithit.mp3' to bfa8481e7e5a2c7219e1021b1a8d4b41d840a828a1ae099975d558ffefff36a2
Storing file 'james.waltzingalong.mp3' of 3458752 bytes (8 chunk/s)..
Successfully stored 'james.waltzingalong.mp3' to e473af2f4f5e58506c3c6ed3015825f68d7558e1a18ec33c20360098a04fb530
Storing file 'james.walklikeyou.mp3' of 6819562 bytes (15 chunk/s)..
Successfully stored 'james.walklikeyou.mp3' to f3a366c66a180c8854c00f33bc58bc654585c7db4232598f541cdfe119b0ab7a
Storing file 'pinkfloyd.oneofthesedays.mp3' of 5692326 bytes (13
chunk/s)..
Successfully stored 'pinkfloyd.oneofthesedays.mp3' to f8945bb0568bcad5ca0b0fcd2049bf94cd42248d514a8e2cc6acab634889da1c

These are the current stats for about 20 nodes running on
Shape: VM.Standard.A1.Flex
OCPU count: 4
Network bandwidth (Gbps): 4
Memory (GB): 24

Pretty…pretty…pretty good!

[joshuef]

@dirvine

Not quite yet, but it’s certainly an issue we see and something we need for launch. Just another ball in the air, but for sure it will be done. Sooner the better I think as folk do get mixed up and reasonable they do at this stage.

Actually the protocols are versioned by the crate versions at the moment. (eg: https://github.com/maidsafe/safe_network/blob/main/sn_networking/src/lib.rs#L275), though I’m not sure how strictly libp2p handles this it is required when setting up the protocols, so I’d imagine there’s some incompatability with breaking changes already. But that’s not been tested thoroughly as yet (maybe @bzee you know more there?)

[joshuef]

We update on stability: We’ve lost a good few nodes still. Perhaps a bit less than last time, but too soon to tell really.

We’ll keep rolling here and see how other bits come along

[JPL]

My two nodes are chugging along with very low mem and CPU. Very small sample of course, and I’m purposefully not overloading them, but it seems to be an improvement. Chunk distribution is uneven though, 144 versus 1120.

[Southside]

Ive been out of action for the past 36hrs
Feeling a bit better now.
Should I go ahead and put up a couple of AWS nodes?

[bzee]

@joshuef

But that’s not been tested thoroughly as yet (maybe @bzee you know more there?)

I’m afraid I also don’t know for sure. It’s a good thing to look at soon and perhaps just straight block any peer running an older version (major/minor).

[Profess]

I don’t know if it makes any difference, but when I tried to upload a photo called “road to freedom”, an error occurred.

After adding underscores to the name, the file saved successfully.

[peca]

You need to tell the computer those spaces are part of the name and not separating different commands. It is telling you in the error message.

You can use:
safe files upload ".\Downloads\road to freedom.jpg"
or this should also work
safe files upload .\Downloads\"road to freedom.jpg"

[Profess]

Thank you for the explanation, valuable knowledge. Probably best to use underlining.

[happybeing]

Hyphens are easier-to-type.

[Profess]

@maidsafe

Running a Node

You can participate in the testnet by running your own node. At the moment, you may not be successful if you’re running the node from your home machine. This is a situation we are working on. If you run from a cloud provider like Digital Ocean or AWS, you should be able to participate.

You can run the node process like so:

# Linux/macOS
SN_LOG=all safenode

# Windows
$env:SN_LOG=all; safenode

When I tried to create a node, a message like the one in the screenshot appeared - a similar message appeared in the previous test, in the command that starts the Safeup program - is this an error?

But then I was able to run the node on my home computer and, if I understand correctly, it was able to connect to 38 nodes.

However, at the end of the day, the NAT status has been set to private, I understand that this is under control?

[JPL]

This is because you are behind a router at home or on a network, meaning that nodes can’t connect directly to you. You can try port forwarding to get around this, or use a cloud node. This is a known issue and Maidsafe are waiting for NAT hole-punching (getting around the router to connect peer-to-peer) to be supported by libp2p.

@maidsafe

Nodes still have to be run from the cloud until libp2p has better QUIC support, but clients can run from anywhere.

[Southside]

I got the same from an AWS instance I just started.
All looked fine, it grabbed 18MB of chunks and then decided it was behind a NAT and refused to play anymore

ubuntu@ip-172-31-6-177:~/.local/share/safe/node$ du -h
18M	./12D3KooWHcpKaJ8pNhhzTq6zFp7TPb9L8QwsR8EZUz1JD6n6peKC/record_store
18M	./12D3KooWHcpKaJ8pNhhzTq6zFp7TPb9L8QwsR8EZUz1JD6n6peKC
18M	.

*[2023-07-20T17:58:39.863664Z TRACE sn_node::api] Handling request: Query(GetReplicatedData { requester: NetworkAddress::PeerId( - None - Key { preimage: [0, 36, 8, 1, 18, 32, 56, 238, 173, 97, 140, 28, 255, 52, 124, 219, 48, 248, 1, 86, 226, 221, 32, 103, 125, 116, 28, 67, 27, 180, 71, 85, 241, 133, 99, 51, 78, 118], bytes: KeyBytes([143, 205, 155, 137, 78, 51, 25, 234, 126, 176, 54, 221, 152, 87, 154, 59, 163, 131, 137, 171, 215, 186, 189, 202, 134, 231, 47, 14, 74, 77, 161, 68]) }), address: NetworkAddress::RecordKey( - Some(Key(b"\xe5\xa3\xe6\"\xa5\x8b\x0e\x06\xd4G\x16\xdfY\xf07k\xeaI\n\xf9>\x85\xbe\xd6h\xce\xc1\xfac\n>\xd3")) - Key { preimage: [229, 163, 230, 34, 165, 139, 14, 6, 212, 71, 22, 223, 89, 240, 55, 107, 234, 73, 10, 249, 62, 133, 190, 214, 104, 206, 193, 250, 99, 10, 62, 211], bytes: KeyBytes([129, 225, 249, 130, 32, 50, 47, 90, 21, 187, 101, 238, 93, 81, 45, 138, 53, 149, 4, 66, 251, 168, 134, 241, 151, 247, 190, 159, 223, 253, 18, 236]) }) })*
*[2023-07-20T17:58:39.863795Z TRACE sn_node::api] Got GetReplicatedData query for NetworkAddress::RecordKey( - Some(Key(b"\xe5\xa3\xe6\"\xa5\x8b\x0e\x06\xd4G\x16\xdfY\xf07k\xeaI\n\xf9>\x85\xbe\xd6h\xce\xc1\xfac\n>\xd3")) - Key { preimage: [229, 163, 230, 34, 165, 139, 14, 6, 212, 71, 22, 223, 89, 240, 55, 107, 234, 73, 10, 249, 62, 133, 190, 214, 104, 206, 193, 250, 99, 10, 62, 211], bytes: KeyBytes([129, 225, 249, 130, 32, 50, 47, 90, 21, 187, 101, 238, 93, 81, 45, 138, 53, 149, 4, 66, 251, 168, 134, 241, 151, 247, 190, 159, 223, 253, 18, 236]) })*
*[2023-07-20T17:58:39.863914Z TRACE sn_networking::record_store] GET request for Record key: Key(b"\xe5\xa3\xe6\"\xa5\x8b\x0e\x06\xd4G\x16\xdfY\xf07k\xeaI\n\xf9>\x85\xbe\xd6h\xce\xc1\xfac\n>\xd3")*
*[2023-07-20T17:58:39.864313Z TRACE sn_networking::record_store] Retrieved record from disk! filename: e5a3e622a58b0e06d44716df59f0376bea490af93e85bed668cec1fa630a3ed3*
*[2023-07-20T17:58:39.864556Z TRACE sn_networking::event] Query task QueryId(196) returned with record Key(b"\xe5\xa3\xe6\"\xa5\x8b\x0e\x06\xd4G\x16\xdfY\xf07k\xeaI\n\xf9>\x85\xbe\xd6h\xce\xc1\xfac\n>\xd3") from peer None, QueryStats { requests: 0, success: 0, failure: 0, start: None, end: None } - ProgressStep { count: 1, last: false }*
*[2023-07-20T17:58:39.868045Z TRACE sn_node::get_validation] Replicating chunk with address ChunkAddress(e5a3e6(11100101)..)*
*[2023-07-20T17:58:39.869448Z TRACE sn_networking::msg] ResponseSent for request_id: RequestId(20832) and peer: PeerId("12D3KooWSebWcv4Birvfi9udSersugRdfhZWysC4EcEoGYGd4NoL")*
*[2023-07-20T17:58:39.869569Z TRACE sn_networking::msg] ResponseSent for request_id: RequestId(20834) and peer: PeerId("12D3KooWSebWcv4Birvfi9udSersugRdfhZWysC4EcEoGYGd4NoL")*
*[2023-07-20T17:58:39.879037Z TRACE sn_networking::msg] ResponseSent for request_id: RequestId(21012) and peer: PeerId("12D3KooWDec61qX9bSWwLJhZ3t72WhCCZTYbhRk6hUvf2Ycwi5ED")*
*[2023-07-20T17:58:39.892240Z TRACE sn_networking::event] Dialing Some(PeerId("12D3KooWDQTmENr3G4yi595h6PNfZrpzyYo5WhsXnmM7oDrWodyb")) on ConnectionId(471)*
*[2023-07-20T17:58:39.892689Z TRACE sn_networking::event] Dialing Some(PeerId("12D3KooWDQTmENr3G4yi595h6PNfZrpzyYo5WhsXnmM7oDrWodyb")) on ConnectionId(472)*
*[2023-07-20T17:58:39.892879Z TRACE sn_networking::event] Dialing Some(PeerId("12D3KooWMXtQmTpZB3Fv1Ar9ASaGBP68RroCb79iDxFWBRqCQCmK")) on ConnectionId(473)*
*[2023-07-20T17:58:39.893421Z TRACE sn_networking::event] Dialing Some(PeerId("12D3KooWDQTmENr3G4yi595h6PNfZrpzyYo5WhsXnmM7oDrWodyb")) on ConnectionId(474)*
*[2023-07-20T17:58:39.893671Z TRACE sn_networking::event] Dialing Some(PeerId("12D3KooWDQTmENr3G4yi595h6PNfZrpzyYo5WhsXnmM7oDrWodyb")) on ConnectionId(475)*
*[2023-07-20T17:58:39.893832Z TRACE sn_networking::event] Dialing Some(PeerId("12D3KooWBuD7KSuV4UgzBW7iodyG2BCBqwRXKpocayUHVvT7Lq6X")) on ConnectionId(476)*
*[2023-07-20T17:58:39.898664Z TRACE sn_networking::event] Dialing Some(PeerId("12D3KooWBuD7KSuV4UgzBW7iodyG2BCBqwRXKpocayUHVvT7Lq6X")) on ConnectionId(477)*
*Error: We have been determined to be behind a NAT. This means we are not reachable externally by other nodes. In the future, the network will implement relays that allow us to still join the network.*

*Location:*
    sn_node/src/bin/safenode/main.rs:318:36

Again this is on AWS. I will try from home with port-forwarding later.

[chriso]

Glad to see you upgraded to Windows Terminal!

Regarding your first screenshot with the error message, unfortunately you haven’t included the crucial piece of information, which is the command you used that caused the error. Based on what I can see, I’m guessing you may have made a typo when trying to set the SN_LOG environment variable.

I wouldn’t be able to comment on the safeup error either unless you posted the command along with the error message.

Also, yes, in most shells, if your path has spaces in it, you either need to enclose the path in quotes, or some shells support escaping spaces using \, but it’s generally just easier to put the whole path inside quotes.

[Southside]

@chriso

but it’s generally just easier to

not put bloody spaces in file names </grumpy

[chriso]

It depends…

For like source code, system files, all that kind of stuff, I totally agree - no spaces! Prime example of something horrible there is, e.g., “Program Files” on Windows . I’m a fan of keeping all that stuff lowercase too.

However, if you’re trying to describe something like say, a document hierarchy, or something that lends itself more to human readability, then spaces there are fine. I wouldn’t want a bunch of photo galleries named with underscores or whatever in them.

[happybeing]

My cloud node seens fine. Compared to last time it appears to be increasing memory usage much more slowly, leveling of at around 50MB but is also receiving chunks at a lower rate so not easy to compare.

One definite change is from few errors last testnet to many more at a fairly regular pace. I haven’t checked to see what they are but it is very noticeable looking at the timeline in vdash.

[Profess]

@chriso

Glad to see you upgraded to Windows Terminal!

Well, a must This is a much better solution, thank you.

@chriso

Regarding your first screenshot with the error message, unfortunately you haven’t included the crucial piece of information, which is the command you used that caused the error. Based on what I can see, I’m guessing you may have made a typo when trying to set the SN_LOG environment variable.

I wouldn’t be able to comment on the safeup error either unless you posted the command along with the error message.

I’ve just realised that when I took the screenshot, I moved the screen up and took a screen of the wrong thing.

I have restarted the node, at the moment it looks like this (previously I also typed the command as it is now)

[JPL]

You need to do this first to give your node something to connect to

$env:SAFE_PEERS = "/ip4/176.58.124.107/tcp/44439/p2p/12D3KooWEwMPj64C1MXEKaCYHGgtMApNzzvoynfprLJRLfgfGo7G"

Then if it still fails maybe try with quotes around the all (I see there are various permutations in the OP)

$env:SN_LOG="all"; safenode

[chriso]

Yeah, it will be the missing quotes.

The template is incorrect. One day I will be able to write one of these without making a bloody mistake!

Also, we should actually amend it to this (which I’ve done in the template):

$env:SN_LOG = "all"; safenode

Note the spaces around the equals sign. That is the proper style in Powershell, as far as I’m aware. So we should use that. It will also keep it consistent with the other Powershell statements that use the space.

For Bash, it’s actually required to not use the spaces!