TheRefugee
-
Posts
24 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by TheRefugee
-
-
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.
-
Just now, binhex said:
try resetting your plugins:-
1. stop container
2. delete /config/rutorrent/plugins folder
3. restart container
You're a saint. Problem fixed.
-
Quote
2017-06-28 14:29:50,638 DEBG 'rutorrent-script' stderr output:
2017/06/28 14:29:50 [error] 734#734: *53 FastCGI sent in stderr: "PHP message: PHP Notice: Undefined offset: 3 in /usr/share/webapps/rutorrent/plugins/extratio/rules.php on line 197" while reading response header from upstream, client: 192.168.1.5, server: localhost, request: "POST /plugins/extratio/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.7:9082", referrer: "http://192.168.1.7:9082/"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
-
15 hours ago, binhex said:
OK firstly i feel for you loosing that quantity of movies, i really do, its one of my worst nightmares (i saw your other post), i hope you get it back.
Good find on that link to github issue, yes i think the reason you have fallen foul of this is two fold:-
1. You deleted the file using your mac and then also did a deletion of the torrent and data through the rutorrent web ui, obviously because you have already deleted the file manually it couldn't find anything that matches, and possibly then went on to do a recursive delete of everything (its a theory of mine nothing more)
2. you should never use the "Remove and.../Delete data (all)" option, instead you should be using the "Remove and.../Delete Data", hands up i have been using the (all) option myself, i guess i have been lucky that every torrent i download has a path and thus its limited to download only that selected folder recursively NOT the root folder, plus i dont point rutorrent at my array so the damage would be limited (see suggestion 1.)
3. Possibly the torrent you downloaded did not have a folder structure to it and this the zero byte file was in the root of the downloads folder, thus when the plugin kicks in and deletes it also deletes all folders (because of the use of the (all) option).
4. Never enable the option '"Don't add torrent's name to path", by doing this you are saying store the downloaded file in the root of the completed folder, if you then select the "Remove and.../Delete data (all)" option then it will recursively delete all files folder from the location of the downloaded file, i.e. the root of the completed folder (dont know if you had this option enabled or not?).
There are also a couple of things you may want to consider in the future:-
Suggestion 1. Dont allow rutorrent direct access to your array, instead seed stuff on your cache drive, this means if things did go wrong (and coding mistakes can happen) then the damage is only limited to whats on the cache, it won't wipe out your entire collection, this is what i do.
Suggestion 2. Disable that option to prevent this happening in the future, as per the github issue you linked to.
Suggestion 3. Backups, this is completely up to you, and hands up i don't backup everything either (too costly), but you have to ask yourself, if you lost share X is the time/stress of getting everything back greater than the financial cost of backing it up on a separate system? if it is greater then it should be backed up. I dont want to bang on about this as this is probably the last thing you want to hear, but hey its gotta be mentioned right.
Suggestion 4. Make sure the CA backup plugin is enabled and working, this will at the very least then backup your configuration of each docker container, including important stuff like Plex metadata.
OK last edit to this - i think in short people need to be aware that when they see the option "Remove and.../Delete data (all)" what that REALLY means is "Remove the torrent AND delete all data recursively from the current location of the download", if the location of the download happens to be the root of the completed folder then this will delete everything in the completed folder, i think i may add this as a FAQ.
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.
-
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.
[Support] binhex - rTorrentVPN
in Docker Containers
Posted
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.