Disqualified Node after 1yr

Node Operators
1

I just got this hit…
10mths nothing wrong and upgrade to GUI and it goes kabluei

Something happened after Apple Update.
Any views welcomed!

Your node has been disqualified on 118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs . If you have any questions regarding this please check our Node Operators thread on Storj forum.

2020-04-10T20:16:18.096+0800 INFO bandwidth Performing bandwidth usage rollups
2020-04-10T21:16:18.120+0800 INFO bandwidth Performing bandwidth usage rollups
2020-04-10T21:45:29.547+0800 INFO trust Scheduling next refresh {“after”: “6h54m47.151546598s”}
2020-04-10T22:16:18.156+0800 INFO bandwidth Performing bandwidth usage rollups
2020-04-10T22:16:19.235+0800 INFO version running on version v1.1.1
2020-04-10T23:16:18.131+0800 INFO bandwidth Performing bandwidth usage rollups
2020-04-10T23:23:00.931+0800 INFO Stop/Shutdown request received.
2020-04-10T23:23:48.927+0800 INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-04-10T23:23:49.119+0800 INFO Operator email: azrin@azrin.info
2020-04-10T23:23:49.119+0800 INFO operator wallet: 0x162C28E126A97D0009158Fbda0cA93E6e9CC13d0
2020-04-10T23:23:50.909+0800 INFO version running on version v1.1.1
2020-04-10T23:23:51.503+0800 INFO db.migration Database Version {“version”: 33}
2020-04-10T23:23:53.318+0800 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-04-10T23:23:54.400+0800 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-04-10T23:23:54.400+0800 INFO bandwidth Performing bandwidth usage rollups
2020-04-10T23:23:54.457+0800 INFO Node 125hQz4G3WRto2n8tJkjv4qiUoKeFrSSYspkZ818HwbVooHJJuY started
2020-04-10T23:23:54.457+0800 INFO Public server started on [::]:28967
2020-04-10T23:23:54.457+0800 INFO Private server started on 127.0.0.1:7778
2020-04-10T23:23:54.457+0800 INFO trust Scheduling next refresh {“after”: “8h38m21.666607766s”}
2020-04-10T23:23:54.828+0800 INFO version running on version v1.1.1

2

Hello azrin and welcome

If you went from docker to GUI did you make sure to the paths were correct before leaving it to run on its own? I seen many people have this issue when going from docker to GUI because the path was different you needed to set to the storage folder inside with GUI.

Which results in a DQ pretty quickly because none of the data is there.

3

heya

I was on the CLI and until it came I was on 1.0.1 alpha *(dumb me never update to beta) but the node identity etc are intact… unless I messed up.

I rebuild the whole install again…but honestly I trust the CLI more better…

any ideas?

4

Well if your running windows GUI is much more stable then running docker, Its the move from Docker to GUI that can be scary if not done right, because the way GUI pulls the data from is different then docker.

But once you get DQed theres no coming back from it you will have to start over which is unfortunate for you. If you start from scatch with GUI you wont have the same issue again…

5

What U mean by start all over? means clear all the data again etc?
Sorry …lost in the clouds

6

Yes you have to delete all the old node and start over, Once your node is DQed theres no getting it back.

7

in other words… rebuild everything again, identities etc etc
correct…?

8

Yes that is correct, Get a new auth code and redo everything you did when you first got your node. here https://documentation.storj.io/

9

quick one… how do i get rid of the old identity cert??

cant seem to find it.

nvm… found it… in %appdata%\storj

deleted everything there.

thx mate!