I have quite a spread of Storage Costs at the moment:-
AWS Instance - starttime 2023-09-24 morning
9811
Home 1 - starttime 2023-09-22 afternoon
12068
(That’s the one with the dip but then the big increase - screenshot above)
Home 2 - starttime 2023-09-22 afternoon
482844!
That one has a wallet balance of 0.028973577 so I don’t want to mess with it now because it’s making me rich!
Uploaded chunk #43e5e3.. in 15 seconds
Error:
0: Chunks error Failed to get find payment for record: de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8.
1: Failed to get find payment for record: de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8
Location:
sn_cli/src/subcommands/files.rs:297
I’ve kept the client logs if useful
Lines in safe.log that mention that record
Summary
[2023-09-25T17:27:34.469534Z INFO sn_networking] Getting record of de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8 attempts 1/1
[2023-09-25T17:27:45.685597Z INFO sn_networking::event] Query task QueryId(12787) NotFound record de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8 among peers [PeerId(“12D3KooWGTPj5JoAChhoZ1GoiSwmm7nFNtAoMCVQ4z53teER4dYa”>
[2023-09-25T17:30:04.849996Z TRACE sn_client::api] Getting store cost at NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8), with tolerance of 1.5 times the cost
[2023-09-25T17:30:18.783228Z DEBUG sn_networking] send_and_get_responses for Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8)))
[2023-09-25T17:30:18.784029Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: OutboundError(D>
[2023-09-25T17:30:18.784065Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: OutboundError(D>
[2023-09-25T17:30:18.784089Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: OutboundError(D>
[2023-09-25T17:30:18.784112Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: OutboundError(D>
[2023-09-25T17:30:18.784137Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: OutboundError(D>
[2023-09-25T17:30:19.324099Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: Query(GetStoreC>
[2023-09-25T17:30:19.380492Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: Query(GetStoreC>
[2023-09-25T17:30:19.774379Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: Query(GetStoreC>
[2023-09-25T17:30:19.836845Z DEBUG sn_networking] Got response for the req: Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8))), res: Query(GetStoreC>
[2023-09-25T17:30:19.836878Z DEBUG sn_networking] Received all responses for Query(GetStoreCost(NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8)))
[2023-09-25T17:30:19.837039Z WARN sn_client::wallet] Cannot get store cost for NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a87408cb8) with error CouldNotSendMoney("Network E>
[2023-09-25T17:31:04.081076Z TRACE sn_client::file_apis/get_local_payment_and_upload_chunk] Client upload started for chunk: NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb6a874>
[2023-09-25T17:31:09.074094Z WARN sn_client::file_apis/get_local_payment_and_upload_chunk] Failed to get payment proof for chunk: NetworkAddress::ChunkAddress(de47d5(11011110)… - - de47d5e80e72f8ff8c2ba5871b5530446b165ae28e8b150a59ccbb>
Yesterday I was testing how long it is possible to have a node disconnected from the network and it still recover and be fine. I’d been thinking it would be just a couple of minutes so was increasing the time I had the node’s network interface down by a few seconds each time and giving it time to recover in between each test.
Then today I accidentally disconnected everything in the house from the internet for more than an hour while trying to tidy up some cabling…
Both home based nodes came back absolutely fine and are getting records again. This is good news.
There’s no mechanism in place for punishing nodes yet so I think this will change.
It’s an interesting question, how long can a node ‘misbehave’ before it is ostracised. Too short and to many good notes are lost, too long and to many bad nodes remain.
Hmm, what was your CPU doing here? I’m wondering if the self-encryption side of things perhaps broke down or hung, here… cc @qi_ma . Right now we dont have any laaaarge file tests, but we’re in a good place to start looking at this.
Is it longer for each and every batch? I dont think we have a log per batch do we, but it may be good to get one to investigate this more
Ah, yes. I’d not taken into account they might not have implemented punishing a node that isn’t available. But it’s still a good sign that it was able to pickup where it left off.
When there is a way of detecting a node has gone offline and punishing it if it’s out of commission for too long maybe there could be a way of announcing a node is going offline to avoid punishment for OS maintenance like upgrades, disk expansion, etc?
Uploaded 20 chunks in 131.122356906s. Current progress is 3520/4058.
Cannot get store cost for NetworkAddress::ChunkAddress(324627(00110010).. - - 324627c2294cade08335a0408406b28f9465eb79694d0b20b7b31d5cc2fc295e) with error
CouldNotSendMoney("Network Error Not enough store cost prices returned from the network to ensure a valid fee is paid.")
My node has high sounding earnings, 0.712427027
According to Vdash he price at the moment is: 28146939 (1044 - 28146939)
What does that (1044 - 28146939) mean, @happybeing ?