willie@gagarin:~$ safe wallet send 1.8 953ad94acacb79f3925d42e5218f4b5cfe4360526090ae056ce265df667fc34e593c239489b86fe480f30cf9b809450d
Logging to directory: "/home/willie/.local/share/safe/client/logs/log_2024-05-23_19-04-55"
safe client built with git version: b0e028e / stable / b0e028e / 2024-05-20
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network Wallet has pre-unconfirmed transactions, can't progress further.
Failed to send NanoTokens(1800000000) to 953ad94acacb79f3925d42e5218f4b5cfe4360526090ae056ce265df667fc34e593c239489b86fe480f30cf9b809450d due to Wallet(UnconfirmedTxAfterRetries).
Error:
0: Wallet Error Unconfirmed transactions still persist even after retries.
1: Unconfirmed transactions still persist even after retries
Hah, now the one having 21 nodes shows 0 shared ports on the router! But there are no more shunned nodes and GETs are happening all the time. It has even earned more. What is this?
The other Laptop with 17 nodes still has 17 "Independent Port Sharing"s enabled.
I’ll leave them running and check back in the morning.
Whatever it is, it is pretty damn nice to have some nodes running from home again and participate testing. Cheers to all!
Please share this to the recipient:
a9cc4f1db6ccbccc4f61becccacc6692cc3cc0cc10cbcc32dccc9dcc6deccc61f4cce1ccd4cc6ccbcc6748cacc2552afccf1cc1cc5ccc8ccdfcc4292cc8bcc210f5cd2cc3e8fccb4cc0a81cc24cdcc73f6ccfecc98cc2188ccc4ccebccf8cc1c3597ccdfccdbcc286126bcccffccbdcca4cccdcca9ccd3cc2d14a5cc4ebccca3ccc4cc22e9cce7cc4ed6cc45dfccb1cc29280eadccc4ccb0cc6000dca6cc594f5090cc8acc0f342c6fcdcc7ab2cc5a5976c4ccd0ccf7cc89ccf1cc5b0a1dddcc772e2c96cc52235674717975c6cc4c90cc90cc43b3cc82cc92cc7d4c92cce9ccc8cce7cc89cc6338f7cc65736f4e58bfcc4602aecce9cc2e4db1cc38f2cca3cc3fc9ccd2cc0923acccc4cc26a2cce5cc1e7a3d0bceccf3cc506d2041cdcc17f8cc72c1cc69202c4701cfccfcccebcc8ccc35b5ccc1cc1388cc6d00dca5ccd6cc94cc0255dacc64a2cc59b2cc4bf4cccecc6141015c4186cc5ebfcc3e534d5995ccd4cc230b077b0a516452d2cc3abccc89cc07f0ccd1ccc4cc6162293b91cc3000dc9391646574707972636e45a981
Some must have dropped due to inactivity. The router would prune the upnp connections after a period of time.
Maybe this is something that the node s/w may have to account for, a hicup (no activity) for some seconds causing the router to drop the upnp assignment. @joshuef does the node keep alive the upnp connection? If not then maybe @Toivo could give you the logs for those nodes next time he sees this happening
You won’t typically notice it until you realise they are no longer earning. It was the same for not setting up port forwarding and/or firewall rules for port forwarding. The nodes fill up with churn chunks but no earnings.
If its available and teh router s/w actually does it properly
I started my uploading of small random files again last night. It has been down for a couple of days as it ran out of token and I was too busy to check. It was working. Might still be if it’s not run out again. Too busy to look!
Yesterday I used my computer for some time on battery power. I suspends after 15 minutes. I did a test today and it seems that the router drops the connections very soon after the computer has gone into suspension.
On re-activation nothing on Vdash indicates any change has happened. GETs and PUTs are rolling and everything seems business as usual. For example on this test I even had one node updating a StoreCost price, which I have been thinking as a sign that the node is reachable externally. That probably happened some time during dimmed screen before the laptop went into suspension.
Still we need to test strange behaviour. But maybe a little later. The live network will not be treated better than that, just we expect the strange behaviour not to affect 1/3 of the network at once