I think the best thing to do here is to look at either journalctl or the safenode logs for the services.
I think this is because the nodes haven’t started yet, and so there is no wallet. I fixed an issue with that on the status command, will need to get it in for this one too.
Can I have a peer please, to connect using a build of the client as it doesn’t work as is. Because… (next post)
Ho hum, brand new install of Ubuntu 24. Installed safeup and same error for client and node installs. Both are failing just before the download completes which is similar, but not the same as the errors I was getting until quite recently. Then the error happened after the downloads reach 100%.
My mobile internet is a little less good today because I’ve moved location but I don’t think that should cause such consistent errors.
safeup client --version 0.91.2
**************************************
* *
* Installing safe *
* *
**************************************
Installing safe for x86_64-unknown-linux-musl at /home/mrh/.local/bin...
Installing safe version 0.91.2...
⠴ [00:00:38] [#####################################>--] 11.09 MiB/11.86 MiB (3s)thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/sn-releases-0.2.0/src/lib.rs:193:56:
called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Body, source: hyper::Error(Body, Kind(UnexpectedEof)) }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
first one is free, /ip4/192.168.88.250/udp/58370/quic-v1/p2p/12D3KooWSo4ApWBBwkpmVLrPXX3tz5xLUk2vqdjw8T4JiHHjRY5J
CPU seems to be way down on this, it is great, punchnet was a CPU hog.
Aaah is that really a public WAN IP?
If @happybeing manages to connect to it, my mind will be blown, lol 
.
Here’s one: /ip4/165.232.45.224/udp/60716/quic-v1/p2p/12D3KooWJHw29hHc6kQoLGzdDrcgGqVLPCusFmc1SgfsthNK7X5H
I’ll do some digging when at my laptop later, but there were 2 issues. 1 was a never ending upload that didnt complete. 2 was the max attempts at payment reached.
Your mind is in tact but @chriso’s peer worked and so did the faucet 
Well thats why it was free. 
sorry I didn’t even look at it properly.
@happybeing List of peers here: https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
How are people doing on the rewards front, I am going to go broke soon, may need to start moonlighting.
can someone help me please debug the logs and understand if there’s a problem and what are the errors?
What is your uptime?
IMHO these are not particularly unusual figures for a set of nodes that have only run for a couple of hours. Hang in there and report back in another hour or two.
I think what some people are doing right now is moonlighting from their paid jobs!
I have 1 node up in AWS for nearly 2 hours with 0.000000020
I have 20 nodes up from home started gradually over the last hour with a total of about 200 nanos. Only 6 have earned so far. They are with the --home-network option.
Next I’ll try a couple without the --home-network option that I couldn’t get to earn at all on the last network.
Then I’ll try a couple of Mac based nodes for the first time.
So far it seems that the connection count is way down from before. Only about 3000 connections on the whole of the router instead of about 9000 before. Network usage is a lot lower before as well. About 1.5Mb/s both up and down on average over 4 mins rather than about 20 up and down. Might be able to run more nodes!
No rewards so far for 25 node using --home-network and no port forwarding.
These have been running for about two and a half hours and are receiving plenty of PUTS.
But 
I also just had a 2GB upload fail on the last chunk (~42 min.) with maximum specified repayments Good news is that it immediately completed successfully on the re-try.
From a quick glance at those lines I don’t see anything untoward there. You aren’t even showing any nodes as ‘Shunned’ which is good.
How long have they been running as per Southside’s question?
and were they started with the ‘–home-network’ option or not?
This might be a long shot but I read a while back there could be some issues accessing S3 based on SSL version. There were specific entry points which appeared to be fronted by incompatible certs. Some people were able to work around this by hard coding a working ip in /etc/hosts.
Worth doing an nslookup on s3-r-w.eu-west-2.amazonaws.com
then picking a couple of different IPs to try hard coding against. IIRC the ones called out at the time which didn’t work started with 128. I’ve run nslookup and don’t see that at the moment. I also can’t recreate any error on my ubuntu (20.04.6 LTS), but I did see it a while back.
Like I say, long shot, but possibly worth a try if your not getting any joy otherwise.
edit: this is one of the references - Possible SSL issue with AWS S3? - Rocky Linux General - Rocky Linux Forum
Thanks, that’s interesting.
The symptoms seem similar but AFAIK I’m the only person who has reported this and there are a few Linux users here, including Ubuntu so it seems unlikely if it hasn’t affected any of them.
cc @chriso
Quick question, how do I stop and remove nodes?
For some reason the command can’t be found:
sudo safenode-manager stop --service-name safenode1
sudo: safenode-manager: command not found
and for pkill I get
pkill: killing pid 32477 failed: Operation not permitted
I’m on Linux Ubuntu, was running nodes through vdash
What am I doing wrong? Thanks
Hmm - I don’t have this file, anyone else?
Edit: it’s here: .local/share/safe/client/account_secret
This actually does seem like a potentially interesting lead for this issue.
