Thanks for the ref. I ran those 2 suggested cat commands on one of my safenode logs and got 952 & 480 respectively, so thinking that could be the clue for what’s maybe going wrong in my case.
Did you come across any other advice on setting up any specific inbound and outbound port rules on the server side beyond default settings?
Small question which I presume has a simple and obvious answer: how to kill my (zombie) nodes? I could ~rm -rf~ the whole thing, but can I just kill the nodes so I can keep my logs?
EDIT: I mean, other than just killing the process? Or, is there a “neat” way of killing the processes? I don’t see any CLI option when I browse the Github repositories, nor when I run ~$ safe --help~.
Thank you for your update after diagnosing and finding the cause of the vdash v0.17.2/safenode v0.105.2 log format compatibility issue.
I think in my case, with some HandshakeTimedOut errors etc. I may have a further issue with inbound/outbound port rules for my ubuntu VM in Azure. In the meantime I think just I need to do some more searching and reading related issues on this forum to see if I can resolve whilst awaiting forthcoming version updates.
Many thanks for your helpful pointers. I only setup the VM in Azure whilst awaiting delivery of a new raspberry pi to play with (for this and some other general experimental web based stuff!). Its maybe easier to wait until newer versions are released in due course when hopefully I’ll also be able to get a few nodes running on my pi through my home router.
I don’t think you can do much about those errors - I think it is a regression that they will attempt to fix in the next testnet. The fact you have PUTS is positive. Earnings are sparse in this test so the lack of those is not necessarily a problem with your nodes.
A great read now publically availabe with the above command for anyone interested, on the Australian hacking scene in the 80s and 90s. It was 733.3kB and took 18s.
My wallet balance is now 0.888691595: I’ve been very frugal
EDIT: I should add that the book is available for free, so legally we’re not even being bold here Underground download page
🔗 Connected to the Network Downloading "“Underground – Dreyfus, Suelette.epub”" from 52890fdb1a746de8d16bee88a7335ae43ea53bf2c513bf211ffc0a118d573201 with batch-size 16
Saved "“Underground – Dreyfus, Suelette.epub”" at /home/willie/“Underground – Dreyfus, Suelette.epub”
real 0m1.982s
user 0m0.683s
sys 0m0.919s
Thanks… I solved it by enabling my VPN so it wasn’t the peers after all. Mobile broadband doesn’t work well with Autonomi, even as client. I used to have a problem running nodes, the client was flaky/slow. I also have the safeup issue back and can’t use it from my laptop. cc @joshuef - might be worth looking into this before we get too far, after all we want to support mobile which might also be an issue.
What are the reasons wanting that and what effects will it have on does running mobile router/phone? nodes and what effect will it have on the Autonomi network and it’s performance?
Concerning. I wonder if others have tried this and noticed anything.
Mobile cell service providers may (probably) use Quality of Service (QoS) to prioritize signaling data over web browsing traffic or for other purposes … which would increase latency for us.
Just came back from vacation and trying this testnet.
For the first time, I’m using safenode-manager, on a podman container (not docker this time) in the usual raspberry pi 4.
I had to fight a little bit with the image, as systemd is needed and this is not so usual in containers, as far as I could see. I had to switch to podman (which is good anyway as people tend to deprecate docker) and then started 15 nodes with some of the commands I saw here:
(or one of the peers pasted at the end of the thread).
Obviously starting the services afterwards.
So far nodes are running according to vdash, but I see no nanos being earnt. I’ve read it could be normal in this testnet even with proper port-forwarding, so I’ll leave it running and we will see.
Is the faucet still working? This did not work for me:
root@aecebd1dcbf3:~# safe wallet get-faucet 188.166.171.13:8000
Logging to directory: "/root/.local/share/safe/client/logs/log_2024-04-02_22-21-04"
Built with git version: cd369d8 / main / cd369d8
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 50 peers
🔗 Connected to the Network Requesting token for wallet address: 93770ddb4f9879117d8d81b29fd449e46a95ba34699ce75a6d9cf3ed4b78aadf1e57a64277a8d5726588e2ce7256ec13
Failed to parse transfer: TransferDeserializationFailed
Transfer: "Failed to send tokens: Wallet Error Failed to send tokens due to The transfer was not successfully registered in the network: CouldNotSendMoney("Failed to send spend requests to the network:a189e2d095111eddd8cce29dd311c524ca804eb2f88de1b326e4e6c9ec8f0f375aadf17fa45c8e312fb5d2ad0ddfe614: Network Error Record not stored by nodes, it could be invalid, else you should retry: NetworkAddress::RecordKey(aff718 - 7cd5a756163e49dcca066d56c005975e4c720337a26cbd8331f2e7e48474a3cd).")."
Error:
0: Transfer deserialisation failed
Location:
sn_cli/src/bin/subcommands/wallet/helpers.rs:130
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.