TheRefugee

I'm not certain of the correct terminology for containers/docker/images. Do I have my ports set up properly so each container is operating independently? I have multiple containers because I was told that rutorrent can only handle 3,500-6000 torrents before the webgui stops working properly. I don't have nearly that many now but I separated TV, Movies and books into their own container because it is not out of the question that I would start to push the upper limits of what rutorrent can handle.

Is this expected behavior? I have several instances of this docker and when I update one, this immediately shows on the others. When I update the remaining instances, nothing gets pulled and they update without issue. Curious as to what is going on. Otherwise, the docker works great and all work wonderfully.

You're a saint. Problem fixed.

Getting this error after update when trying to add/remove labels. I have 3 instances of this container running but this is a new behavior.

From https://wiki.archlinux.org/index.php/RTorrent How do I go about starting a screen for rtorrent inside docker? /etc/systemd/system/rtorrent.service [Unit] Description=rTorrent After=network.target [Service] Type=forking KillMode=none User=rtorrent ExecStartPre=/usr/bin/bash -c "if test -e %h/.rtorrent_session/rtorrent.lock && test -z `pidof rtorrent`; then rm -f %h/.rtorrent_session/rtorrent.lock; fi" ExecStart=/usr/bin/screen -dmfa -S rtorrent /usr/bin/rtorrent ExecStop=/usr/bin/bash -c "test `pidof rtorrent` && killall -w -s 2 /usr/bin/rtorrent" WorkingDirectory=%h Restart=on-failure [Install] WantedBy=multi-user.target ------------------------------------------------------------------------------------------------------------------------------------------------- /etc/systemd/user/rtorrent.service [Unit] Description=rTorrent After=network.target [Service] Type=forking KillMode=none ExecStart=/usr/bin/screen -dmfa -S rtorrent /usr/bin/rtorrent ExecStop=/usr/bin/killall -w -s 2 /usr/bin/rtorrent WorkingDirectory=%h [Install] WantedBy=default.target

Thanks for taking the time to respond. To be clear, my entire array wasn't effected, only my Movie share. The torrent didn't have a path, I didn't select "don't add torrents name to path", it just so happened to contain a single file. Fortunately my TV and Music shares are separated into their own shares so those remain intact. In the future, I am absolutely going to disable the delete all option; for my own utilization, I can't imagine a practical use case where the delete all accomplishes anything that the regular Delete Data option wouldn't. As per your suggestions: 1. I plan to keep torrents seeding long term so my cache really only pulls duty for appdata. 2. Disabled 3. Looking at my plexpy data, 1710 movies got wiped (ouch) but I have ~980 of them backed up on a remote server; I have started the 3.5 mb/s slog to recover those and the others will be recovered over time. I resorted to taking screen shots of my plexpy library data so I can have a list of files; don't want to miss any on my rebuild. I think I will end up biting the bullet and building a local back up because rebuilding from a remote server is a bit ridiculous at my download speeds lol. 4. I use CA backup but I'm not sure what good it would do me for recovering my plex metadata since I will slowly rebuild my library with new additions sprinkled in. So any time I refresh my plex library, they will get cleaned out; I think it will be the least hassle to rebuild bit by bit.

I think this is what I did My share, "mnt/user/Movies/" contained a file that was not in its own folder, "/mnt/user/Movies/movie.title.2016.mkv" as opposed to "/mnt/user/Movies/movie.title.2016/movie.title.2016.mkv" When I selected delete data (all) with the impression that it would delete all data associated with that single torrent file, rutorrent instead deleted the entire directory. Any confirmation of my missteps would be greatly beneficial to my understanding of what went wrong.

After hash checking a torrent file returned 0%, I deleted the file showing "Zero Bytes" on my mac finder/smb and then selected Delete Data (All) option in the rtorrent webGUI and every single file in the share was deleted.

Changed version from 'latest' to 'plexpass' and received error codes and now plex is frozen. I can not stop or restart plex from docker. __code__:699: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead. Got SIGTERM, quitting. Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.xxx.x.xx. Leaving mDNS multicast group on interface docker0.IPv4 with address 172.xx.x.x. Leaving mDNS multicast group on interface br0.IPv4 with address 192.xxx.x.xx. avahi-daemon 0.6.32-rc exiting. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. That is the latest text from my plex log file. The log file does not update after trying to stop or restart plex. kill/stop/restart does nothing in terminal. Had the same problem yesterday and I resorted to rm the entire directory and did a fresh plex install. To say that I am a novice in the command line in an understatement, I get anxiety just looking at the terminal icon. I know I am not providing enough information to help diagnose why plex is frozen but was hoping that I can get a push in the right direction. I read through another thread about the webUI hanging but couldn't decipher what was causing the issue for others.