Warning and error logs since updating to latest releasse

carovonoliver · May 5, 2021, 3:33am

Hello all. I’ve gotten the following errors since updating to the latest Storj release about an hour ago.

2021-05-05T03:02:50.454Z        WARN    contact:service Your node is still considered to be online but encountered an error.    {"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Error": "contact: failed to dial storage node (ID: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838 using QUIC: rpc: quic error: Timeout: No recent network activity"}
2021-05-05T03:02:50.779Z        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: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838 using QUIC: rpc: quic error: Timeout: No recent network activity"}
2021-05-05T03:02:50.863Z        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: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838 using QUIC: rpc: quic error: Timeout: No recent network activity"}
2021-05-05T03:02:51.082Z        WARN    contact:service Your node is still considered to be online but encountered an error.    {"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "Error": "contact: failed to dial storage node (ID: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838 using QUIC: rpc: quic error: Timeout: No recent network activity"}
2021-05-05T03:02:51.184Z        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: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838 using QUIC: rpc: quic error: Timeout: No recent network activity"}
2021-05-05T03:03:04.000Z        ERROR   contact:service ping satellite failed   {"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 1, "error": "ping satellite error: failed to dial storage node (ID: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838: rpc: context deadline exceeded", "errorVerbose": "ping satellite error: failed to dial storage node (ID: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838: rpc: context deadline exceeded\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"}
2021-05-05T03:03:15.792Z        ERROR   nodestats:cache Get pricing-model/join date failed     {"error": "payouts service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "payouts service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/storj/storagenode/payouts.(*Endpoint).dial:231\n\tstorj.io/storj/storagenode/payouts.(*Endpoint).GetAllPaystubs:106\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:81\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:261\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run:80\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"}
2021-05-05T03:03:25.002Z        ERROR   contact:service ping satellite failed   {"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 2, "error": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:152\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\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:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-05-05T03:03:47.003Z        ERROR   contact:service ping satellite failed   {"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 3, "error": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:152\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\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:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-05-05T03:04:11.004Z        ERROR   contact:service ping satellite failed   {"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 4, "error": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:152\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\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:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-05-05T03:04:39.006Z        ERROR   contact:service ping satellite failed   {"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 5, "error": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "ping satellite error: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:152\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\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:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-05-05T03:05:02.358Z        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: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838 using QUIC: rpc: quic error: Timeout: No recent network activity"}
2021-05-05T03:06:36.889Z        ERROR   nodestats:cache payouts err     {"satellite": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2021-05-05T03:06:39.597Z        ERROR   nodestats:cache Get held amount query failed    {"error": "payouts service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "payouts service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/storj/storagenode/payouts.(*Endpoint).dial:231\n\tstorj.io/storj/storagenode/payouts.(*Endpoint).GetPaystub:56\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheHeldAmount.func1:204\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:261\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheHeldAmount:196\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func3:137\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-05-05T03:07:27.714Z        ERROR   nodestats:cache Get stats query failed  {"error": "node stats service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "node stats service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/storj/storagenode/nodestats.(*Service).dial:155\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetReputationStats:66\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats.func1:154\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:261\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats:153\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:120\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"}

I’m still getting traffic to my node though majority of it is coming from the Saltlake satellite. Is the warning and error logs something I should address? Or are those logs normal and there’s nothing I should be worried about?

Stob · May 5, 2021, 11:38am

Breaking down the errors:

WARN    contact:service Your node is still considered to be online but encountered an error.    {"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Error": "contact: failed to dial storage node (ID: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838 using QUIC: rpc: quic error: Timeout: No recent network activity

These relate to UDP port forwarding testing - Experimenting with UDP based protocols. There’s no need to ‘fix’ yet as this is just for testing but may be requested in the future.

ERROR   contact:service ping satellite failed   {"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 1, "error": "ping satellite error: failed to dial storage node (ID: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838: rpc: context deadline exceeded", "errorVerbose": "ping satellite error: failed to dial storage node (ID: 1XtserY2gWe4q8TafVMsa5bLSnZcncY4EDMqBagqpYigRy4FEF) at address carovonoliver-49838.portmap.host:49838: rpc: context deadline exceeded\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"}

This suggests the DDNS/portmap name resolution had a blip. It was only the first attempt, so nothing to be too worried about. It could also be related the satellite outage mentioned below.

2021-05-05T03:06:36.889Z        ERROR   nodestats:cache payouts err     {"satellite": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2021-05-05T03:06:39.597Z        ERROR   nodestats:cache Get held amount query failed    {"error": "payouts service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "payouts service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/storj/storagenode/payouts.(*Endpoint).dial:231\n\tstorj.io/storj/storagenode/payouts.(*Endpoint).GetPaystub:56\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheHeldAmount.func1:204\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:261\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheHeldAmount:196\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func3:137\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-05-05T03:07:27.714Z        ERROR   nodestats:cache Get stats query failed  {"error": "node stats service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout", "errorVerbose": "node stats service error: unable to connect to the satellite 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE: rpc: dial tcp 35.236.51.151:7777: i/o timeout\n\tstorj.io/storj/storagenode/nodestats.(*Service).dial:155\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetReputationStats:66\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats.func1:154\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:261\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats:153\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:120\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"}

I haven’t seen these errors before but it looks to coincide with an outage for the saltlake satellite (http://storjnet.info/):

carovonoliver · May 7, 2021, 2:05am

Thanks! Since it’s been a full 24 hours and my node is still working fine I think it’s safe to assume that the node doesn’t have any issues.

wildraven · June 9, 2021, 8:04pm

my node is starting to give some errors and to restart every 20-30 min

2021-06-09T23:00:11.623+0300 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: 12HDYdp9Gcf9GsbH1Cy5nAq1GgWUjoGh55LEudx7hc8e3MU9nwr) at address updrv.go.ro:28967 using QUIC: rpc: quic: Timeout: No recent network activity”}

any ideea what is with this error ?

Alexey · June 9, 2021, 8:11pm

A post was split to a new topic: The file or directory is corrupted and unreadable

jammerdan · June 9, 2021, 8:24pm

I am seeing different errors on different nodes suddenly:

Get held amount query failed#011{"error": "payouts service: context canceled"}

ping satellite: context canceled

ERROR   nodestats:cache      Get held amount query failed    {"error": "payouts service: context canceled"

Alexey · June 9, 2021, 8:28pm

They all related to the connectivity. Is it the same router?

jammerdan · June 9, 2021, 8:30pm

No, 3 different locations. All at the same time. It is weird.

JJ28 · July 13, 2021, 7:50pm

Hi,

Can someone help with this warning I am getting please? Has been happening for aboout 3 days. Running latest version, ports are open, have rebooted system. I have another node running with a different IP and Port, and it is not recieving any warnings. From what I can see it is only happening on 4 of thee satellites, not all of them.

TIA

021-07-13T19:39:03.301Z 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: 12ngdngJKWJHCTxTmKij6M8TqREyoFnbTQeYdtEVQSF5jL34koJ) at address jasonhenley.no-ip.info:28967 using QUIC: rpc: quic: timeout: no recent network act
ivity”}
2021-07-13T19:39:03.643Z WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”,
“Error”: “contact: failed to dial storage node (ID: 12ngdngJKWJHCTxTmKij6M8TqREyoFnbTQeYdtEVQSF5jL34koJ) at address jasonhenley.no-ip.info:28967 using QUIC: rpc: quic: timeout: no recent network act
ivity”}
2021-07-13T19:39:03.766Z 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: 12ngdngJKWJHCTxTmKij6M8TqREyoFnbTQeYdtEVQSF5jL34koJ) at address jasonhenley.no-ip.info:28967 using QUIC: rpc: quic: timeout: no recent network acti
vity”}
2021-07-13T19:39:03.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: 12ngdngJKWJHCTxTmKij6M8TqREyoFnbTQeYdtEVQSF5jL34koJ) at address jasonhenley.no-ip.info:28967 using QUIC: rpc: quic: timeout: no recent network act
ivity”}
2021-07-13T19:39:04.019Z 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: 12ngdngJKWJHCTxTmKij6M8TqREyoFnbTQeYdtEVQSF5jL34koJ) at address jasonhenley.no-ip.info:28967 using QUIC: rpc: quic: timeout: no recent network acti
vity”}
2021-07-13T19:39:06.246Z WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”,
“Error”: “contact: failed to dial storage node (ID: 12ngdngJKWJHCTxTmKij6M8TqREyoFnbTQeYdtEVQSF5jL34koJ) at address jasonhenley.no-ip.info:28967 using QUIC: rpc: quic: timeout: no recent network act
ivity”}

Stob · July 14, 2021, 9:03am

Hi @JJ28,

QUIC refers to the implementation of UDP connections to storagenodes. There are a few threads in the forum which discuss it but the short version is that it’s still in testing, isn’t required yet and you can currently ignore the warning. If you would like to remove the warning from being logged then you have to add UDP port forwarding in the same way as TCP port forwarding is currently enabled to your node.

edit - added ‘yet’ and ‘currently’

littleskunk · July 14, 2021, 11:58am

Please don’t mix up the different ongoing tests. QUIC might not be the way to go but at the current stage I would say it is safe to say we will pick one out of different UDP options. Please don’t ignore the warning because later down the road it will get a requirement. This warning is there to make the transasition as seamless as possible. You can ignore the warning for a few days but please fix it better sooner than later.

Stob · July 14, 2021, 12:28pm

I have made some edits to my post but your indication that it will be a requirement isn’t something I’ve seen posted from StorJ before.

edit - i found this…

Alexey · October 16, 2021, 10:50am

A post was split to a new topic: I noticed my suspension score dropped on Saltlake