Node offline since update to v0.16.1

Node Operators troubleshooting
1

My node has be offline since it automatically updated to v0.16.1.
my logs:
2019-07-31T09:43:08.838Z INFO running on version v0.16.1
2019-07-31T09:43:08.863Z INFO db.migration Latest Version {“version”: 14}
2019-07-31T09:43:08.863Z INFO vouchers Checking vouchers
2019-07-31T09:43:08.864Z INFO bandwidth Performing bandwidth usage rollups
2019-07-31T09:43:08.864Z INFO Node 12f1H8srz5PUSmPoRuFuefXCMXUSMJVuCztov5JniRhzyj3h4E1 started
2019-07-31T09:43:08.864Z INFO Public server started on [::]:28967
2019-07-31T09:43:08.864Z INFO Private server started on 127.0.0.1:7778
2019-07-31T09:43:09.079Z INFO running on version v0.16.1
2019-07-31T09:43:12.818Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 992463459840}
2019-07-31T09:43:12.818Z WARN piecestore:monitor Disk space is less than requested. Allocating space {“bytes”: 742638753792}

2

Thanks for joining our community.

Please, first try to manually stop your container and run it again.

  1. docker stop -t 300 storagenode
  2. docker start storagenode

If that doesn’t solve the problem:

Can you verify that your firewall, ports in the router and your public IP is still the same than the one when it was running fine?
Can you also post your docker run command (please don’t post your Wallet)?

3

docker run -d --restart unless-stopped -p 28967:28967 -e WALLET=":slight_smile: " -e EMAIL="rvrojas9@gmail.com" -e ADDRESS=“redzstorj.ddns.net:28967” -e BANDWIDTH=“2TB” -e STORAGE=“1TB” --mount type=bind,source=“F:\Storj\Identity\storagenode\”,destination=/app/identity --mount type=bind,source=“F:\Storj2\”,destination=/app/config --name storagenode storjlabs/storagenode:alpha

checked port forwarding and firewall all the same as before…

4

This means that the issue is with hard drive space, In your run command you have specified 1TB of space to use but storj only detects about 0.74 TB free. Do you have anything else saved on the hard drive? Try changing 1TB on the run command to like 600GB and see if it works.

5

Although what you said is true about the missing 0.26 TB, this alone would not be enough to stop the node from connecting to the network. The software does automatically allocate up to the amount of free space available at the time the node is started. @redz it would be worth while figuring out where that free space is. Keep in mind if you have a “1 TB” drive, the formatted capacity is less (you probably already know this), and you shouldn’t allocate more that 90% of your free space.

I would also check that something hasn’t gone wrong with your DDNS updates, and that the machine you are running the node on still has the same static IP as you set in your firewall.

Good luck, and welcome to the forums!

6

What is your OS?
If Windows/MacOS then please, restart the Docker from the Docker desktop application.

1 Like
7

Thanks everyone. Docker updated which needed a restart which made my node run normally again. Thanks again. :smile:

1 Like