GoChris

Members
  • Posts

    232
  • Joined

  • Last visited

Everything posted by GoChris

  1. You do not have to set any shares to use the cache drive if you don't want to. Other than perhaps your VM share/folder as it would seem.
  2. Did you update to the latest version? It's not compatible without a fresh start. Happened to me as well. So I went back to version 12 of the docker and will remain there until I find other alternatives. Didn't think I updated it. Says version 1.3.13. Rebooted the server and it still won't let me in. How do you roll it back to another version? Add ":12" to the end of the repository.
  3. Did you update to the latest version? It's not compatible without a fresh start. Happened to me as well. So I went back to version 12 of the docker and will remain there until I find other alternatives.
  4. It's not a big deal really. I'm not fussed.
  5. How do I turn off the random apps of the day? I don't see a setting for it.
  6. For those confused, like I was, about this and the Shout irc docker. https://github.com/thelounge/lounge/wiki/Differences-between-The-Lounge-and-Shout
  7. Just updated to the latest version, I was previous up to date before this update from the past day. Seems to be working fine however I see this in the log now. Not sure how important it is. :0: UserWarning: You do not have a working installation of the service_identity module: 'No module named service_identity'. Please install it from <https://pypi.python.org/pypi/service_identity> and make sure all of its dependencies are satisfied. Without the service_identity module and a recent enough pyOpenSSL to support it, Twisted can perform only rudimentary TLS client hostname verification. Many valid certificate/hostname mappings may be rejected. Thanks
  8. I've obviously not made myselft clear. I tried a new appdata, I set the option to no, and then after adding a torrent, checking it to 100%, I restarted the container. On startup, the torrent was set to stop, and starting it forced a recheck. Is that the intended behavior with hack check = no?
  9. I've already stated two times I started with a new appdata. The same situation still presents itself.
  10. That's good to know. I have that option set to off like I said so...makes no sense why it should recheck on start. It never did that before, and does it on a new install as well. So if there are no issues, and it's not working as designed, what is the next step?
  11. no it doesn't... it has the hash set to check in the rtorrent.rc file. turn it off if it's a pain. This one? check_hash = no I believe that option is only to do a recheck on completion of a download. Either way, the setting is off according to my rtorrent.rc file.
  12. Renamed my appdata folder so I could start from scratch for testing. Added one torrent, checked it to 100% and started seeding it. Then I restarted the docker. Upon restart it was stopped, hit start and it rechecked it again. So that would imply that my old appdata folder doesn't necessarily have anything wrong with it. Also on a clean appdata start, changing settings are still not sticking. Such as changing the default directory for downloads, it always reverts back. Clearly this new image has issues.
  13. Didn't seem to make a difference. It's still rechecking a bunch of torrents I should add: These are torrents that existed before this docker was changed to a version that used a slightly different appdata structure. I copied the rtorrent_sess folder from my backup (that I did right before upgrading to 6.2-RC4 and thus updated the docker also). Edit 2: Some of the torrents that need rechecking existed before the upgrade, and some were added after.
  14. Good info, so in theory if I run docker stop -t 120 <containerid> for rutorrent when I know I need to shut it down for whatever reason, that might be more graceful. Trying it now as I need to add another drive to my array.
  15. Well I never had this issue before this update. I could start and stop it and it would never have to recheck the torrents. Any ideas for a fix? I can't really have it recheck 1TB+ of torrents each time it restarts.
  16. So I upgraded, copied over my session folder and despite having to check a handful of torrents, all seemed to be good. However my settings don't seem to be saving, and I restarted it and it had to check a (large) handful or torrents again. So, again, it seems something is not saving with some files, like the state of a bunch of torrents. Are there some permissions that need to be fixed? Here is my run command: docker run -d --name="rutorrent" --net="bridge" -e TZ="America/Denver" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8085:80/tcp -p 51413:51413/tcp -p 6881:6881/udp -v "/mnt/user/downloads/":"/downloads":rw -v "/mnt/user/":"/unraid":rw -v "/mnt/cache/appdata/rutorrent":"/config":rw linuxserver/rutorrent
  17. Is there anyway to restore just a single appdata folder from the backup? I don't want to restore them all. Can I just move all the other folders out of the backup folder and leave just the one I want and then restore?
  18. Thanks for the scripts. FYI there is no option to disable the mover, at least not on 6.1. Is there on 6.2?
  19. It was a bug fix until we realized the 'fix' was going to be more involved (because of 'mover' complication). That is why to enable the hard-link functionality you have to go manually edit a config file. We could have just not documented it, but thought, well it's in the code, so let's let some advanced users play around with it. Fair enough, I think with this RC I'll finally move up to 6.2, things are looking very nice and I've had my 2nd parity drive ready and waiting in the box for a few months now. Good work!
  20. I thought there was a feature freeze? And why bother adding a new feature only to remove it right away? Doesn't seem right for a RC.
  21. From a few posts back in this thread http://lime-technology.com/forum/index.php?topic=47299.msg475461#msg475461
  22. I had this problem. Here is my config, I remember manually editing the config.php in appdata, but I don't think that is required. Change your default folder to use /unraid/downloads (for eg) instead of /downloads. So now /unraid for me is the root of everything and I have no issues.
  23. I would tend to agree with that rational. Anyway, I was able to fix the issue. Through some painful trial and error and stumbled upon an rtorrent.lock file in /mnt/user/appdata/rutorrent/rtorrent/rtorrent_sess After removing this file --> works like a charm Thanks for the help CHBMB! Can confirm that anytime you edit the config to an existing rutorrent, that it won't restart properly without removing this lock file. Would be nice if this can be automated. Cheers
  24. FYI I migrated from sparklyballs' ZNC docker to this one by using the existing appdata folder and there have been no issues. Sure was nice not having to set it up again.
  25. I'm sure this has been answered, but it's not the first post and I don't have time to read 30 more pages. When it tells me there are 3 files with hash key corruption, where does it list the files? Seems a bit odd that I only started using this a few days ago, and now there are corrupted files. But I want to investigate.