Hmm… on a closer look, these same chunks have been repaid already 4 times, without any advancements. From my System Activity window it seems like it is not actually uploading anything. Network connection has been working with browser though, but a while ago I had to boot my modem.
@qi_ma ,is it still the case that cancelling an upload with CTRL+C will corrupt your wallet? Because I started this upload yesterday with one batch size, then cancelled, and the one going on now was started after that. I’m going to cancel it now, update the client, reload the wallet and try again later.
Man, this is so frustrating, when I don’t know which things to blame on my wifi/LAN.
The output on the Terminal window reports suspiciously similar time for the verification of 2335 chunks. It is also waaaaayyyyyy off, when the real time was few hours. Following is an edited version of the output:
Verified 8162 chunks in 1855.334018035s
2335 chunks were not stored. Repaying them in batches.
Failed to fetch 50 chunks. Attempting to repay them.
Verified 2335 chunks in 283.315078938s
2335 chunks were not stored. Repaying them in batches.
Failed to fetch 50 chunks. Attempting to repay them.
Verified 2335 chunks in 283.408836941s
2335 chunks were not stored. Repaying them in batches.
Failed to fetch 50 chunks. Attempting to repay them.
Verified 2335 chunks in 283.332505744s
2335 chunks were not stored. Repaying them in batches.
Failed to fetch 50 chunks. Attempting to repay them.
🔗 Connected to the Network Downloading AnarchyInTheSouthside.mp3 from eaa0b39813183323b491e6715a0b4ea9f3cfdeede6f04a73c5b849b5210ad20d
Error downloading "AnarchyInTheSouthside.mp3": Chunks error Chunk could not be retrieved from the network: 85f32a(10000101)..
if you feel like something a bit beefier iv got 6.4Gb Ubuntu image here it succeeded on my home network on the first attempt but failed on second attempt
I now have 30 out of 40 nodes with records after 33 hours. I’m beginning to think that there is less churn going on in this network. This is because most of the nodes that are late to the party have a sudden influx of records which I think indicates they are receiving replication data rather than writes that are brand new to the network. eg:-
It seems to have slowed, but it started off at roughly the same pace.
The percentage increase over 12-hour periods for my nodes is as follows.
(They also started lower this time, so let’s keep that in mind.)
If the trend continues, it may flatten out, though
My nodes seem to have leveled out at about a third of the RAM previously and I don’t think RAM ever dropped before. It’s also the first time I’ve run multiple nodes and not have any killed. Last test, they started dying early and by the end 18 of 20 had been killed. This time none so far!
I have not had any issues with nodes dying for several tests, but… for some reason I have had 2 die on a SBC this time round.
Haven’t yet had time to look and see if I can figure out why.
Got it done with the .47 client and default batch size. Highlights:
Made payment of 0.127740675 for 8162 chunks
New wallet balance: 299.872259325
Verified 8162 chunks in 710.381986384s
3 chunks were not stored. Repaying them in batches.
Verified 3 chunks in 8.655460618s
1 chunks were not stored. Repaying them in batches.
Failed to fetch 1 chunks. Attempting to repay them.
1 chunks to be checked and repaid if required
Verified 1 chunks in 5.037220578s
Verification complete: all chunks paid and stored
