[OSX] Deluge AMC issues

[kmarriner]

I am determined to get this to work!

I am running OSX and the newest version of Deluge.

I have deluge setup to call three scripts currently:

The first is this:

Code: Select all

#!/bin/bash
torrentid=$1
torrentname=$2
torrentpath=$3
echo "Torrent Details: " $torrentname $torrentpath $torrentid  >> ~/Desktop/FBTest/execute_script.log

This is to test to make sure the execute plugin is actually working. It outputs EVERY SINGLE TIME, without fail it works.

The next script is the AMC script which looks like this:

Code: Select all

#!/bin/bash
torrentid=$1
torrentname=$2
torrentpath=$3

filebot -script fn:amc --output /Users/kmarriner/Desktop/FBTest/Media --log-file amc.log --action duplicate --conflict override -non-strict --def music=n artwork=n "ut_dir=torrentpath/torrentname" "ut_kind=multi" "ut_title= torrentname"

This never runs, period. The log never gets generated or anything. However! If I run it manually replacing torrentpath/torrentname and torrentname with the actual file name and location, it works perfectly. That is what perplexed me to no end.


After beating my head against the keyboard for about 4 hours trying to get it to work, I added a third script:

Code: Select all

filebot -version > /Users/kmarriner/Desktop/FBTest/version.log 2>&1

Does not do anything. Not a thing.

if I run it manually, I get this:

Code: Select all

FileBot 4.6 (r3052) / Java(TM) SE Runtime Environment 1.8.0_60

So from this, I have concluded that for some reason its not triggering filebot when called inside of a script. Any ideas?

[rednoah]

Yep, looks like filebot is never even called. But now that you have even called a simple filebot -version command and redirect error output, I'm perplexed as well. There's no way that it produces no output whatsoever...

I assume you installed filebot via brew cask? Just in case it's a strange PATH issue, try calling filebot with the absolute path /usr/local/bin/filebot to the executable:

Code: Select all

/usr/local/bin/filebot -version > /path/to/version.log 2>&1

Deluge might be running as a different user. Make sure that the Deluge user has write permissions to your /path/to/version.log file.