I was forwarding ports, as said it was working in the previous testnet. TCP only though. I did open UDP as well right now, just in case, but there was already someone else reporting it in the thread, wasn’t it?
2 Likes
Yes TCP won’t work here as you say, UDP will. So you would really want the ports forwarded before starting the nodes.
7 Likes
Same here. Uploads are much faster than in the previous testnets (I uploaded yesterday a file of over 4GB in just over an hour), but I also have the same issue with a few chunks failing.
8 Likes
please keep logs if you have them and @qi_ma can likely work this bug out.
6 Likes
@qi_ma do you need me to update the client and rerun the upload?
3 Likes
Hi, All,
Regarding the charge even when no advance is made, it is because the payment was taken from client wallet after the store_cost query and be sent to nodes together with the chunk uploading.
This means even the chunk upload got failed for some reason, the spends was already be published.
I checked the logs you guys shared regarding this, and all charge on no advance is related to this.
Have to say this is an expected behaviour so far.
Regarding why the chunk upload is failed, I will need some further logs for the following 5 nodes:
"12D3KooWGzUkRQoGusDVHFo6zTY421oY37BotvxncLTkTxV4gYEu"
"12D3KooWMC4qeSKSuLt5NFX2LmgPzYaMh159xCwBUnLQ9LtLeTHE"
"12D3KooWPwKAzU4z4DfthVkzTwhaTgDkRqBJFV3P5umBBypKJAH7"
"12D3KooWQ7RjqydeHdjuEacWWCik2rzqw7kHm1xeK8kiTx5Jouaw"
"12D3KooWSvDVMK8NJHhpre9oaqybJZrs9zE3XgA1dMegJHy4PBE5"
If any of you holding one of them, please share me the log of that node, thank you very much
====== just find some nodes are run by us, and one of key node’s log helped to pin the issue
10 Likes
what’s your current version is ?
and, yeah, please update if can, thx
3 Likes
sn_cli 0.89.29
1 Like
Do I need to clean .local/safe ?
1 Like
Do I need to clean .local/safe ?
no, you can use all your previous client stuff, including wallet.
just replace the executable will be fine. i.e. executing safeup client
1 Like
Retry after update of the file that failed before:
safe fi
les upload Rockers1978.mp4 -p
Logging to directory: "/home/ubuntu/.local/shar
e/safe/client/logs/log_2024-01-31_10-11-17"
Built with git version: 76a03f6 / main / 76a03f
6
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 43 peers
🔗 Connected to the Network
"Rockers1978.mp4" will be made public and linka
ble
Starting to chunk "Rockers1978.mp4" now.
⠁ [00:00:00] [---------------------------------
⠓ [00:01:17] [---------------------------------
Unverified file "Rockers1978.mp4", suggest to r
e-upload again.
**************************************
* Uploaded Files *
**************************************
Among 5 chunks, found 0 already existed in netw
ork, uploaded the leftover 5 chunks in 2 minute
s 53 seconds
**************************************
* Payment Details *
**************************************
Made payment of 0.000000080 for 5 chunks
Made payment of 0.000000008 for royalties fees
New wallet balance: 499.997617613
ubuntu@instance-20211208-1104:/volume1$ safe --
version
sn_cli 0.89.31
Logs at
"safe.log" c52edbde72f2477be3f919372a38f7b0b9d94eae739beb5222a57a96764db40e
3 Likes
@qi_ma
Ditto. Have been trying to upload a 2GB file for half the day. First attempt it did 3/4 of the chunks, 2nd go it did most of the rest, but subsequent attempts kept getting more and more failures; eventually leaving the same persistent 10 chunks that won’t upload despite repeated attempts.
Log files - most if not all of them for the my 2GB upload attempt:
“log_2024-01-31_20-57-22.tar.gz” bd22148eafe88dcff70dd88c0f696e33d4e534104198c54abedba07443123003
8 Likes
Thx 4 another testnet Maidsafe devs.
Happy testing everyone, what a bummer that i can’t start testing before tomorrow.
We are really being spoiled 
Keep hacking super ants
10 Likes
Wasn’t mine, I hope you find them.
Maybe time to find ways to expel nodes that don’t store/deliver a chunk they are supposed to?
4 Likes
Do we have a leak problem?
Timestamp: Wed Jan 31 06:05:27 EST 2024
Number: 3
Node: 12D3KooWGy4WdTmm9jfWtzn2TC5brbe9HpuJxWxoUQnmyg
7Vh24a
PID: 965882
Memory used: 34.1992MB
CPU usage: 1.3%
File descriptors: 268
Records: 1085
Disk usage: 439MB
Rewards balance: 0.000061944
------------------------------------------
Timestamp: Wed Jan 31 06:05:27 EST 2024
Number: 4
Node: 12D3KooWLpxH1m5UnmAwAkJU65ZmwsPVeGs25CFSnMQYSX
QeeiAK
PID: 965895
Memory used: 1560.91MB
CPU usage: 18.1%
File descriptors: 280
Records: 1035
Disk usage: 417MB
Rewards balance: 0.000045287
4 Likes
Ah, no worries,
I find some are running by us, and one of the key node’s logs helped to pin the issue.
9 Likes
Oh, great to hear!
(I was so sure those were in a home environment behind NAT.)
3 Likes
For that node 4 in question, does it keeps using that much memory for a while?
if it is just started up, may need leave it for a while to calm down.
5 Likes
Announcement: In less than a day I have earned 1.7 hundredths of a UK penny’s worth of SNT! 
I’m now thinking that useful metrics would be earnings per hour / day / week etc. Any other suggestions for vdash?
Also, has anyone else tried the new live prices feature?
7 Likes
Looks like it stabilised, although still higher
Timestamp: Wed Jan 31 06:19:32 EST 2024
Number: 4
Node: 12D3KooWLpxH1m5UnmAwAkJU65ZmwsPVeGs25CFSnMQYSX
QeeiAK
PID: 965895
Memory used: 299.781MB
CPU usage: 18.6%
File descriptors: 280
Records: 1035
Disk usage: 417MB
Rewards balance: 0.000045287
4 Likes