MrChunky

Members
  • Posts

    97
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by MrChunky

  1. It means that your node cannot reach the satellite for some reason. I would recommend to have a look at the threads on storj.io or make a new thread on the forums there. People there have much more experience debugging storj related errors, as networking is most likely not an unraid issue.
  2. Suggest there is an issue with the storage path. Have a look at your config and setup instructions.
  3. Thanks for sharing, I'll add it to the description.
  4. Nothing immediate comes to mind. Can you post log output when you run it the first time with setup option. Did you generate your certificates correctly?
  5. Hard to say just from the information you have given. May be the TCP port is already in use, may be the mount path are not working properly.
  6. Yes, mover doesn't move locked files. Files that are currently in use by a process are locked, this is true for any process on the unraid system as far as I know. In theory this means that if storj starts using files differently it can breaker mover functionality. Seems to be working fine at the moment... But I think in the long run it is quite risky to have mover running on the storj folders. One thing that could be done is to use mover for the data chunks but not for the folders where the databases are... Just speculating though.
  7. Everyone has a different setup... This is an Unraid issue not a docker/ storj issue I would say.
  8. @KrisMin Thank you for pointing this out. I tested it and it seems that indeed something has changed in unraid docker implementation since I last created a node. This argument is now necessary on the first run. I added this info to the template and the topic.
  9. I really do appreciate the passion to get an optimal setup. However, this discussion should really be had on storj forums directly. The people there will be much more knowledgeable about these topics and you can probably find the answers you are seeking already there.
  10. The docker will Update automatically assuming you have this function turned on on unraid for all your docker containers. This usually achieved through auto update plugin:
  11. 1. Not sure what you mean exactly by pressure on the disks. If you are talking about reducing the read/write cycles, then enabling cache is probably a good idea. It works fine for me and the amount of cache disk used is pretty stable with mover running daily. 2. The nodes you created will be vetted first, afterwards the traffic should increase significantly. You can read more here. In general you should check out the storj forum directly for such questions, there is a lot of information there.
  12. I am not sure what you mean by this. You should not move the identity to the same folder as the data folder. And especially you should not use drives when operating on the unraid system, but rather user shares.
  13. Do not nest the identity and storage folders. e.g. the path should be /mnt/user/storj/storjidentity for the identity and /mnt/user/storj/storage for the storage folder. Here storj is a new share you should create. Make sure the port forwarding is done properly, as it looks like your issue is a network issue from the error that you showed.
  14. I agree that nesting storage and identity folders this way is probably resulting in this error.
  15. Its the right one, but it definitely doesn't have those fields as seen in the XML config, must be something on your side.
  16. These two variables are not a part of the template I am maintaining. Here is the template XML from which it is generated. there are no -v fields.
  17. No Problem. I don't think the -v flags are there normally, at least when I pull the template they are not there. Will do. Already in the description.
  18. The docker run format that you are using here is different then the xml format Unraid docker templates are using. You should remove the backslashes in the template.
  19. Not sure which template you are referring to here. /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='storagenode-v3' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'WALLET'='0xxxx' -e 'EMAIL'='xxx@gmail.com' -e 'ADDRESS'='www.xxx.com:28969' -e 'STORAGE'='8TB' -e 'BANDWIDTH'='10000TB' -p '28969:28967/tcp' -p '14003:14002/tcp' --mount type=bind,source="/mnt/user/appdata/storj_cert/identity/storagenode/",destination=/app/identity --mount type=bind,source="/mnt/user/storj/",destination=/app/config 'storjlabs/storagenode:beta' In your case you have trailing backslashes: " \ " after the mount commands that I don't think should be there. When you paste the mount commands into the extra parameters, they should look like this: --mount type=bind,source="/mnt/user/appdata/storj_cert/identity/storagenode/",destination=/app/identity --mount type=bind,source="/mnt/user/storj/",destination=/app/config The docker tag is latest, mine is beta. In addition, make sure the mount command for the identity folder should point directly to the folder with the certificates, and not a level above.
  20. Sure, here you go. In the top right you need to toggle the Advanced View to see the extra parameters.
  21. Sorry for the late reply. You needed to add the storage via the --mount flag in the extra parameters field as described in the documentation and docker description. That's why you were getting the error.
  22. Got This MCE memory error recently: Sep 15 13:18:16 Tower kernel: mce: [Hardware Error]: Machine check events logged Sep 15 13:18:16 Tower kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Sep 15 13:18:16 Tower kernel: EDAC sbridge MC1: CPU 0: Machine Check Event: 0 Bank 10: 8c000049000800c1 Sep 15 13:18:16 Tower kernel: EDAC sbridge MC1: TSC 3946d4b5f1f49c Sep 15 13:18:16 Tower kernel: EDAC sbridge MC1: ADDR a46740000 Sep 15 13:18:16 Tower kernel: EDAC sbridge MC1: MISC 90008000800128c Sep 15 13:18:16 Tower kernel: EDAC sbridge MC1: PROCESSOR 0:306f2 TIME 1600168696 SOCKET 0 APIC 0 Sep 15 13:18:16 Tower kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0xa46740 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c1 socket:0 ha:0 channel_mask:1 rank:0) I was wondering if there is any way to figure out which memory stick is throwing the errors? And how serious this is? Thanks in advance. tower-diagnostics-20200916-1612.zip