L0rdRaiden

I have seen that the old Storj image is no longer being updated and not part of the apps. How do I migrate my 5 containers to the new image? Thanks

Storj1 above 150 usually, now is 265 Storj2-5 between -20 and 20 All in the same unraid same conditions. I changed pfsense for sophosXG and it was normal (maybe a coincidence) so I think it might be related with pfsense, but I have reinstalled pfsense from scrach and I still have the same issue. On the other hand are no noticing that during the last week or so the nodes have been more quiet? less allocs

I have 5 nodes, all of them "identical" but one of them the first one "Storj1" have a high delta, all the others runs ok. Any idea why? fw/nat rules are the same for all the nodes, using pfsense here.

Sonnar have been adding epsiodes to ruTorrent (those are added in stop mode but I can live with this) when the download finished sonnar says "eppisode missing from disk" but the files are there. This was working in the past with other series, so now I don't understand why it doesn't work. 18-4-29 15:24:54.2|Info|SceneMappingService|Updating Scene mappings 18-4-29 15:24:55.3|Info|RefreshSeriesService|Updating Info for XXXXX 18-4-29 15:24:55.3|Info|RefreshEpisodeService|Starting episode info refresh for: [296762][XXXXX] 18-4-29 15:24:55.3|Info|RefreshEpisodeService|Finished episode refresh for series: [296762][XXXXX]. 18-4-29 15:24:55.3|Info|DiskScanService|Scanning disk for XXXXX 18-4-29 15:24:55.3|Info|DiskScanService|Completed scanning disk for XXXXX 18-4-29 15:24:55.5|Info|MetadataService|Series folder does not exist, skipping metadata creation XXXXX= hide on purpose

Updates from Storj, I don't know exactly what they mean and how will affect to the multinode setup. https://blog.storj.io/post/172871463238/updates-to-farmer-payouts-and-network-testing

Does the container path has to be in "/dev/urandom" or it can be in my usual Docker folder?

Well I have pfsense, so I call it firewall. Regarding the ports I have read the documentation and in principle if you are not using tunels just opening 4000 4004 4008 4012 and 4016 is enough.

I did the setup with the bridges and I could replicate your result, thanks. On the firewall do you open ports 4000, 4004, 4008, or the whole range from 4000 to 4011? Let see how it goes.

I am talking about this picture where all use 4000

What response time are you getting? I have between 6 and 10 secs

In my json files for the storj containers I have 4004 for Storj2 and 4008 for Storj3. If you look at the storjshare status they are using those ports not 4000

Ok thanks, So in the firewall are you doing port forwarding of 4000 only for the first container or for the range 4000-4003? On the other hand I still don't get why unraid\docker reports the same ports for all the containers despite these are different as you can see when I post the storjshare status

I use br0 usually in all my Dockers because it allows to assign different IP. What is the conceptual difference between br0 and bridge? Which one should I use for docker? I thought that br0 was already a bridge

@MrChunky I have already running several Storj containers the problem is that despite having them in diferent ports and working unraid tell me that they are using the same ports. THe json files have differnet ports 4000 4004 and 4008 and the firewall has open this ports and reporting the traffic correctly Still in advance mode I don't see the container port field root@MediaCenter:~# docker exec Storj3 storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ dcea81e7741aeb8db49174ac5821d9035b00e532 │ running │ 2m 25s │ 0 │ 129 │ 0 │ 18ms │ 4008 │ ... │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (...%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7749bf1 │ running │ 2h 6m 4… │ 1 │ 120 │ 3 │ ... │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj storjshare status ^[[A^[[A^[[A ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7749bf1 │ running │ 2h 6m 4… │ 1 │ 121 │ 3 │ ... │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj2 storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4dd54ed8e3b68fe752618e17055e4eec52114b4c │ running │ 15m 21s │ 0 │ 156 │ 1 │ 4ms │ 4004 │ ... │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (...%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘

@MrChunky Clould you post an screenshot of your port mapping column in the docker tab? In the port configuration in unraid I only have Host port not Container port...

With br0 you have to port forward to the ip you assign to the comtainer

I have installed win10 and win server with the virtIO drivers. I have check with HWindo64 and CPUZ and desplite the power plan being on balance the freq of the CPU is always as maximun Is there a way to configure KVM so the CPU freq scales with demand as It happens when you install the SO in baremetal? I have a Ryzen 2400G

For me it works If I have one in host and another in custom br0, the problem with br0 is that I have problems with port forwarding Unraid is reporting the port 4000 despite in the json file I have 4004 192.168.1.214:4000/tcp192.168.1.214:4000 192.168.1.214:4001/tcp192.168.1.214:4001 192.168.1.214:4002/tcp192.168.1.214:4002 192.168.1.214:4003/tcp192.168.1.214:4003 and now it works, don't ask me why root@MediaCenter:~# docker exec Storj2 storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4dd54ed8e3b68fe752618e17055e4eec52114b4c │ running │ 3m 54s │ 0 │ 101 │ 0 │ 50ms │ 4004 │ ... │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (...%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7749bf1 │ running │ 3h 16m … │ 0 │ 105 │ 3 │ 0ms │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ THe only problem is that needs around 120MB or RAM and when is actually doing something I have read that it can take up to 1 GB

I did the same.... What command do you use to see the status of the second node?

I did this but I get this error, Storj is my original container Storj2 is the new one. Am I using the command right? root@MediaCenter:~# docker exec Storj storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7749bf1 │ running │ 15m 32s │ 0 │ 107 │ 0 │ 32ms │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj2 storjshare status Error response from daemon: Container 8c732a9d378bab85f3b062afb47c63713e0248a2bcd6cbc8752ea5b634e1fdcf is restarting, wait until the container is running root@MediaCenter:~# docker exec Storj2 storjshare status Error response from daemon: Container 8c732a9d378bab85f3b062afb47c63713e0248a2bcd6cbc8752ea5b634e1fdcf is restarting, wait until the container is running root@MediaCenter:~# docker exec Storj2 storjshare status Error response from daemon: Container 8c732a9d378bab85f3b062afb47c63713e0248a2bcd6cbc8752ea5b634e1fdcf is restarting, wait until the container is running I edited the Json file but it looks like is not even reading it, share and log folder and empty despite having Storj2 container running. What network type do you use?

I hope you can get this work for dummies, like everything configurable from the docker template. I have tried to troubleshoot the folder error but nothing works. Just running 1 node.

It work, somehow I was able to enter to a kind of BIOS related to PXE not Seabios and I could change the boot order, so now 1 of the nics doesn't try to boot but the other still try to do it. I have tried to press different buttons at different times to see If I can get into a different BIOS but no luck. Does SEABIOS has a bios interface?

If I run the comand below in the screenshot I get the output above the command Every time I run the command it writes a new Json file but I don't know where it is stored Every time I run the command to create a new node I get this error The path are fine, is case sensitive, I don't now what could be failing, I have found this https://github.com/Storj/storjshare-daemon/issues/122 but I don't know how to use it to fix this issue Any idea?

Regarding the system stats app is there any way to keep log of the statistics even when you are not viewing them? I mean every time I enter in the Stats tabs everything is reset, and all the graphs start to write at the time and open the tab, previous data doesn't exist, doesn't matter if I change the periods available when you select Real time -> 2h, 1h, 30 min etc.

In the docker containers, this 2 graphs produces a perfect match (talking about the netdata screeshot), which makes sense, but in the VM I get what you can see in the picture bellow and it doesn't match with what unraid is reporting (unraid reported and average of 15-20% as much load during the period 10:50 and 10:55, and the CPU report included in the application (SophosXG) running in the VM was reporting almost a iddle load... Why is this? I don't know what to trust. I have all the cores assigned to SophosXG and looking at the netdata graphs everything else was mostly idle. In te doc