Cant get new node running

Can somebody help me get my node up and running after i had a hard drive failure?

I installed a new node and getting this message.

ERROR nodestats:cache Get stats query failed {“error”: “context canceled”}
2020-06-14T08:09:10.113-0400 FATAL Unrecoverable error {“error”: “debug: http: Server closed”, “errorVerbose”: “debug: http: Server closed\n\tstorj.io/private/debug.(*Server).Run.func2:108\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

Is it Windows or Linux ? GUI or docker ?

it happens to me too. every time I restart the service on windows 10. it is an installation with gui no docker. I have no other problems nor db or other fail. I just want to point out that in the log the error is not reported as ERROR

Edit:
it happens when I shutdown the service.
I checked the log now

2020-06-01T19:56:39.783+0200 INFO Stop/Shutdown request received.
2020-06-01T19:56:39.956+0200 FATAL Unrecoverable error {“error”: “debug: http: Server closed”, “errorVerbose”: “debug: http: Server closed\n\tstorj.io/private/debug.(*Server).Run.func2:108\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-06-01T19:56:44.585+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}

1 Like

Windows 10 GUI

thank you so much to anybody who helps

Please, show the result of the command (Powershell)

Get-Service storagenode*

Is your node online? If the services above are running, then I would like to recommend you to check your configuration with this checklist:

Running storagenode Storj V3 Storage Node
Running storagenode-upd… Storj V3 Storage Node Updater

Is your node running after that?

If your node OFFLINE, then please, check your configuration with checklist

My ID wasn’t signed. LOL THNX PPL

Of course, I have no mistakes. It restarts and continues without errors. Audits, egress, ingress and more. For two months now I have 3 nodes and also I am already updated to 1.6.3 on all three.

1 Like

But i have a problems?

No, if your node is online, not suspended and not disqualified and its Audit score 100%, all working fine.
I created an internal issue on any case with this bug, but seems it can be ignored at the moment.

Thanks for reply.
Yes, i have audit 100% and not i have others errors in the log.
this errors, anyway, is occured from version 1.4.2.