a kali linux iso here if any one fancies a 4Gb download
safe files download "kali-linux-2023.3-installer-amd64.iso" b6eea5ffd85a1dfe5b2804c4a50e04f317676e47ef89cfd19d8c074ea1baba65
3 Likes
This upload is taking considerably longer than it should…
Gotta be honest - I think there is a lot of work to be done yet before we have a proper beta test worthy of the name.
Sorry if thats an unpopular opinion or if I have missed something crucial but thats how it looks from here.
2 Likes
I am having no issues on default settings for uploads using sn_cli 0.90.2
whats the -b4 for in your above upload command ?
2 Likes
A hangover from a sloppy cut n paste - I’ll try again without it - not that it should make any difference, theres only 3 chunks anyway
2 Likes
6 Likes
Anecdotal perhaps - but I seem to have had some recent success after deleting client/wallet and getting a fresh coin from the faucet
@Roland the full log you requested earlier
**************************************
* Uploaded Files *
**************************************
"safe.log" 62f3238932961191bf588bdb481eeb59dca90efc888e6a14dfd1020fdd4b4b4a
Among 1 chunks, found 0 already existed in network, uploaded the leftover 1 chunks in 12 seconds
**************************************
* Payment Details *
**************************************
Made payment of 0.000000431 for 1 chunks
Made payment of 0.000000076 for royalties fees
New wallet balance: 0.999998581
8 Likes
I did get a ton of OutgoingTransport/OutgoingConnectionError - Handshake Timeouts.
I definitely need to get to the bottom of this issue 
.
Only 7 out of 200 nodes have a wallet balance > 0.
In-fact, some nodes simply fail to bootstrap to the 1st peer in the network contacts due to the transport error:
[2024-03-28T17:03:31.459248Z WARN sn_networking::event] OutgoingConnectionError to PeerId("12D3KooWDV4aSK3oxQNumbvKAvrAExKRhDSwEbti6y5JaW9MHeAv") on ConnectionId(1) - Transport([("/ip4/138.68.146.254/udp/52597/quic-v1/p2p/12D3KooWDV4aSK3oxQNumbvKAvrAExKRhDSwEbti6y5JaW9MHeAv", Other(Custom { kind: Other, error: Custom { kind: Other, error: HandshakeTimedOut } }))])
[2024-03-28T17:03:31.459386Z ERROR sn_networking::event] Dial errors len : 1
[2024-03-28T17:03:31.459406Z ERROR sn_networking::event] OutgoingTransport error : Other(Custom { kind: Other, error: Custom { kind: Other, error: HandshakeTimedOut } })
[2024-03-28T17:03:31.459430Z WARN sn_networking::event] Problematic error encountered: Custom { kind: Other, error: Custom { kind: Other, error: HandshakeTimedOut } }
[2024-03-28T17:03:31.459445Z WARN sn_networking::event] Cleaning out peer PeerId("12D3KooWDV4aSK3oxQNumbvKAvrAExKRhDSwEbti6y5JaW9MHeAv")
Next attempt will be to provide 5 or more off the Peer IDs to SAFE_PEERS env var, reset the services via safenode-manager, and see if some of these nodes can be kick started properly to join the network.
4 Likes
Yay! The testnet is here. I love the fact that as soon as one testnet dies, another is born right away.
12 Likes
Every other network’s beta has had issues, including ethereum’s. A beta isn’t supposed to be perfect and smooth. The beta is used to iron out potential issues. This is a great beta network so far
10 Likes
@roland would you be so kind as to help with what has replaced relevant record length, not seeing anything similar.
1 Like
Hey @Josh, sorry I’m not sure if I follow you, do you mean the relavant record count when calculating the store cost?
1 Like
Hello everyone,
Noob questions:
“Node started” message means I have successfully made it? 
how do I know it is running?
or - how can I stop it?
Can I just close my Powershell and it will run in the background?
Thanks for any answer! 
5 Likes
Thank you! I will take a look at the logs. Also, we have raised an PR to sort out the error due to the unconfirmed transcations that you had seen earlier. Hopefully that addresses the issue.
1 Like
Hey, there was a time when Joshuef said (I think that I understood him correctly) that relevant record length is the number of records that your node is currently responsible for. (not the total number of records in your records dir) that number differs correct?
1 Like
Looks like some loose ends are getting tidied - Im a bit more confident now
Fantastic to get such almost instant feedback from the devs. 
6 Likes
Ah yeah, you’re right. Unfortunately, the PR for that change has not been merged yet feat(networking): only consider close records in price setting by joshuef · Pull Request #1514 · maidsafe/safe_network · GitHub This would make it such that the store cost would be dependent on the number of records that a node is responsible for.
Currently in the testnet, the nodes still use all record count to calculate the store cost.
4 Likes
That answers my question exactly! Thank you
2 Likes
That means the node has started, but doesn’t necessarily mean it’s going to “do a thing” yet. Just that the software is running.
If you’re on a home connection - normally behind a NAT - you can make your outgoing connection and everything looks great, but no one can get to you.
The easiest way to find out if it’s working - without going through the logs anyway - is to check if your node is earning anything using the command that it posts to you.
As for will it stop if you close powershell - yes. Just running the command does not set it up as a service (something that will run in the background) and it’s attached to your powershell instance.
1 Like
When trying to querry the balance, I get this message:
safe : The term 'safe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ `safe wallet balance --peer-id=1sd5gg5gR6WA9jDxdadsoWmajp4b5fdfJmqCu3D4 ...
+ ~~~~~
+ CategoryInfo : ObjectNotFound: (safe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
what does it mean, please?
I actually still think it would be useful when you just run safenode as a foreground process, to have the logging output go to stdout. I don’t remember encountering many programs that output to log files by default. It would even be useful to have it go to both stdout and file so that you could use journalctl to see the node output.
2 Likes