Originally on 0.35.3, system updated to 1.0.1 a few days ago with no problems. Overnight it looks like I got updated to 1.1.1 and when I checked the dashboard this AM it showed offline. Tried restarting the “Storj V3 Storage Node” service and it gave the following error:
Windows could not start the Storj V3 Storage Node service on Local Computer.
Error 1067: The process terminated unexpectedly.
Anyone encountered this and have steps to fix it?
welcom to forum, what log show?
Email address and wallet removed for privacy reasons
2020-04-10T10:16:28.031-0700 INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-04-10T10:16:28.048-0700 INFO Operator email: xxxxxxxxxxxxxxx
2020-04-10T10:16:28.048-0700 INFO operator wallet: xxxxxxxxxxxxxxx
2020-04-10T10:16:28.392-0700 INFO version running on version v1.1.1
2020-04-10T10:28:25.780-0700 INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-04-10T10:28:25.797-0700 INFO Operator email: xxxxxxxxxxxxxxx
2020-04-10T10:28:25.797-0700 INFO operator wallet: xxxxxxxxxxxxxxx
2020-04-10T10:28:26.084-0700 INFO version running on version v1.1.1
2020-04-10T10:35:01.365-0700 INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-04-10T10:35:01.385-0700 INFO Operator email: xxxxxxxxxxxxxxx
2020-04-10T10:35:01.385-0700 INFO operator wallet: xxxxxxxxxxxxxxx
2020-04-10T10:35:01.710-0700 INFO version running on version v1.1.1
The updater log has some interesting info it seems, but it may just be because the storage process is not running:
| 2020-04-10T10:28:10.748-0700 | INFO | Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml |
|---|---|---|
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: operator.email |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: storage.allocated-bandwidth |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: storage.allocated-disk-space |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: operator.wallet |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: contact.external-address |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: server.debug-log-traffic |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: storage.path |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: server.private-address |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file key: server.address |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file value for key: log.level |
| 2020-04-10T10:28:10.749-0700 | INFO | Invalid configuration file value for key: log.stack |
| 2020-04-10T10:28:10.827-0700 | INFO | Downloading versions from https://version.storj.io |
| 2020-04-10T10:28:11.127-0700 | INFO | storagenode version is up to date |
| 2020-04-10T10:28:11.127-0700 | INFO | Downloading versions from https://version.storj.io |
| 2020-04-10T10:28:11.178-0700 | INFO | storagenode-updater version is up to date |
Have you tried running the service manually?
Yes, it always errors out with the error that I listed above in the first post.
If error is still persist, then modify the log.level: parameter to debug in the "C:\Program Files\Storj\Storage Node\config.yaml" file, save it and restart the node.
Then take 20 last lines from the log and post them here.
The drive scanned fine, but apparently something changed because after the scan, the service will start now.
Thank you for your help.