Power was out for 12 hours and when the machine came back up the node was not running. Tried to start it manually but it complained the config file wasn’t correct. Looks like the config.yaml location changed? I found the new location and added the changes and now I get a new error. Help!
C:\Program Files\Storj\Storage Node>storagenode.exe run
2021-07-22T09:42:44.530-0400 INFO Configuration loaded {"Location": "C:\\Users\\cthomas\\AppData\\Roaming\\Storj\\Storagenode\\config.yaml"}
2021-07-22T09:42:44.541-0400 WARN Operator email address isn't specified.
2021-07-22T09:42:44.541-0400 ERROR Invalid configuration. {"error": "operator wallet address isn't specified"}
Error: operator wallet address isn't specified
C:\Program Files\Storj\Storage Node>storagenode.exe run
2021-07-22T09:44:28.088-0400 INFO Configuration loaded {"Location": "C:\\Users\\cthomas\\AppData\\Roaming\\Storj\\Storagenode\\config.yaml"}
2021-07-22T09:44:28.099-0400 INFO Operator email {"Address": "storj-toq@edited.com"}
2021-07-22T09:44:28.099-0400 INFO Operator wallet {"Address": "0xDc68877015B3bac585aAE49edited"}
2021-07-22T09:44:28.099-0400 INFO db database does not exists {"database": "info"}
2021-07-22T09:44:28.099-0400 INFO db database does not exists {"database": "bandwidth"}
2021-07-22T09:44:28.099-0400 INFO db database does not exists {"database": "orders"}
2021-07-22T09:44:28.099-0400 INFO db database does not exists {"database": "piece_expiration"}
2021-07-22T09:44:28.101-0400 INFO db database does not exists {"database": "pieceinfo"}
2021-07-22T09:44:28.103-0400 INFO db database does not exists {"database": "piece_spaced_used"}
2021-07-22T09:44:28.103-0400 INFO db database does not exists {"database": "reputation"}
2021-07-22T09:44:28.103-0400 INFO db database does not exists {"database": "storage_usage"}
2021-07-22T09:44:28.104-0400 INFO db database does not exists {"database": "used_serial"}
2021-07-22T09:44:28.104-0400 INFO db database does not exists {"database": "satellites"}
2021-07-22T09:44:28.104-0400 INFO db database does not exists {"database": "notifications"}
2021-07-22T09:44:28.105-0400 INFO db database does not exists {"database": "heldamount"}
2021-07-22T09:44:28.105-0400 INFO db database does not exists {"database": "pricing"}
2021-07-22T09:44:28.105-0400 INFO db database does not exists {"database": "secret"}
2021-07-22T09:44:28.376-0400 INFO Telemetry enabled {"instance ID": "12gTfp8kSpyChkSAdzbAM9gx1LBvYf25idT7sW3rorj422gMoBf"}
2021-07-22T09:44:28.826-0400 INFO db.migration Database Created {"version": 52}
2021-07-22T09:44:28.978-0400 INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2021-07-22T09:44:29.511-0400 INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
2021-07-22T09:44:29.511-0400 INFO bandwidth Performing bandwidth usage rollups
2021-07-22T09:44:29.511-0400 INFO trust Scheduling next refresh {"after": "7h9m5.260197821s"}
2021-07-22T09:44:29.511-0400 INFO Node 12gTfp8kSpyChkSAdzbAM9gx1LBvYf25idT7sW3rorj422gMoBf started
2021-07-22T09:44:29.513-0400 WARN piecestore:monitor Disk space is less than requested. Allocated space is {"bytes": 186118193152}
2021-07-22T09:44:29.514-0400 ERROR piecestore:monitor Total disk space is less than required minimum {"bytes": 500000000000}
2021-07-22T09:44:29.513-0400 INFO Public server started on [::]:28967
2021-07-22T09:44:29.514-0400 ERROR services unexpected shutdown of a runner {"name": "piecestore:monitor", "error": "piecestore monitor: disk space requirement not met", "errorVerbose": "piecestore monitor: disk space requirement not met\n\tstorj.io/storj/storagenode/monitor.(*Service).Run:123\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T09:44:29.515-0400 INFO Private server started on 127.0.0.1:7778
2021-07-22T09:44:29.515-0400 ERROR nodestats:cache Get pricing-model/join date failed {"error": "context canceled"}
Error: piecestore monitor: disk space requirement not met
C:\Program Files\Storj\Storage Node>
I’m not sure but it looks to me like Storj updated itself a few days ago and didn’t copy over the correct config.yaml as the current one had an old IP address in it? Not sure, anyway, now I am getting this error. If I am reading this correctly right now the log file is 1.7Gb???!!
c:\Program Files\Storj\Storage Node>storagenode.exe run
Error: couldn't open sink "winfile:///C:\\Program Files\\Storj\\Storage Node\\\\storagenode.log": open C:\Program Files\Storj\Storage Node\\storagenode.log: Access is denied.
Usage:
Got the logfile open in Power Shell… Here are the last few lines before the power outage
2021-07-21T15:52:16.970-0400 INFO piecestore upload started {"Piece ID": "RFKWRM3NBCHBSCDUA3BRNALWFDXASX6P5YQLW7HCQOYWV4XQICSA", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Available Space": 6220881032064}
2021-07-21T15:52:17.040-0400 INFO piecestore uploaded {"Piece ID": "RFKWRM3NBCHBSCDUA3BRNALWFDXASX6P5YQLW7HCQOYWV4XQICSA", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Size": 228352}
2021-07-22T05:35:16.846-0400 INFO Configuration loaded {"Location": "C:\\Program Files\\Storj\\Storage Node\\config.yaml"}
2021-07-22T05:35:16.862-0400 INFO Operator email {"Address": "storj-toq@issitoq.com"}
2021-07-22T05:35:16.862-0400 INFO Operator wallet {"Address": "0xDc68877015B3bac585aAE4952160d862bf1EC224"}
2021-07-22T05:35:17.567-0400 INFO Telemetry enabled {"instance ID": "12gTfp8kSpyChkSAdzbAM9gx1LBvYf25idT7sW3rorj422gMoBf"}
2021-07-22T05:35:17.926-0400 INFO db.migration Database Version {"version": 52}
2021-07-22T05:35:18.351-0400 WARN trust Failed to fetch URLs from source; used cache {"source": "https://www.storj.io/dcs-satellites", "error": "HTTP source: Get \"https://www.storj.io/dcs-satellites\": dial tcp: lookup www.storj.io: no such host", "errorVerbose": "HTTP source: Get \"https://www.storj.io/dcs-satellites\": dial tcp: lookup www.storj.io: no such host\n\tstorj.io/storj/storagenode/trust.(*HTTPSource).FetchEntries:68\n\tstorj.io/storj/storagenode/trust.(*List).fetchEntries:90\n\tstorj.io/storj/storagenode/trust.(*List).FetchURLs:49\n\tstorj.io/storj/storagenode/trust.(*Pool).fetchURLs:240\n\tstorj.io/storj/storagenode/trust.(*Pool).Refresh:177\n\tstorj.io/storj/storagenode.(*Peer).Run:843\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:64\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:18.354-0400 INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2021-07-22T05:35:18.355-0400 ERROR preflight:localtime unable to get satellite system time {"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "error": "rpc: dial tcp: lookup europe-north-1.tardigrade.io: no such host", "errorVerbose": "rpc: dial tcp: lookup europe-north-1.tardigrade.io: no such host\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:197\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:163\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).getSatelliteTime:110\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:67\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:18.355-0400 ERROR preflight:localtime unable to get satellite system time {"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "error": "rpc: dial tcp: lookup saltlake.tardigrade.io: no such host", "errorVerbose": "rpc: dial tcp: lookup saltlake.tardigrade.io: no such host\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:197\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:163\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).getSatelliteTime:110\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:67\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:18.355-0400 ERROR preflight:localtime unable to get satellite system time {"Satellite ID": "12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo", "error": "rpc: dial tcp: lookup us2.storj.io: no such host", "errorVerbose": "rpc: dial tcp: lookup us2.storj.io: no such host\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:197\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:163\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).getSatelliteTime:110\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:67\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:18.355-0400 ERROR preflight:localtime unable to get satellite system time {"Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "error": "rpc: dial tcp: lookup eu1.storj.io: no such host", "errorVerbose": "rpc: dial tcp: lookup eu1.storj.io: no such host\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:197\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:163\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).getSatelliteTime:110\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:67\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:18.355-0400 ERROR preflight:localtime unable to get satellite system time {"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "error": "rpc: dial tcp: lookup us1.storj.io: no such host", "errorVerbose": "rpc: dial tcp: lookup us1.storj.io: no such host\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:197\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:163\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).getSatelliteTime:110\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:67\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:18.355-0400 ERROR preflight:localtime unable to get satellite system time {"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "error": "rpc: dial tcp: lookup ap1.storj.io: no such host", "errorVerbose": "rpc: dial tcp: lookup ap1.storj.io: no such host\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:197\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:107\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:90\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:110\n\tstorj.io/common/rpc.Dialer.dialPool:163\n\tstorj.io/common/rpc.Dialer.DialNodeURL:106\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).getSatelliteTime:110\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:67\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:18.355-0400 ERROR Failed preflight check. {"error": "system clock is out of sync: system clock is out of sync with all trusted satellites", "errorVerbose": "system clock is out of sync: system clock is out of sync with all trusted satellites\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check:96\n\tstorj.io/storj/storagenode.(*Peer).Run:847\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:64\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-22T05:35:19.150-0400 FATAL Unrecoverable error {"error": "system clock is out of sync: system clock is out of sync with all trusted satellites", "errorVerbose": "system clock is out of sync: system clock is out of sync with all trusted satellites\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check:96\n\tstorj.io/storj/storagenode.(*Peer).Run:847\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:64\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
Started getting an error about an invalid sink in the log file? and that access was denied. So I changed the permissions on the log file so that everyone had full control. That solved it. Node came up, all good.
I took it back down and took the opportunity to rotate the log file. Which is something I think storj should really do itself.
you sure your hdd is connected … a reboot or shutdown shouldn’t require any reconfiguration to get you back online…
check your basic windows storagenode setup is right.
haven’t really installed a windows node for a long time… so best advice i can give is to check that everything is configured correctly and the paths are right…
like if we say you are using a usb hdd and it was put into a new port and got a new drive letter… something like that might mess it all up
You must provide paths to the config (--config-dir) and to the identity (--identity-dir) to be able to successfully execute storagenode.exe run from the CLI.
Since you use a Windows GUI setup, then you must run it with Administrator’s rights.
But why do not try to start the service from the Services applet or from the elevated PowerShell?