Hello,
I have looked in the forum and there are some threads to the same topic, still I do not get it to do what I want.
I always get this error:
root@vultr:~/STORJ# docker exec -it storagenode /app/dashboard.sh
Error response from daemon: Container e34fbd4cc8e2e1d8f58cb3f8038d0c35aa064f886185313bbc39d8b8afa6ccef is restarting, wait until the container is running
What can I do?
This command: docker logs --tail 20 storagenode Does not get me any log but a list of commands…
This Command: docker ps -a gives mit this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e34fbd4cc8e2 storjlabs/storagenode:beta “/entrypoint” 33 minutes ago Restarting (1) 47 seconds ago storagenode
Sure!:
root@vultr:~# docker logs --tail 20 storagenode
–db.conn_max_lifetime duration Maximum Database Connection Lifetime, -1ns means the stdlib default (default -1ns)
–db.max_idle_conns int Maximum Amount of Idle Database connections, -1 means the stdlib default (default 20)
–db.max_open_conns int Maximum Amount of Open Database connections, -1 means the stdlib default (default 25)
–debug.addr string address to listen on for debug endpoints (default “127.0.0.1:0”)
–debug.trace-out string If set, a path to write a process trace SVG to
–defaults string determines which set of configuration defaults to use. can either be ‘dev’ or ‘release’ (default “release”)
–identity-dir string main directory for storagenode identity credentials (default “identity”)
–log.caller if true, log function filename and line number
–log.development if true, set logging to development mode
–log.encoding string configures log encoding. can either be ‘console’ or ‘json’ (default “console”)
–log.level Level the minimum log level to log (default info)
–log.output string can be stdout, stderr, or a filename (default “stderr”)
–log.stack if true, log stack traces
–metrics.addr string address to send telemetry to (default “collectora.storj.io:9000”)
–metrics.app string application name for telemetry identification (default “storagenode”)
–metrics.app-suffix string application suffix (default “-release”)
–metrics.instance-prefix string instance id prefix
–metrics.interval duration how frequently to send up telemetry (default 1m0s)
–monkit.hw.oomlog string path to log for oom notices (default “/var/log/kern.log”)
BUT with this:
–mount type=bind,source=“/root/STORJ/IDENTITY",destination=/app/identity
–mount type=bind,source="/root/STORJ/STORED-DATA”,destination=/app/config
–name storagenode storjlabs/storagenode:beta
It does not start at all…
Just gets me more lines…:
root@vultr:~# docker run -d --restart unless-stopped -p 28967:28967 \
Yeah thanks! I got it now…
Yes the files are there and it should be ok.
As I were only testing the disk is too small but I will correct that.
Got this now: {“log”:“2019-11-25T15:25:01.213Z\u0009\u001b[31mFATAL\u001b[0m\u0009Unrecoverable error\u0009{“error”: “piecestore monitor: disk space requirement not met”, “errorVerbose”: “piecestore monitor: disk space requirement not met\n\tstorj.io/storj/storagenode/monitor.(*Service).Run:118\n\tstorj.io/storj/storagenode.(*Peer).Run.func2:423\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}\n”,“stream”:“stderr”,“time”:“2019-11-25T15:25:01.213399109Z”}
One more question. More Diskspace is better as I will have more traffic for repairs as I would store many more pieces right?
The calculator on the Storj website seems to be a bit strange in that matter…
More diskspace is good so you can store more data but it has nothing to do with repairs. You can’t use “repair” term loosely here since repair traffic different. If your node is reliable and has a good rep then you get to store more data when your node is chosen.
Calculator is an estimate of what you can make if you utilize all of the available resources which is rare.