Spies

I was already transcoding to RAM when the data was temporarily moved (its back on the cache drive now and still works fine).

My Plex appdata is temporarily on an unassigned disk and it's working just fine.

Was support for UD ever added? I was intending on using Unbalance to move everything to a new cache drive.

My Mojave VM is crashing after the Apple logo, it worked fine last time I used it, have there been any update in 6.6.6 that could have caused it?

Thanks. Is there any way to configure rtorrent to bypass the privoxy for specific trackers?

Transdroid has stopped working since the last update, any idea what setting I need to change?

Ok great, thanks.

After rebooting my server, I had to change the mapping back to the /mnt/user/transcode share and then back to /tmp/transcode in order to get anything to play. Any particular reasoning for this?

I feel like the watchdog script is too aggressive as deeming rtorrent down and restarting the docker. Can I change the timeout somewhere?

I can never get past 200 before everything stops but I feel like it's an issue with my hardware, I just haven't identified what yet.

Is there any way to exclude a tracker from going through the privoxy?

Installed this under 6.6.6, press start but nothing appears?

Can anyone help me understand what is going on here, I want to mount some shares via NFS (only) on my synology, the problem is once unraid mounts the share, all the permissions on the synology are reset, this doesn't happen with SMB shares. For example, I have a Plex share which I only want to be rw by the dockers, and ro by SMB, but even if I remove all the file level permissions and only leave the administrators group with full access, after I press mount in unassigned devices, it removes the administrators group and re-adds nobody, everyone and users will permissions. What is going on?

What performance improvement are we talking?

He has an issue, it should show the following lines in the log: 2019-02-05 15:56:23,635 DEBG 'watchdog-script' stdout output: [info] rTorrent process started [info] Waiting for rTorrent process to start listening on port 5000... 2019-02-05 15:56:23,643 DEBG 'watchdog-script' stdout output: [info] rTorrent process listening 2019-02-05 15:56:23,650 DEBG 'watchdog-script' stdout output: [info] Autodl-irssi not enabled, skipping startup 2019-02-05 15:56:23,650 DEBG 'watchdog-script' stdout output: [info] Initialising ruTorrent plugins (checking rTorrent is running)...

Is your downloads path set correctly?

Run into the same issue again, rtorrent is still running but I'm getting no throughput at all and it fails to resolve any of the trackers. Yet privoxy via the browser is still working. Caught the crash whilst trying to stop a large number of torrents: 1548423482 C Caught internal_error: 'TrackerController cannot set timeout when inactive.'. ---DUMP--- /usr/lib/libtorrent.so.20(_ZN7torrent14internal_error10initializeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x24f) [0x153c1bc5051f] /usr/bin/rtorrent(_ZN7torrent14internal_errorC1EPKc+0x8f) [0x55d9fe6147ff] /usr/lib/libtorrent.so.20(_ZN7torrent17TrackerController14update_timeoutEj+0x345) [0x153c1bc6ebe5] /usr/bin/rtorrent(+0x10031a) [0x55d9fe69031a] /usr/bin/rtorrent(+0x1076df) [0x55d9fe6976df] /usr/lib/libtorrent.so.20(+0xc9d81) [0x153c1bcdbd81] /usr/lib/libtorrent.so.20(+0x3a9de) [0x153c1bc4c9de] /usr/lib/libtorrent.so.20(_ZN7torrent11thread_base10event_loopEPS0_+0x164) [0x153c1bca3424] /usr/bin/rtorrent(+0x36a15) [0x55d9fe5c6a15] /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x153c1b87c223] /usr/bin/rtorrent(+0x372fe) [0x55d9fe5c72fe] ---END--- Seems to change slightly in subsequent crashes. ---DUMP--- /usr/lib/libtorrent.so.20(_ZN7torrent14internal_error10initializeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x24f) [0x14c0586fc51f] /usr/bin/rtorrent(_ZN7torrent14internal_errorC1EPKc+0x8f) [0x560102ca47ff] /usr/lib/libtorrent.so.20(_ZN7torrent17TrackerController14update_timeoutEj+0x345) [0x14c05871abe5] /usr/lib/libtorrent.so.20(_ZN7torrent17TrackerController10do_timeoutEv+0x236) [0x14c05871b326] /usr/lib/libtorrent.so.20(_ZN7torrent17TrackerController15receive_failureEPNS_7TrackerERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x29) [0x14c05871b539] /usr/lib/libtorrent.so.20(_ZN7torrent11TrackerList14receive_failedEPNS_7TrackerERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0xe0) [0x14c05871c250] /usr/lib/libtorrent.so.20(+0xfed98) [0x14c0587bcd98] /usr/lib/libtorrent.so.20(+0x3b6ef) [0x14c0586f96ef] /usr/lib/libtorrent.so.20(+0x3be09) [0x14c0586f9e09] /usr/lib/libtorrent.so.20(+0xfcc96) [0x14c0587bac96] /usr/lib/libtorrent.so.20(+0xfdc5b) [0x14c0587bbc5b] /usr/lib/libtorrent.so.20(_ZN7torrent11TrackerList10send_stateEPNS_7TrackerEi+0x50) [0x14c05871bcb0] /usr/lib/libtorrent.so.20(_ZN7torrent17TrackerController10do_timeoutEv+0x213) [0x14c05871b303] /usr/lib/libtorrent.so.20(_ZN7torrent17TrackerController15receive_failureEPNS_7TrackerERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x29) [0x14c05871b539] /usr/lib/libtorrent.so.20(_ZN7torrent11TrackerList14receive_failedEPNS_7TrackerERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0xe0) [0x14c05871c250] /usr/lib/libtorrent.so.20(+0xfed98) [0x14c0587bcd98] /usr/lib/libtorrent.so.20(+0x3b6ef) [0x14c0586f96ef] /usr/lib/libtorrent.so.20(+0x3be09) [0x14c0586f9e09] /usr/lib/libtorrent.so.20(+0xfcc96) [0x14c0587bac96] /usr/lib/libtorrent.so.20(+0xfdc5b) [0x14c0587bbc5b] ---END---

I've added an 2TB drive dedicated to torrents using unassigned devices, will see how it goes!

HDD appears but I get a username and password box, it won't accept the root username and password and denies access.

I may be missing the point here, but is there any way to create a \\tower\disk share for the unassigned device that I can access via SMB?

I was watching the tmux whilst starting loads of torrents via rutorrent webui and it died back to bash with the message [exited]. It could well be an issue with network i/o, I need to figure out something so I can make the torrent storage local, maybe another server dedicated as a seedbox. Do you have a watchdog script that deems the process hung if it doesn't respond within a certain time limit?

Both incomplete and completed, and yes they are being seeded from there. I don't have enough space on the local server to be able to download and seed. The LAN is gigabit and when rtorrent is stalled, there isn't any excessive network activity. I'm trying to screen into the rtorrent process in the dockers cli, but as screen isn't installed, I don't know how to do that. I have set logging up to ./tmp/rtorrent.log so I can tail that but it hasn't helped so far.

Downloads are stored on a separate NAS. Appdata is on a single spinner cache drive, the FS of which is xfs. I'm back in the same situation with 177 torrents this time, rutorrent is telling me nothing is running and eventually all the trackers time out, if I then start stopping torrents via the web interface then 'rtorrent main' disappears in TOP and restarts. Is there a syslog that can show me why it's closing?

Still got issues, as soon as I get anywhere near 200 torrents, even if they're inactive, it takes a massive nosedive, speeds have dropped right off and everything has stalled out. Here is the top command from inside the docker: %Cpu(s): 2.9 us, 2.4 sy, 0.0 ni, 94.2 id, 0.3 wa, 0.0 hi, 0.1 si, 0.0 st MiB Mem : 32174.8 total, 341.4 free, 17434.0 used, 14399.4 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 13382.7 avail Mem Unknown command - try 'h' for help PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 967 nobody 20 0 6899984 185408 23292 S 1.0 0.6 31:41.85 rtorrent main 1 root 20 0 2300 60 0 S 0.0 0.0 0:01.57 tini 9 root 20 0 85976 14048 852 S 0.0 0.0 0:15.24 supervisord 151 root 20 0 9316 1952 1352 S 0.0 0.0 0:01.50 start.sh 152 nobody 20 0 9184 508 4 S 0.0 0.0 0:00.03 rutorrent.sh 155 nobody 20 0 9312 2472 1928 S 0.0 0.0 0:11.42 watchdog.sh 156 nobody 20 0 9184 480 4 S 0.0 0.0 0:00.03 privoxy.sh 488 root 20 0 25816 2796 1420 S 0.0 0.0 114:19.02 openvpn 884 nobody 20 0 3558100 7872 2528 S 0.0 0.0 1:11.25 privoxy 966 nobody 20 0 12380 2016 1112 S 0.0 0.0 0:04.97 tmux: server 1006 nobody 20 0 99116 6004 148 S 0.0 0.0 0:01.98 php-fpm 1008 nobody 20 0 99992 12352 6232 S 0.0 0.0 0:04.97 php-fpm 1009 nobody 20 0 16244 1268 32 S 0.0 0.0 0:00.02 nginx 1012 nobody 20 0 17100 3736 1736 S 0.0 0.0 0:04.22 nginx 1013 nobody 20 0 16696 3196 1528 S 0.0 0.0 0:00.02 nginx 1014 nobody 20 0 16696 3560 1892 S 0.0 0.0 0:00.00 nginx 1015 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1016 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1017 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1018 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1019 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1020 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1021 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1022 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1023 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1024 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1025 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1026 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1027 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1028 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1029 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1030 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx 1031 nobody 20 0 16696 1600 0 S 0.0 0.0 0:00.00 nginx

217 torrents and everything is queued/not seeding again. Can I get any meaningful logs to get to the bottom of this? Edit: it's the web server which is failing as rtorrent is still running, what web server is it running under and what resources are allocated to it? Edit edit: increased the rpc timeout under rutorrent/config/config.php to 60s from 5s default. I don't think 5s is enough to pull the data for 200 torrents from rtorrent.