Our next testnet, MoreStabilityNet, is looking to see how node stability has been affected by recent fixes.
The NodeDiscoveryNet has done well, surfacing data all the way through, even though we lost 12/20 nodes per droplet due to excessive memory.
We’ve a few fixes in and more pending that should improve things here. And we’d like to see how this goes for our MaidSafe Digital Ocean droplets and for those starting nodes in the community.
With all that, our objectives for this testnet are relatively simple:
- Verify if we still have “lost nodes” and get more data there (we may be asking for some specific types of behaviour to be tested as we go foward).
For those wondering what a lost node might look like: It’s basically a node dying or being killed due to excessive memory usage (>400mb for a long time eg). If you’re only runnning a node at home, or one per machine, you should likely not see this. If you run many nodes per machine, it’s more likely that a spike might cause the operating system to kill your node.
Network Details
Node version: 0.86.25
Client version: 0.79.26
SAFE_PEERS: /ip4/176.58.124.107/tcp/44439/p2p/12D3KooWEwMPj64C1MXEKaCYHGgtMApNzzvoynfprLJRLfgfGo7G
Alternatives:
"/ip4/161.35.39.103/tcp/38297/p2p/12D3KooWCgxHVhPfSndYod2KzRivZF5AnF125R5WoZt5GbX7JMtB"
"/ip4/143.110.169.215/tcp/38247/p2p/12D3KooWHSrZhRZSstxdhHGU3Vfj6Czxp12zqepsLvhFEfGS9R5Q"
"/ip4/161.35.39.22/tcp/36197/p2p/12D3KooWT1ywindpChtzfaWHfCFWexGfxYG1AVNQxwyEwR2cZwR4"
"/ip4/165.232.101.63/tcp/46029/p2p/12D3KooWGEBCRAmekSwfa7yidNNYbXtRDh1JPP14mntgtJ1yGChb"
"/ip4/178.62.91.4/tcp/39243/p2p/12D3KooWGXKWUfiCvEevBaT9VnmR7qVihyQD1PaJThzG4LLewJCU"
"/ip4/165.232.101.62/tcp/34009/p2p/12D3KooWAUuNGrFXux6Fx9kJGSzRxM6fXr1ZBvjY64ujqx3MwjSv"
"/ip4/161.35.39.101/tcp/40003/p2p/12D3KooWEPNrJmZyhRyEqvFkSng8v4yVuQ1ZJDu2PerLRpaQkELH"
We have 100 droplets running a total of ~2000 nodes. One droplet has 2vcpu and 4GB of memory.
If you are a regular user, see the ‘quickstart’ section for getting up and running.
If you are a first-time user, or would like more information, see the ‘further information’ section.
Quickstart
If you already have safeup, you can obtain the client and node binaries:
safeup client --version 0.79.26
safeup node --version 0.86.25
Run a Node
Linux/macOS:
SN_LOG=all safenode
Windows:
$env:SN_LOG = "all" ; safenode
Connect to the Network
Linux/macOS:
export SAFE_PEERS="/ip4/176.58.124.107/tcp/44439/p2p/12D3KooWEwMPj64C1MXEKaCYHGgtMApNzzvoynfprLJRLfgfGo7G"
safe files upload <directory-path>
Windows:
$env:SAFE_PEERS = "/ip4/176.58.124.107/tcp/44439/p2p/12D3KooWEwMPj64C1MXEKaCYHGgtMApNzzvoynfprLJRLfgfGo7G"
safe files upload <directory-path>
Further Information
You can participate in the testnet either by connecting as a client or running your own node.
Connecting as a client requires the safe client binary; running a node requires the safenode binary.
Obtaining Binaries
We have a tool named safeup which is intended to make it easy to obtain the client, node, and other utility binaries.
Installing Safeup
On Linux/macOS, run the following command in your terminal:
curl -sSL https://raw.githubusercontent.com/maidsafe/safeup/main/install.sh | bash
On Windows, run the following command in a Powershell session (be careful to use Powershell, not cmd.exe):
iex (Invoke-RestMethod -Uri "https://raw.githubusercontent.com/maidsafe/safeup/main/install.ps1")
On either platform, you may need to restart your shell session for safeup to become available.
Installing Binaries
After obtaining safeup, you can install binaries like so:
safeup client # get the latest version of the client
safeup client --version 0.79.26 # get a specific version
safeup node # get the latest version of the node
safeup node --version 0.86.25 # get a specific version
safeup update # update all installed components to latest versions
When participating in our testnets, it is recommended to use a specific version. In our project we release a new version of the binaries every time we merge new code. This happens frequently, so over the lifetime of a testnet, many new releases will probably occur. So for participating in this particular testnet, you may not want the latest version.
The binaries are installed to ~/.local/bin on Linux and macOS, and on Windows they go to C:\Users\<username>\safe. Windows doesn’t really have a standard location for binaries that doesn’t require elevated privileges.
The safeup tool will modify the PATH variable on Linux/macOS, or the user Path variable on Windows. The effect of this is that the installed binaries will then become available in your shell without having to refer to them with their full paths. However, if you’re installing for the first time, you may need to start a new shell session for this change to be picked up.
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
This will output all the logs in the terminal.
Sometimes it will be preferable to output the logs to file. You can do this by running the node like so:
# Linux/macOS
SN_LOG=all safenode --log-output-dest data-dir
# Windows
$env:SN_LOG = "all"; safenode --log-output-dest data-dir
The location of data-dir is platform specific:
# Linux
~/.local/share/safe/node/<peer id>/logs
# macOS
/Users/<username>/Library/Application Support/safe/node/<peer id>/logs
# Windows
C:\Users\<username>\AppData\Roaming\safe\node\<peer-id>\logs
If you wish, you can also provide your own path:
# Linux/macOS
SN_LOG=all safenode --log-output-dest <path>
# Windows
$env:SN_LOG = "all"; safenode --log-output-dest <path>
The advantage of using the predefined data-dir location is you can run multiple nodes on one machine without having to specify your own unique path for each node and manage that overhead yourself.
Connecting as a Client
You can use the safe client binary to connect as a client and upload or download files to/from the network.
To connect, you must provide another peer, in the form of a multi address. You can find one in the ‘Network Details’ section at the top.
It is recommended to set the peer using the environment variable SAFE_PEERS. You can set this variable once and it will apply for the duration of your shell session:
# Linux/macOS
export SAFE_PEERS="/ip4/176.58.124.107/tcp/44439/p2p/12D3KooWEwMPj64C1MXEKaCYHGgtMApNzzvoynfprLJRLfgfGo7G"
# Windows
$env:SAFE_PEERS = "/ip4/176.58.124.107/tcp/44439/p2p/12D3KooWEwMPj64C1MXEKaCYHGgtMApNzzvoynfprLJRLfgfGo7G"
NOTE: If you close and/or start a new shell session, you will be required to redefine this environment variable in the new session.
As an alternative to the environment variable, it’s also possible to use the --peer argument:
safe --peer="/ip4/176.58.124.107/tcp/44439/p2p/12D3KooWEwMPj64C1MXEKaCYHGgtMApNzzvoynfprLJRLfgfGo7G" ...
However, this requires specifying the peer with each command.
Using the Client
You can now proceed to use the client, by, e.g., uploading files:
safe files upload <directory-path>
To download that same content:
safe files download
This will download the files to the default location, which is platform specific:
# Linux
~/.local/share/safe/client/downloaded_files
# macOS
/Users/<username>/Library/Application Support/safe/client/downloaded_files
# Windows
C:\Users\<username>\AppData\Roaming\safe\client\downloaded_files
To download to a particular file or directory:
safe file download [directory/filename] [XORURL]
Troubleshooting
If you encounter a problem running any of our binaries on Windows, it’s possible you need the Visual C++ Redistributable installed.
I like the name of this one !! Count me in.
Connected to the Network Preparing (chunking) files at ‘/Users/x/safenetwork.mp4’…
connection node if anyone needs one. My client wouldn’t connect to the default choice. I won’t overload this VM.