Problems with node

Node Operators troubleshooting
,
1

Good morning,

I have some problems with a node with ± 10months.

Suddenly, the node has started to go offline overnight without making any changes to either the node or the network.

I have two nodes in place, one as I say about 10 months and the other 4, so far working perfectly until today.

This is the log that throws me but does not give much information.

2021-04-22T17:08:24.157+0200 ERROR contact:service ping satellite failed {"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 5, "error": "ping satellite error: failed to dial storage node (ID: MY_NODE_ID) at address MY_DDNS:28967: rpc: dial tcp 81.0.38.42:28967: i/o timeout", "errorVerbose": "ping satellite error: failed to dial storage node (ID: MY_NODE_ID) at address MY_DDNS:28967: rpc: dial tcp MY_PUBLIC_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:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

Say that the port and non-IP settings are correct and have not been modified.

I have reinstalled in case it was a version problem but I’m still the same.

Actually i have v1.27.6.

image
image894×145 10.7 KB

Any ideas?

UPDATE:

I can see this logs too

2021-04-22T17:11:49.987+0200	INFO	**Public server started on [::]:28967**
2021-04-22T17:11:49.987+0200	INFO	Private server started on 127.0.0.1:7778
2021-04-22T17:11:49.989+0200	ERROR	**collector	unable to delete piece**	{"Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Piece ID": "B3HHCA6BXDBG3IHNCGYMJREGVG2ROHHORQ4RKNQOOMDPBAPYUWQQ", "error": "pieces error: filestore error: **file does not exist",** "errorVerbose": "pieces error: filestore error: file does not exist\n\tstorj.io/storj/storage/filestore.(*blobStore).Stat:99\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).pieceSizes:239\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).Delete:220\n\tstorj.io/storj/storagenode/pieces.(*Store).Delete:299\n\tstorj.io/storj/storagenode/collector.(*Service).Collect:97\n\tstorj.io/storj/storagenode/collector.(*Service).Run.func1:57\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/collector.(*Service).Run:53\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:81\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:80\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2

Hi @Kyshino,
Please check for open port using both dns name and the public IP - Open Port Check Tool - Test Port Forwarding on Your Router

3

Is your node on Windows or on Linux?

You should check your hard drive for errors. That’s one possible explanation for this.

4

2 posts were split to a new topic: Su nodo ha sido descalificado

5

Is windows, the harddrives are ok.

7

Make sure your ddns is updated.

8

A post was merged into an existing topic: Su nodo ha sido descalificado

9

Is your data on a Storage Spaces Pool? I had this issue with my Windows using Storage Spaces where a Windows Update corrupted part of the data in my pool. Checkdisk kept on finding errors, “fixing” them and losing files every time I ran it. In my case the solution was to copy the files somewhere else and my node started to work again.

10

I have no RAIDs, all is in the same phisic HDD.

Any help @Alexey ?

11

Clearly states that your node is not available from outside.
Please use this checklist to fix the issue:

I personally think that your ISP either changed your external IP and your DDNS updater doesn’t work or your ISP placed you behind their NAT (CGNAT).

Also, maybe you forgot to confirm/extend your DDNS subscription. For example, noip.com requires to confirm your DDNS every month on free account.