$50 for 1 on 1 assistance installing Storj

[thereverendd]

Where is the LOG stored and how do i delete it when it gets too big?

[thereverendd]

Also wondering how long the RED areas will take to change its been up now for 8hrs

[Alexey]

If you did not redirect logs to the file, then they stored inside the container and will be deleted when you re-create the container.
You may specify logs parameters for your docker run command if you do not want to redirect logs to the file:

docker run ... \
...
--log-opt max-size=500m \
--log-opt max-file=10 \
storjlabs/storagenode:latest

These options means: log size 500MiB max, keep 10 logs.

If you would redirect logs to the file, then you may use logrotate tool instead (when you redirect, docker’s log options will not work). See for example:

All my nodes keep restarting since last night: "/var/log/supervisor/supervisord.log does not exist"

Yes, the simplest way is to configure logrotate to manage your storagenode logs. It should already be running on your system. I recommend placing a logrotate config specifically for your node(s) in the /etc/logrotate.d folder. For example, I have a file /etc/logrotate.d/storagenode (it can have any name). The file contents are: /path/to/logs/storj*/storagenode*.log { su username username weekly maxsize 200M rotate 52 dateext dateformat -%Y%m%d …

Regarding 0% for ap1 satellite… Please make sure that your provider do not block connections from these IPs:

nslookup ap1.storj.io 8.8.8.8

and you do not block them on your router or firewall.

[thereverendd]

My NODE is now up and running. Thank you all for helping out.

[thereverendd]

How do you ‘re-create a container’ does this require you to stop the docker and re-start it? and if so wont your up time be effected ?

[Alexey]

Docker is used to create ephemeral containers, so all your persistent information (like data storage and identity) should be on your host. So, when you stop and remove the container, your data is not destroyed with it.
To stop and remove the container:

docker stop -t 300 storagenode
docker rm storagenode

You must never use the SETUP step again for the same node, otherwise you may destroy it. This step must be executed only once for that identity.

To run your node back you should execute a normal docker run command with all your parameters, include changed ones.

[snorkel]

You don’t stop docker. Docker is just a container manager. You stop the container aka storagenode, that runs inside docker.
The logs are deleted by docker when you run the rm command. Only stop and restart dosen’t delete them. With each occasion when I must stop the storagenode, I also do the rm command, just to clear up the logs, then docker run…
When you stop the storagenode, always use the stop -t 300, because it dosen’t instant kill the storagenode, and it gives it time to finish the work that is doing. Stoping it without the -t 300 can and probably will corrupt databases. That just says: hey storagenode, you must stop the work now; I give you 300s and than I will kill your process.

[snorkel]

Please check this run command for Synology NAS.
Is this OK as a run command? The places of options are OK?
Are the log-opt options placed correctly? Thanks!

docker run -d --restart unless-stopped --stop-timeout 300 \
	-p 28967:28967/tcp \
	-p 28967:28967/udp \
	-p 14002:14002 \
	-p 5999:5999 \
	-e WALLET="xxx" \
	-e EMAIL="xxx" \
	-e ADDRESS="xxx:28967" \
	-e STORAGE="14TB" \
	--mount type=bind,source="/volume1/Storj/Identity/storagenode/",destination=/app/identity \
	--mount type=bind,source="/volume1/Storj/",destination=/app/config \
	--name storagenode storjlabs/storagenode:latest \
	--server.address=":28967" \
	--console.address=":14002" \
	--debug.addr=":5999" \
	--log-opt max-size=50m \
	--log-opt max-file=5 \
	--log.level=error \
	--filestore.write-buffer-size 4MiB \
	--pieces.write-prealloc-size 4MiB \
	--storage2.piece-scan-on-startup=true \
	--operator.wallet-features=zksync

[Alexey]

Docker’s options should be before the image name

docker run -d --restart unless-stopped --stop-timeout 300 \
	-p 28967:28967/tcp \
	-p 28967:28967/udp \
	-p 14002:14002 \
	-p 5999:5999 \
	-e WALLET="xxx" \
	-e EMAIL="xxx" \
	-e ADDRESS="xxx:28967" \
	-e STORAGE="14TB" \
	--mount type=bind,source="/volume1/Storj/Identity/storagenode/",destination=/app/identity \
	--mount type=bind,source="/volume1/Storj/",destination=/app/config \
	--log-opt max-size=50m \
	--log-opt max-file=5 \
	--name storagenode storjlabs/storagenode:latest \
	--server.address=":28967" \
	--console.address=":14002" \
	--debug.addr=":5999" \
	--log.level=error \
	--filestore.write-buffer-size 4MiB \
	--pieces.write-prealloc-size 4MiB \
	--storage2.piece-scan-on-startup=true \
	--operator.wallet-features=zksync