Discualification

Node Operators troubleshooting
, ,
1

Hi

I started running a node back in 2021. Unfortunately, I had to move to another place for some time. I did not have the opportunity to run my node back then.
Now I’m back at a stable connection and want to spin up a node.
I know that I fucked up, since I moved the storage and did never come back online again before now.
All data was deleted, since I thought I already had lost all my earnings.

Now I would like to join StorJ for good and sit on a stable 1Gbit connection. I have 10TB of storage I would like to share. But now I have spin up the node I get this message:

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

How can I be qualified again?

2

Hello,
if your node has been disqualified, you have to start all over again.

This means that you also need new identity files. Do not use files from your previous node such as the identity files. Each node has its own identity files.

Just start with Sign up and host a Node on Storj and then follow the documentation.

3

Hi

I did try this when I spin up the new node. I thought I had deleted all data from the old node, but the system did recognize my identifier, and I easily got codes 2 and 3. Without any waiting time.
I did also use the same email as before.

What do I need to do/delete to start over again?

4

Could you provide some more information about your setup? Do you use Windows or Linux? Do you use Docker?

The same E-Mail as before is fine.

If possible, send the last 20 lines of your log file.

5

Yes sure. But im not verry good at CMD /Powershell . I have just used the codes provided in the guides to get it running.

I’m using Windows.

I’m not sure if this is the correct log file you need.

2023-01-31T13:19:14.233+0100 INFO Anonymized tracing enabled {“Process”: “storagenode”}
2023-01-31T13:19:14.337+0100 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2023-01-31T13:19:14.338+0100 INFO Anonymized tracing enabled
2023-01-31T13:19:14.339+0100 INFO Operator email {“Address”: “jespertjoergensen@gmail.com”}
2023-01-31T13:19:14.339+0100 INFO Operator wallet {“Address”: “0x704a74B900374cDA81E4eC37c1fCA80508Bb9f4E”}
2023-01-31T13:19:14.362+0100 INFO db database does not exist {“database”: “info”}
2023-01-31T13:19:14.362+0100 INFO db database does not exist {“database”: “bandwidth”}
2023-01-31T13:19:14.362+0100 INFO db database does not exist {“database”: “orders”}
2023-01-31T13:19:14.362+0100 INFO db database does not exist {“database”: “piece_expiration”}
2023-01-31T13:19:14.362+0100 INFO db database does not exist {“database”: “pieceinfo”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “piece_spaced_used”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “reputation”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “storage_usage”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “used_serial”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “satellites”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “notifications”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “heldamount”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “pricing”}
2023-01-31T13:19:14.363+0100 INFO db database does not exist {“database”: “secret”}
2023-01-31T13:19:14.924+0100 INFO Telemetry enabled {“instance ID”: “1197zJQJMYSaqm7nEsR9CH4KmxRuXZSojHd1kzSto6yokz61sF”}
2023-01-31T13:19:14.924+0100 INFO Event collection enabled {“instance ID”: “1197zJQJMYSaqm7nEsR9CH4KmxRuXZSojHd1kzSto6yokz61sF”}
2023-01-31T13:19:17.310+0100 INFO db.migration Database Created {“version”: 54}
2023-01-31T13:19:17.479+0100 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2023-01-31T13:19:17.937+0100 INFO Stop/Shutdown request received.
2023-01-31T13:19:17.938+0100 ERROR preflight:localtime unable to get satellite system time {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “error”: “context canceled”}
2023-01-31T13:19:17.938+0100 ERROR preflight:localtime unable to get satellite system time {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “error”: “rpc: tcp connector failed: rpc: context canceled”, “errorVerbose”: “rpc: tcp connector failed: rpc: context canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189”}
2023-01-31T13:19:17.938+0100 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2023-01-31T13:19:17.938+0100 INFO bandwidth Performing bandwidth usage rollups
2023-01-31T13:19:17.939+0100 ERROR bandwidth Could not rollup bandwidth usage {“error”: “bandwidthdb: context canceled”, “errorVerbose”: “bandwidthdb: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*bandwidthDB).Rollup:301\n\tstorj.io/storj/storagenode/bandwidth.(*Service).Rollup:53\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/bandwidth.(*Service).Run:45\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-01-31T13:19:17.938+0100 INFO trust Scheduling next refresh {“after”: “5h50m36.819307102s”}
2023-01-31T13:19:17.939+0100 INFO Node 1197zJQJMYSaqm7nEsR9CH4KmxRuXZSojHd1kzSto6yokz61sF started
2023-01-31T13:19:17.939+0100 INFO Public server started on [::]:28967
2023-01-31T13:19:17.939+0100 ERROR nodestats:cache Get pricing-model/join date failed {“error”: “context canceled”}
2023-01-31T13:19:17.939+0100 ERROR gracefulexit:blobscleaner couldn’t receive satellite’s GE status {“error”: “context canceled”}
2023-01-31T13:19:17.939+0100 INFO Private server started on 127.0.0.1:7778
2023-01-31T13:19:17.939+0100 ERROR gracefulexit:chore error retrieving satellites. {“error”: “satellitesdb: context canceled”, “errorVerbose”: “satellitesdb: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*satellitesDB).ListGracefulExits:149\n\tstorj.io/storj/storagenode/gracefulexit.(*Service).ListPendingExits:58\n\tstorj.io/storj/storagenode/gracefulexit.(*Chore).AddMissing:58\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/gracefulexit.(*Chore).Run:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-01-31T13:19:17.939+0100 ERROR collector error during collecting pieces: {“error”: “pieceexpirationdb: context canceled”, “errorVerbose”: “pieceexpirationdb: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceExpirationDB).GetExpired:39\n\tstorj.io/storj/storagenode/pieces.(*Store).GetExpired:537\n\tstorj.io/storj/storagenode/collector.(*Service).Collect:88\n\tstorj.io/storj/storagenode/collector.(*Service).Run.func1:57\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/collector.(*Service).Run:53\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-01-31T13:19:17.939+0100 ERROR piecestore:cache error during init space usage db: {“error”: “piece space used: context canceled”, “errorVerbose”: “piece space used: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceSpaceUsedDB).Init:73\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:81\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-01-31T13:19:18.458+0100 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2023-01-31T13:19:18.459+0100 INFO Anonymized tracing enabled
2023-01-31T13:19:18.460+0100 INFO Operator email {“Address”: “jespertjoergensen@gmail.com”}
2023-01-31T13:19:18.460+0100 INFO Operator wallet {“Address”: “0x704a74B900374cDA81E4eC37c1fCA80508Bb9f4E”}
2023-01-31T13:19:18.989+0100 INFO Telemetry enabled {“instance ID”: “1197zJQJMYSaqm7nEsR9CH4KmxRuXZSojHd1kzSto6yokz61sF”}
2023-01-31T13:19:18.989+0100 INFO Event collection enabled {“instance ID”: “1197zJQJMYSaqm7nEsR9CH4KmxRuXZSojHd1kzSto6yokz61sF”}
2023-01-31T13:19:19.008+0100 INFO db.migration Database Version {“version”: 54}
2023-01-31T13:19:19.532+0100 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2023-01-31T13:19:20.261+0100 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2023-01-31T13:19:20.261+0100 INFO bandwidth Performing bandwidth usage rollups
2023-01-31T13:19:20.261+0100 INFO Node 1197zJQJMYSaqm7nEsR9CH4KmxRuXZSojHd1kzSto6yokz61sF started
2023-01-31T13:19:20.261+0100 INFO Public server started on [::]:28967
2023-01-31T13:19:20.261+0100 INFO Private server started on 127.0.0.1:7778
2023-01-31T13:19:20.261+0100 INFO trust Scheduling next refresh {“after”: “8h1m47.300743321s”}
2023-01-31T13:19:20.261+0100 INFO pieces:trash restore trash started {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”}
2023-01-31T13:19:20.261+0100 INFO pieces:trash restore trash started {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2023-01-31T13:19:20.261+0100 INFO pieces:trash restore trash started {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}
2023-01-31T13:19:20.262+0100 INFO pieces:trash restore trash started {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2023-01-31T13:19:20.262+0100 INFO pieces:trash restore trash started {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2023-01-31T13:19:20.262+0100 INFO pieces:trash restore trash started {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”}
2023-01-31T13:19:25.446+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T13:19:25.502+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T13:19:25.986+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T13:19:26.285+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T13:19:26.935+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T13:19:31.100+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T14:19:20.262+0100 INFO bandwidth Performing bandwidth usage rollups
2023-01-31T14:19:25.502+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T14:19:25.561+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T14:19:25.990+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T14:19:26.091+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T14:19:26.336+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-01-31T14:19:26.899+0100 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “Error”: “contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}

7

Hi @Jesjor2
Please open the config.yaml file

Check the identity.cert-path and identity.key-path variables. Browse to those locations and check the dates on the files… most likely they are old files and if you did create a new identity it was not in this folder.

1 Like
8

Capture

should i delete them?

9

Yes, there’s no need for the old node identity. Then re-run the identity process for the new node.

1 Like
10

Okay thanks for the info.

Let me get this right.

I delete the all files from 2021?
Then I delete Storj app, and rerun the installation with identification.

11

Delete all the files in that identify location.
Delete all databases, folders and files from the Storj data directory.
Uninstall Storj app.
Reboot.
Check identity location and Storj data directory is still empty.
Re-install Storj node and re-run the identity creation process.

1 Like
12

Thank you so much. Everything runs smooth now :slight_smile:

1 Like
13

Now im starting to get wierd Email from StorJ about discualiofication .
First from EU and now South East Asia and saltlake

asia 2
asia 2655×572 26 KB

asia
asia731×525 26.3 KB

salt
salt756×547 26.2 KB

14

These probably are about your previous node: check that the node ID from these e-mails doesn’t match your new node.

This seems related to:

1 Like