Hi,
I’ve started a second node using a second HDD on my Raspberry Pi 4, but it’s been offline since its creation a few hours ago, is this normal? I’m running Raspberry Pi OS, confirmed identity is fine and signed, six files, correct file sizes etc. I’ve confirmed ports are accessible from the outside, I’m using ddns and I’ve had the first node up and running for months with no issues. No firewall active on rPi nor router, even restarted the router for kicks.
Current uptime is 60 minutes since last reboot. I’ve restarted, stopped, deleted docker container, rebooted the rPi. “Last contact” was thousands of hours ago according to the web app. CLI dashboard reports offline as well.
System load is low/normal, NODE 1 is active as normal.
Run commands:
Summary
### NODE 1 ###
docker run -d --restart unless-stopped --stop-timeout 300 -p 28967:28967 -p 14002:14002 -e WALLET="XYZ" -e EMAIL="XYZ@XYZ.XYZ" -e ADDRESS="DDNS:28967" -e STORAGE="3400GB" --mount type=bind,source="XYZ/identity/storagenode",destination=/app/identity --mount type=bind,source="/XYZ/storj/",destination=/app/config --name storagenode1 storjlabs/storagenode:latest
### NODE 2 ###
docker run -d --restart unless-stopped --stop-timeout 300 -p 28968:28967 -p 14003:14002 -e WALLET="XYZ" -e EMAIL="XYZ@XYZ.XYZ" -e ADDRESS="DDNS:28968" -e STORAGE="5100GB" --mount type=bind,source="XYZ/identity/storagenode2",destination=/app/identity --mount type=bind,source="/XYZ/storj2/",destination=/app/config --name storagenode2 storjlabs/storagenode:latest
Log from problem node (NODE 2)
Summary
$ docker logs --tail 20 storagenode2
2020-08-07T20:22:26.181Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2020-08-07T20:22:26.184Z INFO Operator email {"Address": "XYZ@XYZ.XYZ"}
2020-08-07T20:22:26.184Z INFO Operator wallet {"Address": "XYZ"}
2020-08-07T20:22:29.386Z INFO Telemetry enabled
2020-08-07T20:22:29.450Z INFO db.migration Database Version {"version": 43}
2020-08-07T20:22:31.204Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2020-08-07T20:22:36.416Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
2020-08-07T20:22:36.417Z INFO bandwidth Performing bandwidth usage rollups
2020-08-07T20:22:36.418Z INFO Node XYZ started
2020-08-07T20:22:36.418Z INFO Public server started on [::]:28967
2020-08-07T20:22:36.418Z INFO Private server started on 127.0.0.1:7778
2020-08-07T20:22:36.419Z INFO trust Scheduling next refresh {"after": "2h17m53.176808445s"}
Thanks,
alfananuq