Assemble at the Start Line. The Beta is About to Begin

Development Updates
142

So far I’ve received puts, gets, records, even storecost, but no nanos. Patience is a virtue.

4 Likes
143

I don’t think so. vdash takes the values from the logs which include “just earned X nanos” and “wallet balance is Y nanos” type messages. Earnings is the sum of the former. There’s not much room for me to mess that up really, but it has been known :wink:

So I suspect the issue is with the logfile messages rather than vdash but :man_shrugging:

2 Likes
144

The problem seems to be different, my friends say that they successfully start nodes. Apparently I will reinstall the OS again…

Privacy. Security. Freedom

2 Likes
145

I think, that you should not make nervous moves because you can harm yourself (or your equipment), the problem is not a bug or lack of some functionality or unforeseen network behavior, the problem is lack of information flow. It would be greatly appreciated if someone would clearly address the recurring errors and write what to do or not to do and when to expect the improvement of a particular problem.

No Safe, no wave.

2 Likes
146

On one machine, the problem was that I forgot to launch the launchpad as an administrator :frowning_face:

Privacy. Security. Freedom

1 Like
147

@peca found a solution to my other problem:

safenode-manager add --count 10 --node-port 12001-12010 --owner dimitarsafenetworkbulgaria --peer /ip4/142.93.42.123/udp/52692/quic-v1/p2p/12D3KooWBeZVDUQ6zCH6v4TyDxmYYY8HEg47LWnTNVSL2UZbXGkh,/ip4/68.183.36.156/udp/35703/quic-v1/p2p/12D3KooWL9LBbD13U5tRmCwuRbkQkXFM4gLEmf7DdN1r3Ek7yAkF,/ip4/167.71.134.146/udp/56898/quic-v1/p2p/12D3KooWQWTEJ4ngwDAE6oLgYdiZk3ejRYxp4do8Akx9GAWUEe9b,/ip4/167.71.130.219/udp/40949/quic-v1/p2p/12D3KooWBA2qjGDmnZd2GyNC5qVw82bSvWDoQj1FBjuj4h11zXaL

(Of course do safenode-manager reset before)

Privacy. Security. Freedom

1 Like
148

You use nodelauncher on the Linux machine?
You have a public ip and not a shared ip behind the ISP CGNAT?

1 Like
149

Unfortunately, these terms are not very familiar to me. I have Launcher, yes.
ISP CGNAT I have no idea what it is. I’m just being home, connected to my wifi, that’s it :smiley:

1 Like
150

How long you had the nodes running for?

1 Like
151

When gave it a second thought, you might probably be able to connect the nodes even if behind a shared IP.

Due to lack of IPv4 addresses it is common for ISP’s to give their costumers shared IP’s, so ISP have example 1 ip address to connect to the internet and behind that ip can be several customers so the CGNAT routes the traffic to correct customer. That can give that you might be able to connect to the network but the network can’t reach you.

2 Likes
152

Yes, I’ve successfully started nodes on Linux VPS’ and Windows 10, but no luck with MacOS with M1 Mac Mini, though I know others have it running find on ARM Macs… so I’ll need to figure it out.

3 Likes
154

wen ppc plz

1 Like
155

Could someone please help me debug and understand the errors that are in the log file of one of my node? :pray: error_safenode - Pastebin.com
I don’t know if there’s something wrong in the configuration of my machine

1 Like
156

From the update that came out now:

" Another issue a few of you have reported is with nodes stuck in “added” state when using the launchpad. Nic and @roland are looking at that now. For those comfortable with using the command line, the safenode-manager is another way to launch nodes which doesn’t seem to have this problem. Let us know if you need a walkthrough for this."

2 Likes
157

PowerPC? The IBM/Motorola/Apple mashup that produced a line of CPUs in the 1990s? I’m guessing never!

4 Likes
158

Around 30 hours.

2 Likes
159

x86, as in the architecture that was introduced in the 70s?! Im guessing… oh wait, thats today.

Im running p9 cause its open arch but… you get the drift.

3 Likes
160

Nodes 24-30 shown in the picture have puts/gets but no records or earned nanos yet. See what happens when they start uploading data to the network again during this day. I have 100 nodes running but only some have earned and have records yet.

2 Likes
161

Could be it’s not bootstrapping due to the bottleneck described in the update where there are too many nodes trying to join for the number of bootstrap nodes. Just a guess.

2 Likes
162

When trying to use this safenode-manager via CLI in my Linux, this is the error I get when trying to start 3 nodes:

Refreshing the node registry…
Attempting to start safenode1…
Attempting to start safenode2…
Attempting to start safenode3…
Failed to start 3 service(s):
✕ safenode1: Failed to start safenode1.service: Unit safenode1.service has a bad unit file setting.
See user logs and ‘systemctl --user status safenode1.service’ for details.

✕ safenode2: Failed to start safenode2.service: Unit safenode2.service has a bad unit file setting.
See user logs and ‘systemctl --user status safenode2.service’ for details.

✕ safenode3: Failed to start safenode3.service: Unit safenode3.service has a bad unit file setting.
See user logs and ‘systemctl --user status safenode3.service’ for details.

Error:
0: Failed to start one or more services

Location:
sn_node_manager/src/cmd/node.rs:705

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.