Connection refused after moving node

edit: solved i forgot to copy the config.yaml

hi
one of my nodes had a bad HDD but i was able to move the data to a new server (VM with Ubuntu 20.04.5 LTS)
when i start the node (docker) i get this in the log:

2022-09-23T19:13:16.398Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "attempts": 10, "error": "ping satellite: failed to dial storage node (ID: 1ag1X1Uoun183fkVt3KU9CrYofaM9eb4vvxZpaUmekvSVbHVgy) at address x.x.x.x:28967: rpc: tcp connector failed: rpc: dial tcp x.x.x.x:28967: connect: connection refused", "errorVerbose": "ping satellite: failed to dial storage node (ID: 1ag1X1Uoun183fkVt3KU9CrYofaM9eb4vvxZpaUmekvSVbHVgy) at address x.x.x.x:28967: rpc: tcp connector failed: rpc: dial tcp x.x.x.x:28967: connect: connection refused\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-09-23T19:13:17.064Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "attempts": 10, "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:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-09-23T19:13:19.372Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo", "attempts": 10, "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:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-09-23T19:13:20.399Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "attempts": 10, "error": "ping satellite: failed to dial storage node (ID: 1ag1X1Uoun183fkVt3KU9CrYofaM9eb4vvxZpaUmekvSVbHVgy) at address x.x.x.x:28967: rpc: tcp connector failed: rpc: dial tcp x.x.x.x:28967: connect: connection refused", "errorVerbose": "ping satellite: failed to dial storage node (ID: 1ag1X1Uoun183fkVt3KU9CrYofaM9eb4vvxZpaUmekvSVbHVgy) at address x.x.x.x:28967: rpc: tcp connector failed: rpc: dial tcp x.x.x.x:28967: connect: connection refused\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-09-23T19:13:21.040Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 10, "error": "ping satellite: failed to dial storage node (ID: 1ag1X1Uoun183fkVt3KU9CrYofaM9eb4vvxZpaUmekvSVbHVgy) at address x.x.x.x:28967: rpc: tcp connector failed: rpc: dial tcp x.x.x.x:28967: connect: connection refused", "errorVerbose": "ping satellite: failed to dial storage node (ID: 1ag1X1Uoun183fkVt3KU9CrYofaM9eb4vvxZpaUmekvSVbHVgy) at address x.x.x.x:28967: rpc: tcp connector failed: rpc: dial tcp x.x.x.x:28967: connect: connection refused\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-09-23T19:13:25.710Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 10, "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:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

problem i guess is “tcp connector failed: rpc: dial tcp x.x.x.x:28967: connect: connection refused”"
port 28967 is closed but i have no idea why

  • ufw is disabled
  • i checked the IP more than twice
    there was a firewall at hetzner web interface i disabled it but i guess that was only for the physical server running vmware vsphere, the VM where the node is has a single IPv4 for itself

i´m really out of ideas what could cause the port to be closed

do you have node in the same network with same external ip?
did you changed your port forward in router to new internel ip?
it this vm in hetznet server?

no other node, its a new Server and a new VM

forgot to say that i have other docker containers running there, they are working fine and access from outside is working but port 28967 of the storagenode stay closed
no port forwarding, yes its hetzner server, the VM has its own IPv4

im stupid i forgot to copy the config.yaml node is running now

you are not stupid, you are just a human, we all forgot something time to time.

3 Likes