jumperalex
-
Posts
2000 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jumperalex
-
-
uggg while waiting I tried adding an rss feed and it will not load. "Error loading RSS feed" it is a feed I've used before and the url loads in my browser just fine.
First google link is: http://forums.rutorrent.org/index.php?topic=65.0
if that helpsmake sure plugins/rss/cache is read/write to the webuserAnother similar issue http://forums.rutorrent.org/index.php?PHPSESSID=462ee4f8afb81093d2c735f62a52fe61&topic=288.msg1729#msg1729
-
oooooohhhhhhh
of course. Thank you! -
Ok so if I understand you, and please bare with me,
php.ini is in "/etc/php7/" and right now is set to register_argc_argv = Off
So as for you asking me to confirm that register_argc_argv = On enables autotools, all I can say is that is what I'm seeing on the intertubes but I can't confirm. Is there a comment I can execute to make the change on my system to test?
I'm also seeing some notes that this fails using unix sockets. I assume that is as opposed to the option to use an scgi port?
I'm getting some of this also from here http://forums.rutorrent.org/index.php?topic=57.0
Mind you I've also tried setting a watch folder in rtorrent.rc and that isn't working either. when trying one or the other I've made sure to disable one as well so they don't compete; then restart the docker. no luck with either and I don't care which I get working. my rtorrent.rc config line is
schedule = watch_directory_1,5,5,"load.start=~/downloads/watch/*.torrent"
take the tilde "~" out and it's watched
schedule = watch_directory_1,5,5,"load.start=/downloads/watched/*.torrent"
I suppose I understand the tilde, but why "watched"? I specifically created a folder called watch.
that said, removed the ~ but left it at "watch" and
HOT DAMN it worked. [sigh] ... now I need to get it to remove the torrent file, but that is my problem to deal with 
Have you made the permission change? Should I kill and download the docker image / container? The autowatch tools are indeed easier to deal with from the GUI of course
-
I'm down with fixing the easy stuff first
Also kinda makes the whole docker useless without it I await patiently. As always, thanks. And because I want to learn, at any time feel free to tell me to do more research with a bit of a hint where to start. Pieces are falling into place with this most recent comment, the php stuff, and my now trolling through your docker git
-
So I tried to manually add the torrent in question and this popped in the error log
2016/08/07 12:56:50 [crit] 235#0: *1 open() "/var/lib/nginx/tmp/client_body/0000000001" failed (13: Permission denied), client: 10.0.0.6, server: _, request: "POST /php/addtorrent.php?torrents_start_stopped=1& HTTP/1.1", host: "10.0.0.4:8081", referrer: "http://10.0.0.4:8081/" 2016/08/07 12:57:10 [crit] 235#0: *55 open() "/var/lib/nginx/tmp/client_body/0000000002" failed (13: Permission denied), client: 10.0.0.6, server: _, request: "POST /php/addtorrent.php?torrents_start_stopped=1& HTTP/1.1", host: "10.0.0.4:8081", referrer: "http://10.0.0.4:8081/"
I've always been able to manually add torrents, so um ... now what? What other log should I send?
-
Ok so if I understand you, and please bare with me,
php.ini is in "/etc/php7/" and right now is set to register_argc_argv = Off
So as for you asking me to confirm that register_argc_argv = On enables autotools, all I can say is that is what I'm seeing on the intertubes but I can't confirm. Is there a comment I can execute to make the change on my system to test?
I'm also seeing some notes that this fails using unix sockets. I assume that is as opposed to the option to use an scgi port?
I'm getting some of this also from here http://forums.rutorrent.org/index.php?topic=57.0
Mind you I've also tried setting a watch folder in rtorrent.rc and that isn't working either. when trying one or the other I've made sure to disable one as well so they don't compete; then restart the docker. no luck with either and I don't care which I get working. my rtorrent.rc config line is
schedule = watch_directory_1,5,5,"load.start=~/downloads/watch/*.torrent"
-
Quick question because I don't know how to check it myself, can you please confirm that within the docker container this is the correct path to PHP
/usr/bin/php7
I ask because autotool for autowatch is not working and what I'm reading says the first thing to check is the path to php in the config.php file. The above is what I found.
EDIT: also can you confirm, or not, if
sorry if that is opaque, I'm trying to track down the issue with autowatch. that is another one of the "things to check" from here http://forums.rutorrent.org/index.php?PHPSESSID=557b64757da258035d65eb80f2a4ad26&topic=645.msg4895#msg4895"register_argc_argv" enabled for the php-cli.ini -
So two things:
1) now that I've updated, sure enough making changes to things like my connection port in the webgui do not stick on docker restart. So behaving as described
2) I copied over my entire session folder from my old appdata structure into the new appdate structure and all of my old torrents came over, connected to my private tracker, and started seeding as hoped for. So nuking the docker and appdata from orbit is not as much of a complete startover as I had worried.
Thanks guys!!!
-
So I submitted this as a candidate for Fix Common Problems but I really think this is ultimately the job of the base UI.
Maybe I'm obtuse, stupid, or both but I just spent forever tracking down why my bridged containers that I just regenerated (due to linuxserver.io container reworks) would not start. Turns out, it was because they were defaulting to ports 80 or 8080 which are already owned.
Sure you say, any experienced docker user should know that is something you need to change,
BUT ... guess where that is mentioned BOLDLY in the docker config page? No where that I could find and aren't you afterall trying to make this as easy for the newbie user as possible?
Sure you say, but unRaid's help dialogue says the following
When the network type is set to Bridge, you will be given the option of customizing what ports the container will use. While applications may be configured to talk to a specific port by default, we can remap those to different ports on our host with Docker. This means that while three different apps may all want to use port 8000, we can map each app to a unique port on the host (e.g., 8000, 8001, and 8002). When the network type is set to Host, the container will be allowed to use any available port on your system. Additional port mappings can be created, similar to Volumes, although this is not typically necessary when working with templates as port mappings should already be specified.BUT ...you know what it doesn't say, it doesn't say that the docker will not even start or that you need to specifically ensure there are no conflicts. It says you CAN change the mapping, it doesn't say you MUST change the mapping.
Sure you say, but the docker logs will tell you
Cannot start container HandBrake: Bind for 0.0.0.0:8080 failed: port is already allocatedBUT ... that is the docker log, not the system log. The only way to get to the docker log via the GUI is to generate a diagnostics log which contains the docker log and then read it. Sure you can drop to the command line but really, is that the correct solution given your push to help the newbie and keep us out of the CLI for anything but the most advanced tweaking?
So, I humbly suggest that unRaid GUI checks for port mapping conflicts. I think Limetech needs to do a better job of making all this very clear right in the UI, maybe even checking when the container is created and pop-up an error. If not that, then you need to do a better job of communicating the docker start-failure in the logs to make it easier for the user to identify the failure issue. Like, maybe provide webgui access to the docker log or better yet, interleave it into the system log with a toggle to show/hide like you have to errors, warning, text, etc.
As it is, there is literally no useful error given in the current log display. But as soon as I viewed the docker logs it was immediately apparent and my problem was solved. A newbie might not still have made the connection mind you, hence why I suggest you consider dealing with this in the Docker template config page when the docker is being created/edited and saved.
Thank you for your consideration
-
I have another candidate for FC: docker webui port mapping conflicts. Maybe I'm obtuse, stupid, or both but I just spent forever tracking down why my bridged containers that I just regenerated (due to linuxserver.io container reworks) would not start. Turns out, it was because they were defaulting to ports 80 or 8080 which are already owned.
Sure you say, any experienced docker user should know that is something you need to change,
BUT ... guess where that is mentioned BOLDLY in the docker config page? No where that I could find
Sure you say, but unRaid's help dialogue says the following
When the network type is set to Bridge, you will be given the option of customizing what ports the container will use. While applications may be configured to talk to a specific port by default, we can remap those to different ports on our host with Docker. This means that while three different apps may all want to use port 8000, we can map each app to a unique port on the host (e.g., 8000, 8001, and 8002). When the network type is set to Host, the container will be allowed to use any available port on your system. Additional port mappings can be created, similar to Volumes, although this is not typically necessary when working with templates as port mappings should already be specified.BUT ...you know what it doesn't say, it doesn't say that the docker will not even open or that you need to specifically ensure there are no conflicts. It says you CAN change the mapping, it doesn't say you MUST change the mapping.
Sure you say, but the docker logs will tell you
Cannot start container HandBrake: Bind for 0.0.0.0:8080 failed: port is already allocatedBUT ... that is the docker log, not the system log. The only way to get to the docker log via the GUI is to generate a diagnostics log which contains the docker log and then read it. Sure you can drop to the command line but really, is that the correct solution?
So, I humbly suggest that FC checks for port mapping conflicts. I mean yes I think Limetech needs to do a better job of making all this very clear right in the UI, maybe even doing their own checking when the container is created and pop-up an error. If not that, then they need to do a better job of communicating the error in the logs somewhere to make it easier for the user to identify the failure issue. Like, maybe provide webgui access to the docker log.
BUT I also know that the first thing I did was fire up FC to see if it would help me find the problem. It has become my go to maintenance and troubleshooter and I think this is a feature that can save people a lot of headache if they aren't paying attention to this "common problem" when installing a new / refreshed docker ;-)
Thank you for your consideration
-
is there anyway to add an additional path. I understand the download path but heres my dilemma. i want to be able to have download be a share on unraid which is on the cache and then move to a seperate share called complete so that way it goes onto the array. The cache mover cant move completed torrents while the docker is running. i tried adding -v /complete but that didnt seem to work.
Just add an extra path in the docker webui on Unraid. Edit the container config and do it there.
unfortunately even when i do add the path when trying to edit autotools to use this folder its stuck in the download folder?
any changes made in the webui are not permanent and only apply to that session, ie until the docker is restarted.
this is a limitation of the apps themselves
https://github.com/Novik/ruTorrent/wiki#some-non-obvious-points
any permanent changes need to be made to the rtorrrent.rc file
/config/rtorrent/rtorrent.rc
Weird because my changes three main settings i can think of seem to stick. I restarted my docker about an hour again and these settings were retained:
feed interval
watch folder
unpack
Or are those ruTorrent config settings and not rTorrent??
-
But be aware that performance of the app as a whole (and transcoding in particular) is going to go downhill with appdata sitting on the array. If you really make extensive use of Plex, your best solution is to either turn off thumbnail generation (which will save huge amounts of storage space, but you'll probably have to start the db over again from scratch to get rid of the existing thumbnails) or a larger cache drive.
It should be easy to map the plex library on the array but transcoding to cache.
-
Yeah honestly at the least what is needed is a way to retain the users and their client certificated between updates. Needing to regenerate and reissue all user certificates, to all clients can be a real limitation for some people. Fortunately not me really since I have on user and two devices. But if I had a lot more I would certainly have to consider skipping some update points just to lighten the maintenance load and that isn't the best solution for security
-
gotcha on the rollout strategy thanks.
Crash and burn ... uggg. At least for openVPN I only had a single certificate and two clients to reissue. I'm sure for more prolific users that would be a real PITA. I'll have to be strategic reseeding because doing them all will be serious hassle
Well thanks for all the work though, it is appreciated.
-
I don't ruTorrent listed in OP and the page https://hub.docker.com/r/linuxserver/rutorrent/ seems like it isn't using the new image. Is support being dropped?
-
Most people have access to a real OS as well as linux.
Yeah right, I keep my OS/2 handy
BASIC SUPPORT OR DIE!!!!!
-
Fair enough on Time.
As for the What though ... I'd say you might not have to pay too much attention to documenting how to passthru since that is pretty well covered elsewhere. That is, unless you have to do something specific to your hardware?
Which is the bit I think could be helpful to others, what you had to do specific to your hardware to get iomuu turned on and recognized my unRaid. Once that is done the process is mostly hardware agnostic.
Just my final two cents ;-)
-
so something you might consider doing is post a new thread with all your findings and doings, with all the key search terms someone might use, a good descriptive subject, and maybe even a few screen shots based on your board.
Save the next poor soul 3/4 of a day
-
the benefit to the AMD hardware, at least when I boult the rig in my sig, was that it was cheaper to get VM and ECC memory capable hardware because with Intel you have to go server parts but with AMS you can go ASUS consumer. That might have changed and there is still the choice of what performance level to shoot for and the cost to get it. Its just that cheap iommu and ECC support is (was) not easy.
-
only if you limit its resources. my plex docker can do two BD rip to ROKU transcodes at the same time. See sig for specs.
-
The thumbs nails are used for any GUI that allows you scan fwd/rwd so it can present those thumbnails as a visual queue. I say "any" when in fact that is probably only ROKU but I can't be sure. What I can be sure about is that without them using my ROKU would be painful, so thumbnails are a must for me and are auto generated. If I run out of space I'll just buy more space. I also don't tend to horde media after I've watched it, but some movies are kept for future rewatch unlike tv shows (well The Wire and Firefly will never leave my server until the day I die!)
-
Price drops would indeed be nice
I will say that regardless of the price, I couldn't be happier with the 8TB Reds ... these are REALLY nice drives that perform exceptionally well and run very cool.
good to hear. I had planned on a pair of 4TB (parity + data) but now Im' tempted to step that up to the 8's especially after a little time for the 10's to put pressure no prices
-
-
Plex is crashing in the container. God knows why. Not something we've seen before. Might be worth grabbing the dump and asking over in the Plex forums
any chance you recent;y changed your container mapping from a user share to a disk share? That will break things and require you to recreate the container. Your appdata will be safe though. I had to do that exact same thing.
of course. Thank you!
HOT DAMN 
[DEPRECATED] Linuxserver.io - Rutorrent
in Docker Containers
Posted
But but but ... it really is lovely. Does what I need and plays well with my trackers. Neither Transmission nor Deluge have I ever been able to get setup right.
Maybe your permission change will help [shrug], but to be clear you're telling me you were able to click on the feed icon, enter in a feed url in the form of
and it worked? Because I get exactly
re: your image ... uggg ... I don't have even an idea where to start with my config that might make me so special. maybe I'll try another completely pristine docker, no session shenanigans, and see what happens