October 20, 20232 yr The last few versions have had a problem of randomly restarting the Storj Docker. its been like this on a couple different systems in different locations. I have also noticed that the 4 threads i allocate to storj are pinned max allot! I thought this was supposed to be light weight so it could run on things like RiPi...seems like its getting more and more of a power hog as time goes on. The goal is to use the EXTRA space on already used pools...but lately, storj seems to get mad if other people are accessing the pool drives at the same time... they don't pay enough to dedicate hardware to this. Lets hope the original goal and MO hasn't been forgotten!
October 20, 20232 yr 2 hours ago, miicar said: they don't pay enough to dedicate hardware to this. Yup, got rid of it recently. It does hammer the storage big time. The kind of people it seems to be worthy for are "my business rents 100 hosted VMs with a TB of SSD each and only need 50GB for a basic OS and app so I run storj on them on the side"... Edited October 20, 20232 yr by Kilrah
October 23, 20232 yr On 10/20/2023 at 4:47 PM, Kilrah said: Yup, got rid of it recently. It does hammer the storage big time. The kind of people it seems to be worthy for are "my business rents 100 hosted VMs with a TB of SSD each and only need 50GB for a basic OS and app so I run storj on them on the side"... my use case was old retired HDD's in an enclosure already being used for business stuff. that was great for the first couple years...still used those pools for other things at the same time (temp network scan folders, steam library, storing wallpapers, etc), my complaint is that over time, it seems that STORj has gotten greedy about IO time. if it cant have exclusive access to the HDD's it throws a fit and seems to reboot the docker container, or lock up the pool for a second...Im going to stick it out and hope things keep taking off to the point where it will pay to have dedicated file servers. If not on the storj platform, maybe in another...i am learning allot about server/network storage in the process. Edited October 23, 20232 yr by miicar
February 16, 20242 yr Hi, i got an error with mit storagenode-v3 docker "database disk image is malformed". It was an error in the bandwith.db and i could fix it with this article: https://support.storj.io/hc/en-us/articles/360029309111-How-to-fix-a-database-disk-image-is-malformed It is recommended to put the databases on an ssd into another folder, like described in this article: https://forum.storj.io/t/how-to-move-db-s-to-ssd-on-docker/7064 But i could not do it with this image because this image does not use /app/dbs folder. Is there a change to move the databases into another folder und use it?
March 10, 20242 yr I had Storj running for over a year now without problems at all. Since the last updates my banwidth.db got corrupted several times. It's like repairing it and storj runs like ~2 h and bandwidth.db is corrupted again. Since the last update storj-node stops on startup with info.db error. All files are in place and nothing was changed at all. -> info.db file is there... Greetings Dark
May 2, 20242 yr Hi, I can't pass the debug address to Storj's docker. I also inserted it in the config.yaml file but nothing. I opened the port with command -p xxxx:xxxx but nothing. Can someone explain to me how to do it please. Thanks in advance
March 21, 20251 yr You all should add "--restart unless-stopped" to the dockers Extra Parameters because the container updates and after that stops itself from time to time.
June 7, 20251 yr Literally just trying this for the first time. Followed the instructions to a 't' and I keep getting the following error;"sed: -e expression #1, char 313: unknown option to `s'"Any thoughts? My command line comes out as;docker run -d --name='storagenode-v3' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Precision" -e HOST_CONTAINERNAME="storagenode-v3" -e 'WALLET'='<redacted>' -e 'EMAIL'='<redacted>' -e 'ADDRESS'='<redacted>:28969' -e 'STORAGE'='16TB' -e 'BANDWIDTH'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:14002]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/dalekseevs/Unraid-Docker-Templates/master/logos/storj-logo-png-transparent.png' -p '28967:28967/udp' -p '28967:28967/tcp' -p '14002:14002/tcp' --mount type=bind,source="/mnt/user/storj/storj/identity/storagenode/",destination=/app/identity --mount type=bind,source="/mnt/user/storj/storage/",destination=/app/config 'storjlabs/storagenode'All the locations exist and are set up correctly. I have my identity files. config.yaml is created as are folders but ends with the same error.
August 19, 2025Aug 19 I have no idea what I'm doing. I have tried to get this up and for a couple of days now. If someone can tell me what I should do next that would be amazing!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.