Slow traffic node no email and little errors help

Node Operators troubleshooting
1

My node was running fine until 10/01, I suspect a system update of nas (synology update) occurred which removed the buffer size setting and the node got suspended (I think). I can’t seem to be able to reverse this. Unfortunately, I lost the logs at this time. but here are the latest.

here are my logs

image
image923×374 48.5 KB 

{"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "attempts": 1, "error": "ping satellite: rpc: dial tcp: lookup us1.storj.io on 192.168.1.1:53: read udp 172.17.0.6:60940->192.168.1.1:53: i/o timeout", "errorVerbose": "ping satellite: rpc: dial tcp: lookup us1.storj.io on 192.168.1.1:53: read udp 172.17.0.6:60940->192.168.1.1:53: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:114\n\tstorj.io/common/rpc.TCPConnector.DialContext:78\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\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"}

2022-01-29T11:07:40.079Z ERROR contact:service ping satellite failed {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “attempts”: 1, “error”: “ping satellite: rpc: dial tcp: lookup us2.storj.io on 192.168.1.1:53: read udp 172.17.0.6:48221->192.168.1.1:53: i/o timeout”, “errorVerbose”: “ping satellite: rpc: dial tcp: lookup us2.storj.io on 192.168.1.1:53: read udp 172.17.0.6:48221->192.168.1.1:53: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:114\n\tstorj.io/common/rpc.TCPConnector.DialContext:78\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\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”}
2022-01-29T11:07:40.080Z ERROR contact:service ping satellite failed {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “attempts”: 1, “error”: “ping satellite: rpc: dial tcp: lookup eu1.storj.io on 192.168.1.1:53: read udp 172.17.0.6:48014->192.168.1.1:53: i/o timeout”, “errorVerbose”: “ping satellite: rpc: dial tcp: lookup eu1.storj.io on 192.168.1.1:53: read udp 172.17.0.6:48014->192.168.1.1:53: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:114\n\tstorj.io/common/rpc.TCPConnector.DialContext:78\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\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”}
2022-01-29T11:07:40.079Z ERROR contact:service ping satellite failed {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “attempts”: 1, “error”: “ping satellite: rpc: dial tcp: lookup europe-north-1.tardigrade.io on 192.168.1.1:53: read udp 172.17.0.6:53317->192.168.1.1:53: i/o timeout”, “errorVerbose”: “ping satellite: rpc: dial tcp: lookup europe-north-1.tardigrade.io on 192.168.1.1:53: read udp 172.17.0.6:53317->192.168.1.1:53: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:114\n\tstorj.io/common/rpc.TCPConnector.DialContext:78\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\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”}
2022-01-29T11:07:40.080Z ERROR contact:service ping satellite failed {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 1, “error”: “ping satellite: rpc: dial tcp: lookup saltlake.tardigrade.io on 192.168.1.1:53: read udp 172.17.0.6:47683->192.168.1.1:53: i/o timeout”, “errorVerbose”: “ping satellite: rpc: dial tcp: lookup saltlake.tardigrade.io on 192.168.1.1:53: read udp 172.17.0.6:47683->192.168.1.1:53: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:114\n\tstorj.io/common/rpc.TCPConnector.DialContext:78\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\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”}
2022-01-29T11:07:40.080Z ERROR contact:service ping satellite failed {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “attempts”: 1, “error”: “ping satellite: rpc: dial tcp: lookup ap1.storj.io on 192.168.1.1:53: read udp 172.17.0.6:45347->192.168.1.1:53: i/o timeout”, “errorVerbose”: “ping satellite: rpc: dial tcp: lookup ap1.storj.io on 192.168.1.1:53: read udp 172.17.0.6:45347->192.168.1.1:53: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:114\n\tstorj.io/common/rpc.TCPConnector.DialContext:78\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\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”}
2022-02-03T19:51:15.828Z WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Error”: “contact: failed to dial storage node (ID: 12PcUFgbfXYTnFS7GHbMwLbZjnTkZEcmzPEXccM95rcVkbQeEeR) at address xx.tplinkdns.com:28967 using QUIC: rpc: quic: timeout: no recent network activity”}
2022-02-03T19:51:15.958Z WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Error”: “contact: failed to dial storage node (ID: 12PcUFgbfXYTnFS7GHbMwLbZjnTkZEcmzPEXccM95rcVkbQeEeR) at address xxx.tplinkdns.com:28967 using QUIC: rpc: quic: timeout: no recent network activity”}
2022-02-03T19:51:16.050Z WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “Error”: “contact: failed to dial storage node (ID: 12PcUFgbfXYTnFS7GHbMwLbZjnTkZEcmzPEXccM95rcVkbQeEeR) at address xxx.tplinkdns.com:28967 using QUIC: rpc: quic: timeout: no recent network activity”}
2022-02-03T19:51:16.528Z WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “Error”: “contact: failed to dial storage node (ID: 12PcUFgbfXYTnFS7GHbMwLbZjnTkZEcmzPEXccM95rcVkbQeEeR) at address xxx.tplinkdns.com:28967 using QUIC: rpc: quic: timeout: no recent network activity”}

2

Hi @Geelhem
the node is not suspended, the online has just dropped, if you stay online the value will rise.
I have a Qnap and the other day the power went out and I lost the IP settings. Check both the Nas and the router

And if you haven’t already, update the port parameters to include UDP

-p 28967:28967/tcp
-p 28967:28967/udp

3

I used to have 4TB traffic a week before 10/01 now 32 MB.

Also why does it says suspension 100% in the screenshot above if not suspended

image
image923×374 29.9 KB

4

100% is good, below 60% is suspended.

1 Like
5

No one has gotten 4TB in a week on a single node ever also not sure why your bandwidth is pretty low so far this has been a pretty good month for egress.

6

Sorry meant GB lol! I just looked into it more I got no ingress for the last month, so something is definitely up as I get 95% less traffic than last month

7

Please, update the node, use the latest docker run command and configure automatic updates.

2 Likes
8

Thank my watch tower did not seem to be working :slight_smile:

1 Like