tried setting up a node first on Windows with the new .msi.
Opened and forwarded ports, let it ran for approx 48 hrs, no contact, node still offline.
Checked with the port checker that the port indeed is open and matches the WAN IP.
Then reinstalled on Windows, nothing changed.
Then I tried a new installation via docker on Ubuntu to see if anything changes, but nope.
Getting this error and can’t seem to get a connection whatever I try.
“Unknown desc = contact: couldn’t connect to client a│t addr: inity.hopto.org:28967 due to internal error”
Don’t have access to that box right now, will paste it later here. But I’m remoted in to the Windows box now, reinstalled the node again, made sure everything looks correct. Getting the same error on Windows now, the exact same error keeps appearing whenever the node is started and it never gets online.
The cli dashboard is neither showing the “neighbourhood” which I’ve seen on some screenshots.
On Windows now after restarting/reinstalling the node log looks like this:
2019-10-15T10:43:00.325+0300 INFO Configuration loaded from: D:\StorjV3_new\Node-installation\config.yaml
2019-10-15T10:43:00.335+0300 INFO Node ID: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr
2019-10-15T10:47:42.384+0300 INFO Stop/Shutdown request received.
2019-10-15T10:47:43.388+0300 FATAL Unrecoverable error {“error”: “rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: error while dialing: dial tcp 127.0.0.1:7778: connectex: No connection could be made because the target machine actively refused it.””}
2019-10-15T10:47:43.748+0300 INFO Configuration loaded from: D:\StorjV3_new\Node-installation\config.yaml
2019-10-15T10:47:43.758+0300 INFO Operator email: gmail@gmail.com
2019-10-15T10:47:43.758+0300 INFO operator wallet: 0xFEeED3762EA30s2sa6E3934E03AE1303e8ae6De5
2019-10-15T10:47:44.472+0300 INFO version running on version v0.23.3
2019-10-15T10:47:44.476+0300 INFO db.migration Database Version {“version”: 25}
2019-10-15T10:47:44.478+0300 INFO contact:chore Storagenode contact chore starting up
2019-10-15T10:47:44.478+0300 INFO piecestore:monitor Remaining Bandwidth {“bytes”: 2000000000000}
2019-10-15T10:47:44.479+0300 INFO bandwidth Performing bandwidth usage rollups
2019-10-15T10:47:44.479+0300 INFO Node 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr started
2019-10-15T10:47:44.479+0300 INFO Public server started on [::]:28967
2019-10-15T10:47:44.479+0300 INFO Private server started on 127.0.0.1:7778
2019-10-15T10:47:44.615+0300 INFO version running on version v0.23.3
2019-10-15T10:47:46.506+0300 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Internal desc = contact: couldn’t connect to client at addr: inity.hopto.org:28967 due to internal error.”}
2019-10-15T10:47:47.545+0300 INFO Configuration loaded from: D:\StorjV3_new\Node-installation\config.yaml
2019-10-15T10:47:47.555+0300 INFO Node ID: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr
2019-10-15T10:49:13.967+0300 ERROR nodestats:cache Get stats query failed {“error”: “node stats service error: rpc error: code = PermissionDenied desc = node not found: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr; node stats service error: rpc error: code = PermissionDenied desc = node not found: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr; node stats service error: rpc error: code = PermissionDenied desc = node not found: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr; node stats service error: rpc error: code = PermissionDenied desc = node not found: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr”, “errorVerbose”: “group:\n— node stats service error: rpc error: code = PermissionDenied desc = node not found: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr\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: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr\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: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr\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: 14B2kuyrk6jv6d2yCq1hYcgFRDazjbZ7w3eUiNdXoLWq1mgzZr\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”}
Actually, this most likely is the interesting error:
FATAL Unrecoverable error {“error”: “rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: error while dialing: dial tcp 127.0.0.1:7778: connectex: No connection could be made because the target machine actively refused it.””}
This is how the logs continue to look on the Windows node:
2019-10-15T11:02:45.972+0300 INFO version running on version v0.23.3
2019-10-15T11:17:45.397+0300 INFO version running on version v0.23.3
2019-10-15T11:32:46.229+0300 INFO version running on version v0.23.3
2019-10-15T11:47:44.480+0300 INFO bandwidth Performing bandwidth usage rollups
2019-10-15T11:47:46.026+0300 INFO version running on version v0.23.3
2019-10-15T11:47:47.382+0300 ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Internal desc = contact: couldn’t connect to client at addr: inity.hopto.org:28967 due to internal error.”}
2019-10-15T12:02:45.566+0300 INFO version running on version v0.23.3
So it seems it’s saying it’s running even though the occasional " ERROR contact:chore pingSatellites failed {“error”: “rpc error: code = Internal desc = contact: couldn’t connect to client at addr: inity.hopto.org:28967 due to internal error.”}" error.
However the node is still offline and seems to be doing nothing even though “running”. Should I just wait or how to proceed…?
Alrighty I managed to find out the problem.
Problem was with my identity files, it seems that my copy to another folder had failed somehow or something, the files were named differently etc. dunno what happened. In any case.
I had them on my original backup, replaced the bad ones I were using and node shows up online! \o/
