New storj UNRAID Docker node is offline

Node Operators troubleshooting
, ,
1

Hi, I just deployed my first storj docker on UNRAID.
The port forwarding it’s done and tested from Open Port Check Tool - Test Port Forwarding on Your Router

The node still offline after 12h running.

Can you help me to troubleshoot the issue?

imagen

Log output (obfuscated)

Blockquote
2020-05-08T09:59:41.261Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-05-08T09:59:41.262Z INFO tracing disabled
2020-05-08T09:59:41.271Z INFO Operator email {“Address”: “xxxxx@gmail.com”}
2020-05-08T09:59:41.271Z INFO Operator wallet {“Address”: “0x00000000000000000000”}
2020-05-08T09:59:42.769Z INFO db.migration Database Version {“version”: 36}
2020-05-08T09:59:44.662Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-05-08T09:59:45.532Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-05-08T09:59:45.532Z INFO trust Scheduling next refresh {“after”: “5h6m26.500217832s”}
2020-05-08T09:59:45.532Z INFO bandwidth Performing bandwidth usage rollups
2020-05-08T09:59:45.532Z INFO Node 1nNFrV84EoeGFHTRrLs1hSVjpbgfKCJQZSKRqdpUPcMaQncz29 started
2020-05-08T09:59:45.532Z INFO Public server started on [::]:28967
2020-05-08T09:59:45.532Z INFO Private server started on 127.0.0.1:7778

2

is your node reachable TO the internet as well? (not only from)

3

Yes, the storj docker can rearch Internet.

/app # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=56 time=8.526 ms
64 bytes from 8.8.8.8: seq=1 ttl=56 time=8.871 ms
64 bytes from 8.8.8.8: seq=2 ttl=56 time=8.800 ms
^C
— 8.8.8.8 ping statistics —
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 8.526/8.732/8.871 ms

4

Can you show your docker run command and remove any personal info from it

5

command after apply changes on docker:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name=‘storagenode-v3’ --net=‘bridge’ -e TZ=“Europe/Paris” -e HOST_OS=“Unraid” -e ‘WALLET’=‘0x00000000000000000000’ -e ‘EMAIL’=‘xxxxx@gmail.com’ -e ‘ADDRESS’=‘ip.serviciosenlared.es:28969’ -e ‘BANDWIDTH’=‘151TB’ -e ‘STORAGE’=‘1TB’ -p ‘28967:28967/tcp’ -p ‘14002:14002/tcp’ --mount type=bind,source=“/mnt/user/appdata/storj/identity/storagenode/”,destination=/app/identity --mount type=bind,source=“/mnt/user/appdata/storj/data/”,destination=/app/config ‘storjlabs/storagenode:beta’

ps from terminal:

./storagenode run --config-dir config --identity-dir identity --metrics.app-suffix=-alpha --metrics.interval=30m --contact.external-address=ip.serviciosenlared.es:28969 --operator.email=xxxxx@gmail.com --operator.wallet=0x00000000000000000000 --console.address=:14002 --storage.allocated-disk-space=1TB

6

This is the result from Open Port Check Tool - Test Port Forwarding on Your Router
Closed Port 28969 is closed on ip.serviciosenlared.es

In the remote address enter ip.serviciosenlared.es. In Port number enter 28969

Why aren’t you using port 28967 ?

7

This is the problem. You need to fix your address to ip.serviciosenlared.es:28967 .The port is open too.

8

Thanks @nerdatwork I did a mistake with the port on docker configuration. I changed “ip.serviciosenlared.es:28969” to “ip.serviciosenlared.es:28967” and the node it’s now online.

Thanks again.

1 Like
9

Awesome :tada: Make sure you have kept 10% disk space for overhead. Use only 90% of available free space.

1 Like