My node doesn't start

Node Operators troubleshooting
,
1

This node have been running for a while but I needed to change settings for the wallet and now its not starting


2023-01-16 16:19:07,346 INFO RPC interface 'supervisor' initialized
2023-01-16 16:19:07,347 INFO supervisord started with pid 1
2023-01-16 16:19:08,352 INFO spawned: 'processes-exit-eventlistener' with pid 55
2023-01-16 16:19:08,358 INFO spawned: 'storagenode' with pid 56
2023-01-16 16:19:08,365 INFO spawned: 'storagenode-updater' with pid 57
2023-01-16T16:19:08.405Z        INFO    Configuration loaded    {"Process": "storagenode-updater", "Location": "/app/config/config                           .yaml"}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "contact.externa                           l-address"}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet                           -features.0"}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocat                           ed-bandwidth"}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet                           "}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.email"                           }
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.address"                           }
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocat                           ed-disk-space"}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.private-                           address"}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file value for key        {"Process": "storagenode-updater", "Key":                            "log.caller"}
2023-01-16T16:19:08.405Z        INFO    Invalid configuration file value for key        {"Process": "storagenode-updater", "Key":                            "log.encoding"}
2023-01-16T16:19:08.406Z        INFO    Anonymized tracing enabled      {"Process": "storagenode-updater"}
2023-01-16T16:19:08.409Z        INFO    Running on version      {"Process": "storagenode-updater", "Service": "storagenode-updater                           ", "Version": "v1.70.2"}
2023-01-16T16:19:08.411Z        INFO    Downloading versions.   {"Process": "storagenode-updater", "Server Address": "https://vers                           ion.storj.io"}
2023-01-16T16:19:08.478Z        INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-01-16T16:19:08.479Z        INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2023-01-16T16:19:08.480Z        INFO    Operator email  {"Process": "storagenode", "Address": "hidden-info"}
2023-01-16T16:19:08.480Z        INFO    Operator wallet {"Process": "storagenode", "Address": "hidden-info                           0817851"}
2023-01-16T16:19:08.866Z        INFO    Current binary version  {"Process": "storagenode-updater", "Service": "storagenode", "Vers                           ion": "v1.70.2"}
2023-01-16T16:19:08.866Z        INFO    Version is up to date   {"Process": "storagenode-updater", "Service": "storagenode"}
2023-01-16T16:19:08.890Z        INFO    Current binary version  {"Process": "storagenode-updater", "Service": "storagenode-updater                           ", "Version": "v1.70.2"}
2023-01-16T16:19:08.890Z        INFO    Version is up to date   {"Process": "storagenode-updater", "Service": "storagenode-updater                           "}
2023-01-16 16:19:09,892 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 secon                           ds (startsecs)
2023-01-16 16:19:09,893 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-16 16:19:09,893 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (start                           secs)
Error: trust: open config/trust-cache.json: permission denied
2023-01-16 16:19:11,631 INFO exited: storagenode (exit status 1; not expected)
2023-01-16 16:19:12,638 INFO spawned: 'storagenode' with pid 90
2023-01-16 16:19:12,639 WARN received SIGQUIT indicating exit request
2023-01-16 16:19:12,640 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2023-01-16T16:19:12.641Z        INFO    Got a signal from the OS: "terminated"  {"Process": "storagenode-updater"}
2023-01-16 16:19:12,645 INFO stopped: storagenode-updater (exit status 0)
2023-01-16T16:19:12.749Z        INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-01-16T16:19:12.751Z        INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2023-01-16T16:19:12.752Z        INFO    Operator email  {"Process": "storagenode", "Address": "hidden-info"}
2023-01-16T16:19:12.752Z        INFO    Operator wallet {"Process": "storagenode", "Address": "hidden-info                           0817851"}
Error: trust: open config/trust-cache.json: permission denied
2023-01-16 16:19:12,950 INFO stopped: storagenode (exit status 1)
2023-01-16 16:19:12,951 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
pi@raspberrypi:~ $
2

Hi @Gerarardit
Please post your docker run command with any personal information removed.

3

sudo docker run -d
–restart unless-stopped
–stop-timeout 300
-p 28967:28967/tcp
-p 28967:28967/udp
-p 14002:14002
-e WALLET=“x1”
-e EMAIL=“x”
-e ADDRESS=“x:28967”
-e STORAGE=“0.9GB”
–user $(id -u):$(id -g)
–mount type=bind,source=“/home/pi/storagenode”,destination=/app/identity
–mount type=bind,source=“/mnt/storj”,destination=/app/config
–name storagenode storjlabs/storagenode:latest

4

Seems your docker container doesn’t have an access to the config directory.
Since you used an option

then you need to change an owner for your data location

to your user recursively, i.e.

sudo chown $(id -u):$(id -g) -R /mnt/storj
1 Like
5

now it gives me another error saying i dont meet space requirements

2023-01-17 08:21:26 (17.7 MB/s) - ‘/tmp/storagenode.zip’ saved [15681110/15681110]

2023-01-17 08:21:30,840 INFO RPC interface ‘supervisor’ initialized
2023-01-17 08:21:30,841 INFO supervisord started with pid 1
2023-01-17 08:21:31,845 INFO spawned: ‘processes-exit-eventlistener’ with pid 55
2023-01-17 08:21:31,852 INFO spawned: ‘storagenode’ with pid 56
2023-01-17 08:21:31,858 INFO spawned: ‘storagenode-updater’ with pid 57
2023-01-17T08:21:31.897Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Locatio n”: “/app/config/config.yaml”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features.0”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2023-01-17T08:21:31.897Z INFO Invalid configuration file value for key {“Process”: “storag enode-updater”, “Key”: “log.stack”}
2023-01-17T08:21:31.897Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”}
2023-01-17T08:21:31.900Z INFO Running on version {“Process”: “storagenode-updater”, "Service ": “storagenode-updater”, “Version”: “v1.70.2”}
2023-01-17T08:21:31.900Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2023-01-17T08:21:31.974Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/ap p/config/config.yaml”}
2023-01-17T08:21:31.975Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2023-01-17T08:21:31.976Z INFO Operator email {“Process”: “storagenode”, “Address”: “gerardit4@gm ail.com”}
2023-01-17T08:21:31.977Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0xe24eCf6a6b 509efddA817De28E111B12F0817851”}
2023-01-17T08:21:32.358Z INFO Current binary version {“Process”: “storagenode-updater”, "Service ": “storagenode”, “Version”: “v1.70.2”}
2023-01-17T08:21:32.358Z INFO Version is up to date {“Process”: “storagenode-updater”, "Service ": “storagenode”}
2023-01-17T08:21:32.382Z INFO Current binary version {“Process”: “storagenode-updater”, "Service ": “storagenode-updater”, “Version”: “v1.70.2”}
2023-01-17T08:21:32.382Z INFO Version is up to date {“Process”: “storagenode-updater”, "Service “: “storagenode-updater”}
2023-01-17 08:21:33,384 INFO success: processes-exit-eventlistener entered RUNNING state, process has staye d up for > than 1 seconds (startsecs)
2023-01-17 08:21:33,384 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-17 08:21:33,384 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-17T08:21:35.972Z INFO Telemetry enabled {“Process”: “storagenode”, “instance ID”: " 12p8vXhGUUoL5p3Gw7vi68VfZ3D9hgdWniSY22sDVf1E8uTedBv”}
2023-01-17T08:21:35.973Z INFO Event collection enabled {“Process”: “storagenode”, “instanc e ID”: “12p8vXhGUUoL5p3Gw7vi68VfZ3D9hgdWniSY22sDVf1E8uTedBv”}
2023-01-17T08:21:37.506Z INFO db.migration Database Version {“Process”: “storagenode”, “version”: 54}
2023-01-17T08:21:38.322Z INFO preflight:localtime start checking local system clock with trus ted satellites’ system clock. {“Process”: “storagenode”}
2023-01-17T08:21:39.060Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock. {“Process”: “storagenode”}
2023-01-17T08:21:39.062Z INFO bandwidth Performing bandwidth usage rollups {“Process”: “storagenode”}
2023-01-17T08:21:39.063Z INFO Node 12p8vXhGUUoL5p3Gw7vi68VfZ3D9hgdWniSY22sDVf1E8uTedBv started { “Process”: “storagenode”}
2023-01-17T08:21:39.063Z WARN piecestore:monitor Used more space than allocated. Allocated s pace is {“Process”: “storagenode”, “bytes”: 800000000}
2023-01-17T08:21:39.066Z ERROR piecestore:monitor Total disk space is less than required mini mum {“Process”: “storagenode”, “bytes”: 500000000000}
2023-01-17T08:21:39.068Z ERROR services unexpected shutdown of a runner {“Process”: “storag enode”, “name”: “piecestore:monitor”, “error”: “piecestore monitor: disk space requirement not met”, “error Verbose”: “piecestore monitor: disk space requirement not met\n\tstorj.io/storj/storagenode/monitor.(*Servi ce).Run:125\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:75”}
2023-01-17T08:21:39.069Z ERROR gracefulexit:blobscleaner couldn’t receive satellite’s GE sta tus {“Process”: “storagenode”, “error”: “context canceled”}
2023-01-17T08:21:39.069Z ERROR nodestats:cache Get pricing-model/join date failed {“Process”: “storagenode”, “error”: “context canceled”}
2023-01-17T08:21:39.069Z ERROR gracefulexit:chore error retrieving satellites. {“Process”: “storagenode”, “error”: “satellitesdb: context canceled”, “errorVerbose”: “satellitesdb: context canceled\ n\tstorj.io/storj/storagenode/storagenodedb.(*satellitesDB).ListGracefulExits.func1:152\n\tstorj.io/storj/s toragenode/storagenodedb.(*satellitesDB).ListGracefulExits:164\n\tstorj.io/storj/storagenode/gracefulexit.( *Service).ListPendingExits:58\n\tstorj.io/storj/storagenode/gracefulexit.(*Chore).AddMissing:58\n\tstorj.io /common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/gracefulexit.(*Chore).Run:51\n\tstorj.io/storj/ private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Grou p).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-01-17T08:21:39.070Z INFO trust Scheduling next refresh {“Process”: “storagenode”, “after”: “7h25m3.899398885s”}
2023-01-17T08:21:39.064Z INFO Public server started on [::]:28967 {“Process”: “storagenode”}
2023-01-17T08:21:39.070Z INFO Private server started on 127.0.0.1:7778 {“Process”: “storag enode”}
2023-01-17T08:21:39.070Z INFO failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Receive Buffer Size · lucas-clemente/quic-go Wiki · GitHub for details. {“Process”: “storagenode”}
2023-01-17T08:21:39.071Z ERROR piecestore:cache error getting current used space: {“P rocess”: “storagenode”, “error”: “context canceled; context canceled; context canceled; context canceled; c ontext canceled; context canceled; context canceled”, “errorVerbose”: “group:\n— context canceled\n— co ntext canceled\n— context canceled\n— context canceled\n— context canceled\n— context canceled\n— context canceled”}
2023-01-17T08:21:39.262Z ERROR collector error during collecting pieces: {“Process”: “storagenode”, “error”: “context canceled”}
Error: piecestore monitor: disk space requirement not met
2023-01-17 08:21:41,141 INFO exited: storagenode (exit status 1; not expected)

6

You dont have enough space to run a storagenode → 500GB min.

1 Like
7

Did you provide a correct path to the data location?
I hope you did not run a SETUP step in the second time (it should be executed only once for the entire node’s life).

1 Like
8

I did not run setup and I think the path is the right data location. The path is /mnt/storj and this is whats inside it


pi@raspberrypi:/mnt/storj $ ls
config.yaml  orders          storage           trust-cache.json098346934
lost+found   revocations.db  trust-cache.json  trust-cache.json812360297
9

-e STORAGE=“0.9GB”

You need to raise this to a minimum of 500GB.

2 Likes
10

I have space is the same disk and I have data in it

im stupid i wanted to put 0.9TB xd

11

i assume now its working?

2 Likes
12

yes thanks for your help

2 Likes