L0rdRaiden

Members
  • Content count

    175
  • Joined

  • Last visited

Community Reputation

7 Neutral

About L0rdRaiden

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. What do you mean by automated repo? what it does differently? How is SIA working for those playing with it? I'm not running it since you have to pay 50$ or so to become a miner but I'm thinking again about it. BTW SIA requires a good graphic card but storj does not, right?, maybe this is why SIA isn't working properly for some while using it in docker.
  2. L0rdRaiden

    [Support] Linuxserver.io - Rutorrent

    Every time I download something new I dont have permisions to modify it with samba (windows explorer), then I run un unraid tools->new permisions and it works How can I fix this permanently? the share is shared as public.
  3. do you lose lots of peers on Storj when the server is up many hours/days? I start the nodes with around 150 peers, after a day or so I have 30-50 less and the number is smaller every day, so I usually restart the docker. Do you experience the same problem? is normal?
  4. I get this ouput root@MediaCenter:~# docker exec StorjMonitor storjshare stop 8fx70bbceb6xefd9d1325x6b5eeeaf44c0fxxxxx missing node id, try --help root@MediaCenter:~# docker exec StorjMonitor storjshare start 8fx70bbceb6xefd9d1325x6b5eeeaf44c0fxxxxx no config file was given, try --help What am I missing? After a few days some nodes lose almost all peers so this is why I want to restart them. Is this normal?
  5. L0rdRaiden

    [Support] Linuxserver.io - Sonarr

    In case someone has the same problem an run Tool->New permisions and now it works
  6. What network type are you using with StorjMonitor container?
  7. I am using storjmonitor container now I have the main node plus 4 more but the container is only mapping 4 ports 172.17.0.2:4000/TCP172.17.0.2:4000 172.17.0.2:4001/TCP172.17.0.2:4001 172.17.0.2:4002/TCP172.17.0.2:4002 172.17.0.2:4003/TCP172.17.0.2:4003 I have fix it adding the port mapping manually. But I think the problem is that it only map the ports the first time you create the container if you change the number after that the port mapping doesn't update Now is working but for some reason, I don't know why, my first node has always a high delta ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7xxxxxx │ running │ 7m 51s │ 0 │ 138 │ 0 │ 103ms │ 4000 │ 11.99GB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (12%) │ │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4dd54ed8e3b68fe752618e17055e4eec52xxxxxx │ running │ 7m 49s │ 0 │ 139 │ 0 │ 7ms │ 4001 │ 9.92GB │ connected │ │ → /storj/Node_1/share │ │ │ │ │ 0 received │ │ (TCP) │ (10%) │ │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ dcea81e7741aeb8db49174ac5821d9035xxxxxxx │ running │ 7m 47s │ 0 │ 93 │ 0 │ 7ms │ 4002 │ 12.02GB │ connected │ │ → /storj/Node_2/share │ │ │ │ │ 0 received │ │ (TCP) │ (12%) │ │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4428e5e0f2e84b4e9e9e86df57f381dcdxxxxxxx │ running │ 7m 46s │ 0 │ 120 │ 0 │ 2ms │ 4003 │ 8.56GB │ connected │ │ → /storj/Node_3/share │ │ │ │ │ 0 received │ │ (TCP) │ (9%) │ │ ├─────────────────────────────────────────────┼─────────┼─────���────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ c3c26bcc0e3af7d2d8add82d602a1xxxxxxxxxxx │ running │ 7m 44s │ 0 │ 104 │ 0 │ 8ms │ 4004 │ 1.15GB │ connected │ │ → /storj/Node_4/share │ │ │ │ │ 0 received │ │ (TCP) │ (1%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ BTW how can I restart a node without restarting all of them?
  8. Thanks @Jcloud, does SIA supports multi nodes? How do I add storage folders in the share? Could you explaint please a little bit more the setup until the end? I have followed you steps but right now I don't know if it's working or not. BTW it says that I need 2000 SC (52$) to start to host... I guess I need to put some money in, or is there a way to avoid this? BTW all of you please register in filecoin early miner program https://filecoin.io/ https://docs.google.com/forms/d/e/1FAIpQLSfdFpWhJj8OIGA2iXrT3bnLgVK9bgR_1iLMPdAcXLxr_1d-pw/viewform?c=0&w=1
  9. L0rdRaiden

    [Support] Linuxserver.io - Rutorrent

    I have change the default port of rutorrent, in the docker template, software and rtorrent.rc file After many days and restarts I get in my fw (pfsense) many blocks to the port 51413 which was the previous default, it like every minute a get few of those. Does it make sense? why are there IP trying to contact to the old port? is the setting still maybe embeded somewhere in docker? ruttorents reports my current port as open and is working fine bur having so many ip's calling to the old/default rtorrent port smells bad. May 6 00:31:36 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:51043 xx.xxx.xxx.146:51413 TCP:S May 6 00:31:36 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:27913 xx.xxx.xxx.146:51413 UDP May 6 00:31:39 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:51043 xx.xxx.xxx.146:51413 TCP:S May 6 00:31:39 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:27913 xx.xxx.xxx.146:51413 UDP May 6 00:26:04 WAN Default deny rule IPv4 (1000000103) 68.63.214.93:36440 xx.xxx.xxx.146:51413 TCP:S May 6 00:26:05 WAN Default deny rule IPv4 (1000000103) 68.63.214.93:36440 xx.xxx.xxx.146:51413 TCP:S May 6 00:26:07 WAN Default deny rule IPv4 (1000000103) 68.63.214.93:36440 xx.xxx.xxx.146:51413 TCP:S
  10. I'm using this template, I guess is still valid right? https://hub.docker.com/r/oreandawe/storjshare-cli/
  11. 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
  12. 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
  13. L0rdRaiden

    Samba doesn't work

    That happend whem I was tryng to move files from one place to another to see If I could copy files to a folder. I enable the share after that, so is not connected. Maybe my issue if one of those weird things that are fixed after reboot the client and or the server, I will try.
  14. 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.
  15. L0rdRaiden

    Samba doesn't work

    attached I installed local master to see if the situation improves, thanks. mediacenter-diagnostics-20180429-1756.zip

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.