My node has some type of problem, the Storj service can’t start. I get a 1067 error. The disk seems to be good, and the log doesn’t says nothing strange:
2020-06-25T13:42:34.938+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2020-06-25T13:42:35.041+0200 INFO Operator email {“Address”: “XXXXX@gmail.com”}
2020-06-25T13:42:35.041+0200 INFO Operator wallet {“Address”: “0xXXXXX”}
yeah the log really should show more…
i checked what came next in the logs by rebooting my node…
so could be a version issue… maybe you are on 1.6.3 in which case you should just try and update…
next it goes to telemetry which i suppose is the online part of the boot… if it reboots and never getting to
2020-06-25T13:04:26.491Z INFO db.migration Database Version {“version”: 39}
if you don’t get that line then it’s most likely an internet connection issue…
we need more log details, we need to know if your node is new or has worked before… we need to know what OS you are using… and that’s most likely the minimum.
internet port routing and dns is a popular issue for new SNO’s
seems like this could be it
Worth a try, after uninstalling make sure the entire folder C:\Program Files\Storj is removed. It could be helpful if you write down the info you entered during install, paths and address and stuff. I guess that would be the equivalent of the run command for GUI nodes.
Please, remove the Windows GUI storagenode, delete the folder "C:\Program Files\Storj".
Enable the Windows firewall and dnscache service.
Please, extract the msi from the archive to the Downloads folder for example then try to install the Windows GUI.
Done. But didn’t worked. The services are installed ok, but they don’t start. If I try to start by hand, I get a 1067 error. I think it’s a generic error. I have tried to change the user that start the service by the machine user, but don’t work.
this is on linux so not sure if this is the same, but i would be very surprised if it wasnt’…
when you enabled debug, it should show you more lines of log… even if it doesn’t get any further…
to me this looks like a connection issue… but i would kinda hate to have to shut down my node and try to boot it without the connection, just to confirm that being the case…
the telemetry enabled is when it goes online… so since it died before that… either your version is wrong or it cannot get access to the internet through the ports it needs to use and thus just reboots to retry again…
mine did that when i had routed the ports wrong… i just don’t remember what the log looked like, that it keeps rebooting without doing anything is a pretty good sign… but yeah enable debug on logs, check your ports and be sure you got the correct version… even tho that might be a bit unlikely… so maybe try the first two …
2020-06-25T13:04:24.668Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2020-06-25T13:04:25.599Z DEBUG Anonymized tracing disabled
2020-06-25T13:04:25.621Z INFO Operator email {"Address": "mail@mail.com"}
2020-06-25T13:04:25.621Z INFO Operator wallet {"Address": "XXXXXXXXXXXXXXXXXXX"}
2020-06-25T13:04:25.738Z DEBUG Version info {"Version": "1.5.2", "Commit Hash": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "Build Timesta$
2020-06-25T13:04:26.413Z DEBUG version Allowed minimum version from control server. {"Minimum Version": "1.3.0"}
2020-06-25T13:04:26.413Z DEBUG version Running on allowed version. {"Version": "1.5.2"}
2020-06-25T13:04:26.414Z INFO Telemetry enabled
Please, change the log.level in the config.yaml to the log.level: debug, save the config (explicitly, not by closing the editor) and restart the storagenode service from the elevated Powershell
Restart-Service storagenode
Wait for a minute and give me 20 last lines from the log