ERROR contact:chore pingSatellites failed

[CaptainInt]

Hello,

I am running one Windows Node perfeclty, but having issues with another one (Different public IP, different Subnet etc.)

The log shows following:

|2019-10-19T09:48:52.014+0200|ERROR|contact:chore|pingSatellites failed|{"error": "rpc error: code = Internal desc = contact: couldn't connect to client at addr: MYIP:28967 due to internal error."}|
|---|---|---|---|---|
|2019-10-19T09:52:28.763+0200|ERROR|nodestats:cache|Get stats query failed|{"error": "node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR; node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR; node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR; node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR", "errorVerbose": "group:\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetReputationStats:73\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats.func1:108\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats:107\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:79\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetReputationStats:73\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats.func1:108\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats:107\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:79\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetReputationStats:73\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats.func1:108\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats:107\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:79\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetReputationStats:73\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats.func1:108\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheReputationStats:107\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:79\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}|
|2019-10-19T09:53:48.991+0200|ERROR|nodestats:cache|Get disk space usage query failed|{"error": "node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR; node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR; node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR; node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR", "errorVerbose": "group:\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetDailyStorageUsage:112\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage.func1:130\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage:129\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:91\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetDailyStorageUsage:112\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage.func1:130\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage:129\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:91\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetDailyStorageUsage:112\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage.func1:130\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage:129\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:91\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n--- node stats service error: rpc error: code = PermissionDenied desc = node not found: 1e8qGMDM7Hs36YnB6gktGRsHCZdQ6Hwue8T38nEYj7XMgBcfbR\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetDailyStorageUsage:112\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage.func1:130\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:170\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage:129\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:91\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/internal/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}|

What is wrong?

[Alexey]

Your second node is offline.
Please, check its identity:

(sls BEGIN $env:AppData\Storj\Identity\storagenode\ca.cert).count
(sls BEGIN $env:AppData\Storj\Identity\storagenode\identity.cert).count

The signed identity must return 2 and 3 respectively.
If your identity is not signed, you should sign it with a second one-time authorization token. To receive a new one you should subscribe to the waitlist with a different email address.

[Ruskiem]

Got same problem, my identity is authorized.
Win10pro, brand new Windows GUI installation, identity created and signed before align with the documentation.
Node is ONLINE in localhost:14002, but he gets some errors, and no traffic:

Edit: lol what happend, i check localhost:14002 and it was offline, so i portchecked again and it was reachable, then i see node started being ONLINE and started doin some traffic, lol, does that means the new node need some plumbing with port signal to help him start? lol

EDIT2: he is ONLINE but strugling with that:
“ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}”

EDIT3: confirmed if i refresh localhost:14002 after some time, its shows its offline again, and nothing changed, internet connection is still.

Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2019-10-23T21:21:10.305+0200 INFO Operator email: cenzoredbyruskiem@gmail.com
2019-10-23T21:21:10.305+0200 INFO operator wallet: cenzoredbyruskiem
2019-10-23T21:21:11.008+0200 INFO version running on version v0.23.5
2019-10-23T21:21:11.016+0200 INFO db.migration Database Version {“version”: 25}
2019-10-23T21:21:11.018+0200 INFO contact:chore Storagenode contact chore starting up
2019-10-23T21:21:11.018+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-23T21:21:11.021+0200 INFO Node 1EH8VzKXkt1hVgQh5e7FMmrHMLiuYuUr3XYDFvibaxacUmzQ1i started
2019-10-23T21:21:11.021+0200 INFO Public server started on [::]:20780
2019-10-23T21:21:11.021+0200 INFO Private server started on 127.0.0.1:7778
2019-10-23T21:21:11.022+0200 INFO piecestore:monitor Remaining Bandwidth {“bytes”: 45000000000000}
2019-10-23T21:21:11.168+0200 INFO version running on version v0.23.5
2019-10-23T21:25:55.192+0200 INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2019-10-23T21:25:55.265+0200 INFO Operator email: cenzoredbyruskiem@gmail.com
2019-10-23T21:25:55.265+0200 INFO operator wallet: cenzoredbyruskiem
2019-10-23T21:26:07.317+0200 ERROR version Failed to do periodic version check: Get https://version.storj.io: dial tcp: lookup version.storj.io: no such host
2019-10-23T21:26:07.485+0200 INFO db.migration Database Version {“version”: 25}
2019-10-23T21:26:07.506+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-23T21:26:07.506+0200 INFO Node 1EH8VzKXkt1hVgQh5e7FMmrHMLiuYuUr3XYDFvibaxacUmzQ1i started
2019-10-23T21:26:07.506+0200 INFO Public server started on [::]:20780
2019-10-23T21:26:07.506+0200 INFO Private server started on 127.0.0.1:7778
2019-10-23T21:26:07.506+0200 INFO contact:chore Storagenode contact chore starting up
2019-10-23T21:26:07.554+0200 INFO piecestore:monitor Remaining Bandwidth {“bytes”: 45000000000000}
2019-10-23T21:26:08.284+0200 INFO version running on version v0.23.5
2019-10-23T21:41:08.315+0200 INFO version running on version v0.23.5
2019-10-23T21:56:08.240+0200 INFO version running on version v0.23.5
2019-10-23T22:11:08.210+0200 INFO version running on version v0.23.5
2019-10-23T22:26:07.520+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-23T22:26:08.214+0200 INFO version running on version v0.23.5
2019-10-23T22:36:08.866+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-23T22:41:08.230+0200 INFO version running on version v0.23.5
2019-10-23T22:56:08.240+0200 INFO version running on version v0.23.5
2019-10-23T23:11:08.197+0200 INFO version running on version v0.23.5
2019-10-23T23:26:07.507+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-23T23:26:08.255+0200 INFO version running on version v0.23.5
2019-10-23T23:36:08.886+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-23T23:41:08.221+0200 INFO version running on version v0.23.5
2019-10-23T23:56:08.344+0200 INFO version running on version v0.23.5
2019-10-24T00:11:08.213+0200 INFO version running on version v0.23.5
2019-10-24T00:26:07.538+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-24T00:26:08.241+0200 INFO version running on version v0.23.5
2019-10-24T00:34:58.081+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-24T00:35:11.653+0200 ERROR telemetry failed sending report: lookup collectora.storj.io: no such host
2019-10-24T00:41:08.258+0200 INFO version running on version v0.23.5
2019-10-24T00:56:08.329+0200 INFO version running on version v0.23.5
2019-10-24T01:11:08.252+0200 INFO version running on version v0.23.5
2019-10-24T01:26:07.517+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-24T01:26:08.262+0200 INFO version running on version v0.23.5
2019-10-24T01:36:08.857+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-24T08:40:04.218+0200 INFO Interrogate request received.
2019-10-24T08:40:30.421+0200 INFO version running on version v0.23.5
2019-10-24T08:41:07.680+0200 INFO version running on version v0.23.5
2019-10-24T08:56:08.251+0200 INFO version running on version v0.23.5
2019-10-24T09:11:08.269+0200 INFO version running on version v0.23.5
2019-10-24T09:25:29.338+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-24T09:26:07.506+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-24T09:26:08.237+0200 INFO version running on version v0.23.5
2019-10-24T09:35:30.682+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-24T09:41:08.244+0200 INFO version running on version v0.23.5
2019-10-24T09:45:31.998+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-24T09:56:08.186+0200 INFO version running on version v0.23.5
2019-10-24T10:11:08.950+0200 INFO version running on version v0.23.5
2019-10-24T10:26:07.519+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-24T10:26:08.164+0200 INFO version running on version v0.23.5
2019-10-24T10:36:08.859+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-24T10:41:08.231+0200 INFO version running on version v0.23.5
2019-10-24T10:56:08.212+0200 INFO version running on version v0.23.5
2019-10-24T11:11:08.216+0200 INFO version running on version v0.23.5
2019-10-24T11:26:07.515+0200 INFO bandwidth Performing bandwidth usage rollups
2019-10-24T11:26:08.232+0200 INFO version running on version v0.23.5
2019-10-24T11:36:08.864+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Unavailable desc = transport is closing”}
2019-10-24T11:41:08.249+0200 INFO version running on version v0.23.5
2019-10-24T11:56:08.206+0200 INFO version running on version v0.23.5
2019-10-24T12:11:08.216+0200 INFO version running on version v0.23.5

EDIT4: wtf is he doin? now i see that error got some more details after i furiously restarted that windows 2 times:
"
2019-10-24T19:32:36.850+0200 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Internal desc = contact: lookup 24comps.ddns.net on 10.127.0.10:53: read udp 10.127.0.10:54995->10.127.0.10:53: read: connection refused”}
"
now he included my ddns.
which was in config file from the begining,
and why its udp, been said node use only tcp

EDit5: seems like it was something with noip.com - it wasnt forwarding the port lol (its not the 1st time they cause troubles), i created new domain and this one seems to work, will ses over nigh how it goes

EDIT6: yes it was something between me and noip.com, new domain works, and since then the node is operating successfully.

[Alexey]

noip only keeps your DDNS. The port is forwarding by router.
So, I would recommend to start from there.

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

[Ruskiem]

but port was forwarded, on my ip it was reachable from internet, that was my mistake to check by ip, i forgot to check by my noip domain, on whitch the port was closed.

[noknan89]

i found new issue about “contact:chore pingSatellites failed”

my config

[Alexey]

Please, check your address and port on https://www.yougetsignal.com/tools/open-ports/

[subwolf]

So I’ve been doing some testing and updating of my linux node at home, I’ve managed to mess things up pretty badly. I have a wired connection on 192.168.1.46 and a wireless connection that I have disabled currently. I’m using the no-ip service to get an external address, which is specified in the docker startup options.

When I start it up, I get this message:

2019-10-24T17:42:44.869Z        INFO    version running on version v0.23.5
2019-10-24T17:42:46.142Z        ERROR   contact:chore   pingSatellites failed   {"error": "rpc error: code = Internal desc = contact: couldn't connect to client at addr: subwolf.ddns.net:28967 due to internal error."}

If I try to connect from another server to that address and port:

subwolf@localhost:/ext$ telnet subwolf.ddns.net 28967
Trying 2.98.183.99...
telnet: Unable to connect to remote host: Connection refused

If I perform a netstat:

root@subwolf-tk:/media/subwolf/Games/storj# netstat -a | grep 28967
tcp6       0      0 [::]:28967              [::]:*                  LISTEN     

I’m probably missing something obvious?

[subwolf]

I verified the port is forwarded in the router as well, so very confused.

[Odmin]

Please check your router ip, it should be equal your ddns name ip.

[Realistickz]

my system hang off on 0.25.1…
no uploads, no downloads…

no satelits founds… all down, but dashboard say its all right.
i have restartet windows 10, but logfile says no satelites
… Ping satelites failed
come near an update?

i think tomorrow i will shut down…
browser is firefox and i do strg + F5

[Alexey]

Hello @Realistickz,
Welcome to the forum!

Please, check everything from this check list:

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

[Realistickz]

It worked before the update so everything. 14 hours ago no connection to the satellites was possible.
For an hour everything works perfectly again. thanks

[aquarat]

I just had the same problem. Got an email saying my node was offline. I edited config.yaml and fixed the IP. I also added the port, which wasn’t present originally. My node is working again yay. Thanks

[Alexey]

Hello @aquarat,
Welcome to the forum!

If your public IP is dynamic, please, use the DDNS address instead. In this case the address will be updated automatically: https://documentation.storj.io/dependencies/port-forwarding#setup-dynamic-dns-service-hostname-configuration