Should I just delete all the Storj1 folders (on C drive and I drive) and start over? If yes, how to delete the storagenode1 service?
I would delete and start over doing anything as admin. Make sure with sc command there is nothing left from previous attempts.
sc delete storagenode1
SC command? in Powershell (admin)?
if you want to delete service, sc.exe delete storagenode1 in cmd as admin
when install please avoid spaces in folder, also indentity for example on C:\indentity1
increment number for every node
what happens if start over but do not delete thestoragenode1 service?
Service names must be unique, so you can not install it twice.
That may be the problem. I did not increment the identity folder to I:\identity1. Is that still necessary as it is on the I drive and there are no other identity folder on that drive?
Name of identity folder doesn’t matter as long as there is an unused and signed identity.
1 Like
Has my identity been used if the setup never completed correctly?
you need to increment it only if thay in 1 folder, only to not mix them, it is real problem when you have lot of nodes. Also better to delete service, and folder in Program files, then it will make all new.
ok. I am going to start over and delete service, folders and get a new signed identity.
Install completed successfully. However the node show offline and miss configured. I check the config file and it has this -
server.address: :46016
Is that wrong?. Should it be
server.address: :28968
Changes to 28968 and now it is online and OK
Great news.
Thanks everyone for your help. Much appreciated
3 Likes
Now working on a 2nd node for a different PC. I thought I understood the Windows GUI Toolbox based on succeeding (after lots of help) with a second node for a different PC 5 days ago. But this time I received the same service error after the toolbox said the install was successful. I triple checked the config file, port forwardings, and firewall rules. They all look ok. here is the log entry -
2024-06-27T21:14:25-05:00 INFO Configuration loaded {“Location”: “C:\Program Files\Storj0\Storage Node\config.yaml”}
2024-06-27T21:14:25-05:00 INFO Anonymized tracing enabled
2024-06-27T21:14:25-05:00 INFO Operator email {“Address”: “xxxxxxxxxxxxxxxxxxx”}
2024-06-27T21:14:25-05:00 INFO Operator wallet {“Address”: “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”}
2024-06-27T21:14:25-05:00 ERROR failure during run {“error”: “Error opening database on storagenode: group:\n— CreateFile E:\Storjv3node9\blobs: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\temp: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\trash: The system cannot find the file specified.”, “errorVerbose”: “Error opening database on storagenode: group:\n— CreateFile E:\Storjv3node9\blobs: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\temp: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\trash: The system cannot find the file specified.\n\tmain.cmdRun:67\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:393\n\tstorj.io/common/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tstorj.io/common/process.ExecWithCustomConfig:72\n\tstorj.io/common/process.Exec:62\n\tmain.(*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78”}
2024-06-27T21:14:25-05:00 FATAL Unrecoverable error {“error”: “Error opening database on storagenode: group:\n— CreateFile E:\Storjv3node9\blobs: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\temp: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\trash: The system cannot find the file specified.”, “errorVerbose”: “Error opening database on storagenode: group:\n— CreateFile E:\Storjv3node9\blobs: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\temp: The system cannot find the file specified.\n— CreateFile E:\Storjv3node9\trash: The system cannot find the file specified.\n\tmain.cmdRun:67\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:393\n\tstorj.io/common/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tstorj.io/common/process.ExecWithCustomConfig:72\n\tstorj.io/common/process.Exec:62\n\tmain.(*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78”}
New signed identity was created before running the toolbox and moved to the identity folder E:\identity
From the config file -
console.address: localhost:14003
contact.external-address: cryptoforall.ddns.net:46017
identity.cert-path: E:\Identity\identity.cert
identity.key-path: E:\Identity\identity.key
log.output: winfile:///C:\Program Files\Storj0\Storage Node\storagenode.log
server.address: :28968
server.private-address: 127.0.0.1:7779
storage.allocated-disk-space: 3.5TB
storage.path: E:\Storjv3node9
Storage2.Database-Dir: E:\Storjv3node9\
The service was created - storagenode0
Storjv3node9 folder is empty
I’m stumped. Your help (again) is much appreciated.
This PC already has ~6TB of used space on node 1 so switching to Ubuntu is a no go. I have several other Windows PCs with space to add more drives so the toolbox looked promising. Now I’m not so sure. I do have 1 low power (2 cores, 2GB/4gb max) Ubuntu PC I recently decommissioned but am now considering running two nodes on it. The only concern is that my other low power (2 cores, 7GB/8GB max) Ubuntu PC with 1 one node (~9TB used space) is unresponsive when trying to remote into it via NoMachine since the start of stress testing this month (it was fine before then).
I really just want to use what I have and not throw away my Window licenses by switching those PCs to Ubuntu.
Started node 2 over. Then renamed the storgenode.exe zip file in the Toolbox folder. Now it successfully created all the necessary files in the storage folder. Node 2 is working!
1 Like