NatNet [May 26 Testnet 2023] [Offline]

Development Releases
21

I removed everything old now, downloaded again, and I get:

[2023-05-26T12:58:27.863706Z INFO safenode] 
Running safenode v0.1.0
=======================
[2023-05-26T12:58:27.866968Z INFO safenode] Starting node ...
[2023-05-26T12:58:27.869107Z INFO safenode::network] Node (PID: 23265) with PeerId: 12D3KooWBjvLnyGSmR2y2efY4uhgvLCmDfUwhLh4JvkiNP1kJQVM
[2023-05-26T12:58:27.869125Z INFO safenode::network] PeerId converted to XorName: 12D3KooWBjvLnyGSmR2y2efY4uhgvLCmDfUwhLh4JvkiNP1kJQVM - 600920(01100000)..
[2023-05-26T12:58:27.878250Z DEBUG safenode::domain::fees::spend_queue] Starting fee: current_fee 4000.
[2023-05-26T12:58:27.878265Z DEBUG safenode::domain::fees::spend_queue] stats: highest 10494, high 8000, medium_high 6333, avg 4667, medium_low 3333, low 2000, lowest 1662, std_dev 2494, len 3, queue [8000, 4000, 2000]
[2023-05-26T12:58:27.880239Z INFO safenode::network::event] Local node is listening on "/ip4/127.0.0.1/udp/40193/quic-v1/p2p/12D3KooWBjvLnyGSmR2y2efY4uhgvLCmDfUwhLh4JvkiNP1kJQVM"
[2023-05-26T12:58:27.880295Z INFO safenode::network::event] Local node is listening on "/ip4/192.168.1.104/udp/40193/quic-v1/p2p/12D3KooWBjvLnyGSmR2y2efY4uhgvLCmDfUwhLh4JvkiNP1kJQVM"
[2023-05-26T13:29:14.152333Z INFO safenode] 
Running safenode v0.1.0
=======================
[2023-05-26T13:29:14.156099Z INFO safenode] Starting node ...
[2023-05-26T13:29:14.158327Z INFO safenode::network] Node (PID: 12155) with PeerId: 12D3KooWNegZeQkXZs9kQChePpwna7XVt8MeYbRF33fM2zcdQ3J3
[2023-05-26T13:29:14.158345Z INFO safenode::network] PeerId converted to XorName: 12D3KooWNegZeQkXZs9kQChePpwna7XVt8MeYbRF33fM2zcdQ3J3 - 5c2e02(01011100)..
[2023-05-26T13:29:14.167447Z DEBUG safenode::domain::fees::spend_queue] Starting fee: current_fee 4000.
[2023-05-26T13:29:14.167461Z DEBUG safenode::domain::fees::spend_queue] stats: highest 10494, high 8000, medium_high 6333, avg 4667, medium_low 3333, low 2000, lowest 1662, std_dev 2494, len 3, queue [8000, 4000, 2000]
[2023-05-26T13:29:14.169977Z INFO safenode::network::event] Local node is listening on "/ip4/127.0.0.1/udp/42298/quic-v1/p2p/12D3KooWNegZeQkXZs9kQChePpwna7XVt8MeYbRF33fM2zcdQ3J3"
[2023-05-26T13:29:14.170057Z INFO safenode::network::event] Local node is listening on "/ip4/192.168.1.104/udp/42298/quic-v1/p2p/12D3KooWNegZeQkXZs9kQChePpwna7XVt8MeYbRF33fM2zcdQ3J3"

It says v0.1.0. Which one should it be? And am I in or not?

3 Likes
22

Your logs show it’s listening on a UDP address, so I am afraid it’s still an old version. The 0.1.0 is a little misleading, because we’re not doing proper releases yet.

The most recent versions should log a first line with Current build's git commit hash.

5 Likes
23

a small and likely trivial quirkette…

willie@gagarin:~/.safe$ ./safe -V
safenode 0.1.0
willie@gagarin:~/.safe$ ./safenode -V
error: unexpected argument '-V' found

Usage: safenode [OPTIONS]

For more information, try '--help'.
willie@gagarin:~/.safe$ ./safenode --help
Usage: safenode [OPTIONS]

Options:
      --log-dir <LOG_DIR>
          Specify the node's logging output directory.
..........
3 Likes
24

Current build's git commit hash: ---- No git commit hash found ---- to be precise.

5 Likes
25

@bzee should the join command perhaps include nohup just in case folk close out like I just did. seems we may be causing unnecessary churn?

5 Likes
26

On a Windows 10 machine behind a NAT firewall, VPN, and no port-forwarding. Grabbed, unzipped, and placed the safenode directory at root and then using PowerShell as an administrator:

C:\safenode> ./safenode --peer=/ip4/206.189.29.202/tcp/38379/p2p/12D3KooWN7AJe7wxVckZ6SF3ybYXVgetQ9hkYWHCHLokpSRC31W2 --log-dir=/tmp/safenode --root-dir=/tmp/safenodedata

Everything worked as expected…the node shut down after a few minutes:

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.

safenode-log.zip (6.0 KB)

:+1:

11 Likes
27

Yay! Another Testnet is here!

10 Likes
28

Yes, on Windows (and Linux) it shows that unfortunately. :frowning: Which is my mistake. I built those binaries this morning on a Windows partition I don’t do developing on. I hadn’t checked it out with git, but downloaded the zip of the repository via GitHub. Which then it means it doesn’t know the current revision it’s building. Linux is probably some mistake with the checkout too. Hopefully will be resolved by next testnet!

I guess it depends on use cases of people. I’m also not sure what the Windows or macOS equivalent of that would be.

:pray:

9 Likes
29

Indeed, fair enough.

3 Likes
30

So it was like this (for other non-skilled to know):

  1. I searched for “safenode” in filebrowser and removed everything I found. There was many.
  2. But it didn’t show the stuff in usr/local/bin, where is the one it runs.
  3. I removed that manually, which wasn’t possible from GUI, had to re-learn to do it manually. (Oh, how I hate Linux).
  4. Put a hopefully correct version there.
  5. Run it.

Got:

safenode: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by safenode)
4 Likes
31

Are you using Debian 11 or similar?

2 Likes
32

The GLIBC_2.32 issue is build related. Ubuntu 20.10 and newer uses GLIBC_2.32 whereas Ubuntu 20.04 and earlier uses GLIBC_2.31.

What version of Ubuntu do you have @Toivo

3 Likes
33

Toivo - It is confusing when there are different safe binaries for different purposes … this might help…

For testnets like this, where we are using very specific binaries that will likely be only useful for hours or days at a push, one strategy is to download and extract to a temporary dir - say /tmp/safetestnet/ and run the commands from there

like…
/tmp/safetestnet/safenode --log-dir=/tmp/safenode --root-dir=/tmp/safenodedata

then when the test has done its stuff, just delete all of /tmp/safetestnet.

Always do a ls -al $(which safe) when you are in any doubt and check that the date is sensible. which safe will point to the safe binary that will run if you do not give a specific path

2 Likes
34

Ubuntu 18.04.6 LTS. Time to update!

Thanks, I might give it a go!

3 Likes
35

Be aware that the update may take several hours.

4 Likes
36

@Southside is right it could take a while and may be easier to do a fresh install.
Anyhow, the issue will be solved if you build your own binary.

Edit:
Also see that @happybeing is on it :slight_smile:

5 Likes
37

I just opened an issue around this (no solution but to upgrade OS AFAIK):

6 Likes
38 
[2023-05-26T16:07:46.243123Z INFO safenode::network] Node (PID: 13196) with PeerId: 12D3KooWDjaP99CX25KCisoZ487bYyVpXbCbhupbqtwtawfSmDkw

C:\abc>safenode --log-dir=/tmp/safenode --root-dir=/tmp/safenodedata --peer=/ip4/206.189.29.202/tcp/38379/p2p/12D3KooWN7AJe7wxVckZ6SF3ybYXVgetQ9hkYWHCHLokpSRC31W2
Starting logging to directory: "/tmp/safenode"
Node is stopping in 1s... Node log path: /tmp/safenode
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:
    safenode\src/bin/safenode/main.rs:235:36
4 Likes
39

Strange one. If I run a node from say /home/user/Downloads with /home/user/Downloads/safenode --log-dir=.. etc it works as expected - ie it gets detected as being behind NAT and stops after a couple of minutes.

But

If I copy the binary into /usr/local/bin and run it from outside that dir with safenode --log-dir=.. etc it doesn’t die, just keeps on listening. I changed the owner and group from root to my username but it didn’t make any difference.

Can anyone else reproduce this?

1 Like
40

What if you use the full path to the binary?

Also try which safenode.

5 Likes