[OdroidC2] Start my Node but Docker says it's alway restarting

Node Operators troubleshooting
1

Hello.

I have set up a node on my Odroid C2 with a 1 To HDD

I declare the node with this command :slight_smile:

docker run -d --restart unless-stopped -p 28967:28967 \
-p 14002:14002 \
-e WALLET="0x*********09b4" \
-e EMAIL="****.*****@gmail.com" \
-e ADDRESS="xxx.xxx.xxx.xxx:28967" \
-e BANDWIDTH="18TB" \
-e STORAGE="920MB" \
--mount type=bind,source="/home/jeedom/.local/share/storj/identity/storagenode",destination=/app/identity \
--mount type=bind,source="/media/StorJ_1To",destination=/app/config \
--name storagenode storjlabs/storagenode:beta

Ports 28967 and 14002 are forwarded on my network provider set top box.

Identity is correct :

root@odroidc2:~# ls -l /home/jeedom/.local/share/storj/identity/storagenode
total 24
-rw-r–r-- 1 jeedom jeedom 546 Mar 1 17:56 ca.1582221999.cert
-rw-r–r-- 1 jeedom jeedom 1076 Mar 1 17:56 ca.cert
-rw------- 1 jeedom jeedom 241 Mar 1 17:56 ca.key
-rw-r–r-- 1 jeedom jeedom 1084 Mar 1 17:56 identity.1582221999.cert
-rw-r–r-- 1 jeedom jeedom 1614 Mar 1 17:56 identity.cert
-rw------- 1 jeedom jeedom 241 Mar 1 17:56 identity.key

And storage is mounted :

root@odroidc2:~# ls -l /media/StorJ_1To
total 44
-rw------- 1 root root  7096 Mar  1 18:33 config.yaml
d--------- 2 root root  4096 Jan  1  1970 lost+found
-rw------- 1 root root 32768 Mar  1 18:42 revocations.db
drwx------ 6 root root  4096 Mar  1 18:42 storage
-rw------- 1 root root  1202 Mar  1 18:42 trust-cache.json

But my node is alway restarted :

root@odroidc2:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a11b511d31c3 storjlabs/storagenode:beta “/entrypoint” 10 minutes ago Restarting (1) 47 seconds ago storagenode

And I can’t access Dashboard on internal or external IP on port 14002

What do I need to check or modify ?

Thanks.

2

Please, provide logs

docker logs --tail 20 storagenode
3

Minimum requirement is 500GB

You need to find actual free space and keep 10% as overhead. If you have 920GB free then make your drive use 800GB to be safe.

2 Likes
4

Oops, shame on me !!

I have a 1 To HDD so, to keep 10% as overhead, I wnat to allocate 920 GB and not MB

Now, my Node is OK :

docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fb6b33b36e43 storjlabs/storagenode:beta “/entrypoint” About a minute ago Up About a minute 0.0.0.0:14002->14002/tcp, 0.0.0.0:28967->28967/tcp storagenode

Thanks.

5

1TB HDD does NOT have 1000GB as free space. I could be 920GB to 935GB actual free space. So 10% of it would be ~800GB. Don’t risk your node by allocating more. You can increase the size any time later by editing your docker run command. We have seen database files, log files using the free space, also trash folder.

6

Thanks for this advice, as my 1 Tb HDD is really 916GB, I have set up my Node to use 820GB

1 Like
7

It’s actually most likely really 916GiB… But almost every OS displays it in the wrong unit. This means your HDD is actually 983GB so you can assign a little more than 820GB. Not that it matters that much.

2 Likes