NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Automatic 0.6.2 on Duo Issues
I've been trying to get automatic running on my Duo for the last few days with little to no success. I'm not much for unix so that doesn't help matters but i'll walk you thru where i've gotten to.
i have the automatic bin installed and am currently starting the daemon manually so i can pass it custom paths to where my config file is (why on earth it's it /etc/ and not in c/addons-config/ i'll never know) and where to output a log file. for example:
based on another thread for automatic (x86 version) here on this board i've configured my automatic.conf file as such (i've removed all the commenting to keep this code box small and readable:
as you can see i've changed some things etc, hopefully they're correct. i wish the automatic.conf-sample had actual examples in it!!!
anyway, the log i'm generating is throwing this at me at level 1:
any ideas? i've tried various setups using external instead of 1.3 to just try to save .torrent files to my sources directory and let transmission do the watching and starting itself but those attempts haven't born any fruit either.
thanks,
hellbent
i have the automatic bin installed and am currently starting the daemon manually so i can pass it custom paths to where my config file is (why on earth it's it /etc/ and not in c/addons-config/ i'll never know) and where to output a log file. for example:
automatic -v 5 -l /c/addons-config/automatic/auto.log -c /c/addons-config/automatic/automatic.conf
based on another thread for automatic (x86 version) here on this board i've configured my automatic.conf file as such (i've removed all the commenting to keep this code box small and readable:
transmission-version = "1.3"
rpc-host = "localhost"
rpc-port = 8181 (i assume this port is the same as the transmission web-access port? its the same port i use for transmission-remote-dotNet)
rpc-auth = "MYUSER:MYPASS"
feed = { url => "http://ezrss.it/feed" }
interval = 30
# upload-limit = 10 (unchanged)
# use-transmission = yes (disabled for testing)
# start-torrents = yes (disabled for testing)
torrent-folder = "/c/media/BitTorrent/sources/"
statefile = "/c/addons-config/automatic/automatic.state"
filter = { pattern => ".*" folder => "" }
as you can see i've changed some things etc, hopefully they're correct. i wish the automatic.conf-sample had actual examples in it!!!
anyway, the log i'm generating is throwing this at me at level 1:
../src/web.c, 523: Upload to 'http://localhost:8181/transmission/rpc' failed: number of redirects hit maximum amount
any ideas? i've tried various setups using external instead of 1.3 to just try to save .torrent files to my sources directory and let transmission do the watching and starting itself but those attempts haven't born any fruit either.
thanks,
hellbent
54 Replies
Replies have been turned off for this discussion
- Hmm. Must be some other error because I tested the script before I posted it but since it works I guess there's not much need for further debugging ;)
-Stefan - When using automatic to download the torrent files, they're saved with strange names such as FGR4RF~2 etc
Using the dir command within the directory the files are saved in returns a list of real torrent names, for example torrent.one.name.torrent and not the strange names listed above.
However, both transmission and the rename script in this thread see the files as the strange names, so I can't rename them to .torrent files or get them to auto-load.
Anyone have any idea why this is occuring?
Thanks! Kevin_R wrote: When using automatic to download the torrent files, they're saved with strange names such as FGR4RF~2 etc
Using the dir command within the directory the files are saved in returns a list of real torrent names, for example torrent.one.name.torrent and not the strange names listed above.
However, both transmission and the rename script in this thread see the files as the strange names, so I can't rename them to .torrent files or get them to auto-load.
Anyone have any idea why this is occuring?
Thanks!
Did you try adding the quotes in the script? That worked for me, and I get the same strange filenames.
Here is the code I used:#!/bin/bash
cd /c/media/BitTorrent/Sources
for file in *; do ext=${file: -7}; if [ ! "$ext" = "torrent" ]; then mv "${file}" "${file}.torrent"; fi; done
cd -- I still have the same issues, even after adding quotes.
I can create a file manually, using a similar name and the script will rename it without any issues, it's only files created by automatic that it can't rename!
Nevermind, it seems the quotes did it. Even though the file names look the same as they did originally, Transmission recognises them as torrents and auto-loads them! :)
Finally, where is the best place to use this script? Should I just set it up as a cron, or place it into the automatic start.sh script?
Cheers! - As it happens, I've also bumped into this redirection message. I did pull a source copy of automatic, but haven't had to time yet to trace down the actual culprit here. I suspect it's the RPC step to transmission since I can successfully get automatic to write torrent files to a watch dir. Problem is that the latest transmission add-on versions seem to not support the watch-dir function, despite having entries in the default config file (sigh).
So, either way I am still hunting a working solution. - If you're looking at the code using a recent Linux distribution it's unlikely you'll find a problem. Many of the problems with automatic on the Sparc line of ReadyNAS systems relate to old versions of Curl, PCRE and other libs used on the ReadyNAS. One of the things is that cURL on the Sparc ReadyNAS will return the actual redirect http status code (30x) whereas newer versions of cURL return 200. Automatic in it's original version will check for a 200 status and thus will never ever work on Sparc ReadyNAS systems without being patched ;)
-Stefan - This sadly doesn't come as a surprise. There's an Ultra in my future somewhere soon, so I'll not fret too much about libraries. For now I think I'm taking the watch-dir approach and see about getting that going.
btaroli wrote: This sadly doesn't come as a surprise. There's an Ultra in my future somewhere soon, so I'll not fret too much about libraries.
Well, to be honest, the situation isn't much better there. I couldn't get the RPC stuff going there as well, but you're welcome to give it a spin. As for the patches I've been talking about: Just change every occurrence of "responseCode == 200" to "responseCode < 400" and you're good to go. That's what I did for the add-on. Ah, and don't forget to change the version numbers of the required libs in configure.in.
-Stefan- Ok, so I finally figured out how to make a filter to get 720p but at the same time dismiss if for example BluRay or DVDRip or any other word is present. Here is what it looks like.
filter = { pattern => "^(?=.*?\b720p\b)((?!Complete|BluRay|DVDRip).)*$"
folder => ""
}
Hope it helps anyone! - Is there a guide for setting parameters for automatic?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
