Newly created node is offline

Node Operators troubleshooting
,
1

Hello,

I previously had a node that got disqualified, due to database corruption. I created a new node, with a new identity. The new node was created yesterday, and it still is offline. Port forwarding on my router seems correct.

Node version is 1.3.3
This is a Linux docker node on Raspberry Pi

2020-05-19T18:33:52.655Z INFO tracing disabled
2020-05-19T18:33:53.296Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-05-19T18:33:53.301Z INFO tracing disabled
2020-05-19T18:33:53.310Z INFO Operator email {“Address”: “XXX@gmail.com”}
2020-05-19T18:33:53.311Z INFO Operator wallet {“Address”: “0x…”}
2020-05-19T18:33:55.639Z INFO db.migration Database Created {“version”: 36}
2020-05-19T18:33:56.561Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-05-19T18:34:06.610Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-05-19T18:34:06.611Z INFO bandwidth Performing bandwidth usage rollups
2020-05-19T18:34:06.622Z INFO trust Scheduling next refresh {“after”: “6h44m36.910068681s”}
2020-05-19T18:34:06.613Z INFO Node 127q1bcJUdF8uYD32r6AdA6SpUDzTXzyFT877YH79SqjxZTEMqY started
2020-05-19T18:34:06.624Z INFO Public server started on [::]:28967
2020-05-19T18:34:06.624Z INFO Private server started on 127.0.0.1:7778
2020-05-19T18:34:12.131Z ERROR nodestats:cache Get pricing-model/join date failed {“error”: “heldamount service error: node not found: 127q1bcJUdF8uYD32r6AdA6SpUDzTXzyFT877YH79SqjxZTEMqY”, “errorVerbose”: “heldamount service error: node not found: 127q1bcJUdF8uYD32r6AdA6SpUDzTXzyFT877YH79SqjxZTEMqY\n\tstorj.io/storj/storagenode/heldamount.(*Service).GetAllPaystubs:132\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:78\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:244\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run:77\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func1:56\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-05-19T19:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-19T20:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-19T21:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-19T22:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-19T23:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-20T00:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-20T01:18:44.385Z INFO trust Scheduling next refresh {“after”: “6h52m56.882035877s”}
2020-05-20T01:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-20T02:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-20T03:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-20T04:34:06.612Z INFO bandwidth Performing bandwidth usage rollups
2020-05-20T05:34:06.612Z INFO bandwidth Performing bandwidth usage rollups

2

Is this Windows or Linux node ? If its Windows is it docker or GUI ?

3

Linux docker node on Raspberry Pi

4

Did you make sure you deleted all files of your old node ? These are storage and identity folders.

5

It turns out there was a certain number of networking issues:

  1. From inside the container it was not possible to contact satellites on port 7777, but was possible to contact public web servers on port 80
  2. I had configured port 28968 for incoming connections, which was apprently done correctly, but probably caused some issue
2 Likes