Second Node seems unable to connect

Node Operators troubleshooting
,
1

I created a second node using StorJ Toolbox

Now my first node runs fine but the second node seems unable to connect to the network, I see the following errors

2020-04-25T02:24:59.958+0100	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "attempts": 1, "error": "ping satellite error: context canceled", "errorVerbose": "ping satellite error: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:130\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:87\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:90\n\tstorj.io/common/sync2.(*Cycle).Start.func1:69\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-04-25T02:25:00.054+0100	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "attempts": 1, "error": "ping satellite error: context canceled", "errorVerbose": "ping satellite error: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:130\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:87\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:90\n\tstorj.io/common/sync2.(*Cycle).Start.func1:69\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-04-25T02:25:00.066+0100	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW", "attempts": 1, "error": "ping satellite error: context canceled", "errorVerbose": "ping satellite error: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:130\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:87\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:90\n\tstorj.io/common/sync2.(*Cycle).Start.func1:69\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-04-25T02:25:00.081+0100	INFO	version	running on version v1.1.1
2020-04-25T02:25:00.229+0100	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "attempts": 1, "error": "ping satellite error: context canceled", "errorVerbose": "ping satellite error: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:130\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:87\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:90\n\tstorj.io/common/sync2.(*Cycle).Start.func1:69\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-04-25T02:25:00.333+0100	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 1, "error": "ping satellite error: context canceled", "errorVerbose": "ping satellite error: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:130\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:87\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:90\n\tstorj.io/common/sync2.(*Cycle).Start.func1:69\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-04-25T02:25:00.689+0100	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 1, "error": "ping satellite error: context canceled", "errorVerbose": "ping satellite error: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:130\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:87\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:90\n\tstorj.io/common/sync2.(*Cycle).Start.func1:69\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

Both nodes are running on the same Windows 10 machine.

2

@Vadim please take a look ^

3

What settins did you used? and update to 1.3.3

4

My config for the second node is almost the same as the 1st

console.address: 127.0.0.1:14003
contact.external-address: nymode.ddns.net:28969
identity.cert-path: C:\Users\me\AppData\Roaming\Storj\Identity2\storagenode\identity.cert
identity.key-path: C:\Users\me\AppData\Roaming\Storj\Identity2\storagenode\identity.key
log.level: info
log.output: winfile:///C:\Program Files\Storj1\Storage Node\\storagenode.log
operator.email: xxxx@gmail.com
operator.wallet: 0xaC3Ec9
preflight.local-time-check: false
server.address: :28969
server.debug-log-traffic: false
server.private-address: 127.0.0.1:7779
storage.allocated-bandwidth: 16.0 TB
storage.allocated-disk-space: 4.0 TB
storage.path: E:\Storj

The only thing I really changed was the preflight.local-time-check, with this set to true it was failing to start up due to failure to get time from the nodes. Presumably for similar reasons to the above.

5

Well tried deleting my config and recreating it from my working config and it seems to start now, nothing obviously different

6

Perhaps encoding. Can you compare with CLI tools such as a diff (in the WSL)?

7

It’s a pc I only really use for media so don’t have any dev tools on it. I would have done otherwise, I’ve deleted the offending config file now

1 Like