Bivvo
December 13, 2021, 1:10pm
1
Hi there,
from what I have found in the forum, I should not be concerned - right?
2021-12-13T11:13:37.085Z ERROR contact:service ping satellite failed {"Satellite ID": "xxx", "attempts": 1, "error": "ping satellite: failed to dial storage node (ID: xxx) at address abc.domain.net:28967: rpc: dial tcp <ip>:28967: i/o timeout", "errorVerbose": "ping satellite: failed to dial storage node (ID: xxx) at address abc.domain.net:28967: rpc: dial tcp <ip>:28967: i/o timeout\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
The node is online and no other error message occurred - it’s the only one.
Alexey
December 13, 2021, 9:53pm
2
Just make sure that
Bivvo:
abc.domain.net
is updated to your actual WAN IP. For DDNS it could take some time to propagate the changes, especially if you uses the application (for NoIP it’s called DUC) instead of configuration on your router (usually in DDNS section).
Bivvo
December 13, 2021, 10:42pm
3
Understood, thank you. In my case I am using a domain name from my provider, which is updated by the router, linked to that DDNS service, automatically. So it seems to be a single hiccup as the external ip might have been changed. Meaning and confirming, as long as it is and stays with that single message, I don’t have to be concerned (, right?).
Alexey
December 14, 2021, 8:14am
4
If your dashboard shows your node as online and all reputation scores on all satellites 100%, then all should be fine.
Bivvo
December 14, 2021, 5:48pm
5
Hey @Alexey , can you pls interpret, what that means?
2021-12-14T17:44:22.401Z ERROR contact:service ping satellite failed {"Satellite ID": "xxx", "attempts": 1, "error": "ping satellite: check-in ratelimit: node rate limited by id", "errorVerbose": "ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:138\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-12-14T17:47:27.960Z ERROR pieces:trash emptying trash failed {"error": "pieces error: filestore error: context canceled", "errorVerbose": "pieces error: filestore error: context canceled\n\tstorj.io/storj/storage/filestore.(*blobStore).EmptyTrash:154\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).EmptyTrash:310\n\tstorj.io/storj/storagenode/pieces.(*Store).EmptyTrash:367\n\tstorj.io/storj/storagenode/pieces.(*TrashChore).Run.func1:51\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
Alexey
December 15, 2021, 7:44pm
6
The satellites will apply the rate limit to nodes by Id, if they are trying to check-in too often. The storagenode would try to check-in if the satellite said that the node was not reachable after the last check-in.
So, yes, it’s related to your configuration - something partially blocking access from the satellite in question.
Please, check your firewall and make sure that you have not blocking the traffic from said satellite (you should not block any traffic to the port of the node), please …
Found by Search results for 'ping satellite: check-in ratelimit: node rate limited by id' - Storj Community Forum (official)
If I receive this error : ERROR pieces:trash emptying trash failed
Can I empty storage/trash folder on my own. Or data can be rolled back/needs to be deleted by satellite so leave them intact?
Found by Search results for 'pieces:trash emptying trash failed' - Storj Community Forum (official)
Do not hesitate to use search feature
1 Like
it can be helpful!