Hi - my server just shut down and wont boot up - what do i do?
I looked in the wrong config file - i fixed it.
Just dont understand how my config got mixed up tho.
Still manual boot works just fine. i can find the service in windows services but cant start it from there. I can start i from CMD. If i restart the PC storj does not boot back up.
If you run the storagenode binary from the command line, you should provide options to specify correct location for config file with --config-dir option, identity location with --identity-dir option.
Without options it will create a config file, your storage location in %AppData% on your system disk by default. Unlikely you wants this.
If your node were running as a service, it used the config file from "C:\Program Files\Storj\Storage Node\config.yaml", and your storage location likely were on a different disk, not in %AppData%. So now your node under a risk of failing audits and on the way to disqualification, because a previous data is on other location.
When you figure out, where your previous location is (it is a storage.path option in the config file), you likely will need to merge blobs folder from the %AppData%\Storj\Storagenode with blobs folder in the correct location without overwrite of existing files, so add only new ones. This will allow your node to survive, when you fix the underlying issue.
Please try to start the service and post 20 last lines from your logs: How do I check my logs? | Storj Docs
So what you mean is: when i open CMD and type “storagenode run” i need additional parameters? i thought they where just in my config file?
I do belive that my storage is being saved to the correct spot atm.
I see blobs have been edited or added to the correct drive - so i think “both” config files saves it to the right place?
i honestly have no clue what to do to fix my issue.
Im just gonna post my logs:
Yes, you must do so, unless you did setup your node without an installation wizard and used default location for config file (%AppData%\Storj\Storagenode) and default location for identity (%AppData%\Storj\Identity\storagenode).
If you used a wizard, then started a node from the command line without options - it will use the default ones and creates config file, storage location in %AppData% as you showed here
And this location is definitely did not match this one
So, if you continue run your storagenode from the command line, it will store data in a different location and eventually will be disqualified for losing a previous data.
From your next screenshots I can assume that you provided a different path to the wizard for storagenode installation location, so your command to see logs will be
Get-Content -Tail 20 C:\Storj\storagenode.log
And the correct config file is C:\Storj\config.yaml
From your screenshot of the text (please do not do that next time, post the text instead of picture) I can see, that something stopped the service.
Is the storagenode-updater service running? If so, check its logs:
Get-Content -Tail 20 C:\Storj\storagenode-updater.log
From your messed setup I can guess, that you now have at least three wrong storage locations:
- in
%AppData%, the folderstorage - In
C:\Storj, the folderstorage - In some disk with folder
StorjData(this one seems the initial location)
Yes, I mean that.
Please add another option --log.output stderr, we will see, what’s wrong with this config file.
I see. This is encoding with BOM, so you have used a regular Notepad to edit your config and it broken your config file.
Open this config file with a Notepad++ and save with encoding UTF8 without BOM.
I will open in notepad++ and try
it seems to allready be?
Ok, this is better.
Now please delete the file C:\Storj\trust-cache.json and try to start the service, then check your logs