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/):
