I’ve set a laaaarge upload (a directory of video files) going again (still using client defaults) and it has been sitting at this point for at least an hour:
Connected to the Network
Total number of chunks to be stored: 53458
What’s happening in terms of activity and network traffic here (I’m not seeing much up or down and have a separate large download going which probably accounts for most of it)? There’s no progress indication which would be nice.
The log contains a lot of OutgoingConnectionError errors and seems to have stopped activity a long time ago so I suspect that up until that message it was just doing local preparation, and then could not access the network.
It may help to have both progress indication and a timeout at that point.
EDIT:
I stopped the download to see if that was affecting this very large upload but it isn’t.
After restarting the upload it hasn’t got past Connected to the Network before, looking at the logs it is now full of OutgoingConnectionError messages again, after the initial success showing it connected to 182 peers.
So my network isn’t loaded at all now but connectivity for the client seems to fail after a few minutes.
I’ll some smaller uploads and report back…
- 44k file, 4 chunks to upload completed in about 3 mins including repaying for 2 chunks
- 18M file, 36 chunks to upload … gave
Cannot get store cost for NetworkAddress errors for 5 of the first batch of 20 chunks and continued to upload the final 16 chunks which gave no errors. After two phases of repaying it completed successfully in 6mins.
Verification gave mixed messages. First it said failed to fetch for 7 chunks, then it says “verified 36 chunks” which I guess means it attempted to verify but might be better saying “verified 29 of 36 chunks”:
After 88.051157424s, verified 36 chunks
======= Verification: 7 chunks were not stored. Repaying them in batches. =============
Failed to fetch 7 chunks. Attempting to repay them.
- 270MB file, 524 chunks to upload is proceeding in batches of 20… during batch at 40 chunks I’m seeing
OutgoingConnectionError in the log but mixed with Final fees calculated as: so I guess it has enough peers to proceed.
During batch 60 chunks the terminal gave one Cannot get store cost for NetworkAddress but the log shows it is also proceding ok.
For batch 80 chunks same, 100 same, 120 same, 140 same, 160 two failures, 180 one failure, 200 one failure, 220 two failures, 240 one failure, 260 zero failures… EDIT: as soon as I stopped watching the failures stopped! Then one failure at 340. One at 380. One at 420. One at 480. One at 500. 
Verification: 32 (of 524) chunks not stored, repaying… in the end it failed:
[snip]
Uploaded chunk #e58b4e.. in 1 seconds
Failed to fetch 12 chunks. Attempting to repay them.
Cannot get store cost for NetworkAddress::ChunkAddress(f1bc07(11110001).. - - f1bc07e1e17f697f998e92b6300eeeaec5556d8f43ec332d7254e6a8d032e275) with error CouldNotSendMoney("Network Error Not enough store cost prices returned from the network to ensure a valid fee is paid.")
Transfers applied locally
All transfers completed in 35.006110548s
Total payment: NanoTokens(19730894) nano tokens for 11 chunks
Uploaded chunk #2de77d.. in 1 seconds
Uploaded chunk #5f4999.. in 1 seconds
Uploaded chunk #1b44f4.. in 1 seconds
Uploaded chunk #a239b1.. in 1 seconds
Uploaded chunk #94e702.. in 1 seconds
Uploaded chunk #8960e3.. in 1 seconds
Uploaded chunk #b07b00.. in 1 seconds
Uploaded chunk #be21b7.. in 1 seconds
Uploaded chunk #20c9bc.. in 0 seconds
Uploaded chunk #35a8be.. in 0 seconds
Uploaded chunk #d8d7a4.. in 0 seconds
Error:
0: Chunks error Failed to get find payment for record: f1bc07e1e17f697f998e92b6300eeeaec5556d8f43ec332d7254e6a8d032e275.
1: Failed to get find payment for record: f1bc07e1e17f697f998e92b6300eeeaec5556d8f43ec332d7254e6a8d032e275
Location:
sn_cli/src/subcommands/files.rs:297
So for each batch of twenty chunks it shows one Cannot get store cost for NetworkAddress error except for the first two batches which went ok and the occasional double error or zero errors. That seems a bit too regular to be a network only issue so maybe the client has an issue here?
For my very large upload (50k chunks) is it possible that the client loses connection to the peers and for a very large upload and then fails to progress?
