ok I take that as a no change the -p 14003:14002
no error just got what looks like my NODE address ?
run docker ps
then run docker logs -f storagenode
Got this from DOCKER
diamonddog@storj1:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
xxx storjlabs/storagenode:latest “/entrypoint” About a minute ago Up 11 seconds 0.0.0.0:14003->14002/tcp, :::14003->14002/tcp, 0.0.0.0:28968->28967/tcp, 0.0.0.0:28968->28967/udp, :::28968->28967/tcp, :::28968->28967/udp storagenode
Then got this from the LOGS
2023-02-02T16:29:07.692Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2023-02-02T16:29:07.694Z INFO Operator email {“Process”: “storagenode”, “Address”: “xxxx”}
2023-02-02T16:29:07.694Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “xxx”}
Error: Error starting master database on storagenode: group:
— stat config/storage/blobs: no such file or directory
— stat config/storage/temp: no such file or directory
— stat config/storage/garbage: no such file or directory
— stat config/storage/trash: no such file or directory
2023-02-02 16:29:07,722 INFO exited: storagenode (exit status 1; not expected)
2023-02-02 16:29:10,731 INFO spawned: ‘storagenode’ with pid 64
2023-02-02T16:29:10.824Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2023-02-02T16:29:10.827Z INFO Operator email {“Process”: “storagenode”, “Address”: “xxx”}
2023-02-02T16:29:10.828Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “xxx”}
Error: Error starting master database on storagenode: group:
— stat config/storage/blobs: no such file or directory
— stat config/storage/temp: no such file or directory
— stat config/storage/garbage: no such file or directory
— stat config/storage/trash: no such file or directory
2023-02-02 16:29:10,856 INFO exited: storagenode (exit status 1; not expected)
2023-02-02 16:29:11,858 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2023-02-02 16:29:12,861 WARN received SIGQUIT indicating exit request
2023-02-02 16:29:12,862 INFO waiting for processes-exit-eventlistener, storagenode-updater to die
2023-02-02T16:29:12.862Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2023-02-02 16:29:12,867 INFO stopped: storagenode-updater (exit status 0)
2023-02-02 16:29:13,869 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
Ok I think you missed a step, did you run the setup first?
I walked thru the CONFUSING directions on the site. They jump you all over the darn place.
so NO IDEA what i did or did not do as my brain is a pile of MUSH
So run
docker run --rm -e SETUP="true" \
--user $(id -u):$(id -g) \
--mount type=bind,source="<identity-dir>",destination=/app/identity \
--mount type=bind,source="<storage-dir>",destination=/app/config \
--name storagenode storjlabs/storagenode:latest
First
Getting this error
Error response from daemon: Conflict. The container name “/storagenode” is already in use by container “xxxx”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
diamonddog@storj1:~$ sudo docker rm storagenode
Error response from daemon: You cannot remove a running container xxx. Stop the container before attempting removal or force remove
diamonddog@storj1:~$
ok run docker stop storagenode
then run docker rm storagenode
It appears to have stalled out here
0K .......... .......... .......... .......... .......... 0% 4.57M 2s
50K .......... .......... .......... .......... .......... 1% 5.59M 2s
100K … … … … … 1% 8.67M 1s
150K … … … … … 2% 11.9M 1s
200K … … … … … 2% 13.9M 1s
250K … … … … … 3% 8.60M 1s
300K … … … … … 4% 24.4M 1s
350K … … … … … 4% 7.46M 1s
400K … …
Still not moving from that spot
That I cannot really help much with its either the server or you.
Now getting
HTTP request sent, awaiting response… 401 Unauthorized
Username/Password Authentication Failed.
diamonddog@storj1:~$
Ok looks like i re-ran it and it worked now. So what would the next step be?
next step is just re running the docker start command you had done before this part
How do i fix this to be 9tb
-storage.allocated-disk-space=2.0TB
You just run with -e STORAGE=“9TB”
how do i check to see if it is running now?
docker ps
docker logs -f storagenode