Custom scripts not executing on Synology

[zorch]

Environment Notes:

• Synology DS414 w/ DSM 5.2-5644 Update 1
• Sonarr Ver. 2.0.0.3645 – grabbed v20150731-8 from the SynoCommunity package index, used Sonarr’s self-updater to update to 2.0.0.3645.

---

I tried to set up the Slack notification script, detailed here. After specifying the path to the script, clicking “Test” in the Custom Script edit modal yields “Test Successful”. Strangely though, Sonarr doesn’t seem to be doing anything. Nothing shows up in the logs, but according to CustomScriptService.cs, it should be writing a debug message: "Executing external script: slack.sh". I let Sonarr download a file to see if the Test button was broken, but again no dice.

I ssh’d into my Synology box and switched to the nzbdrone user with su nzbdrone. As the nzbdrone user, I was able to execute the script just fine, which should hopefully rule out any permissions issues.

Next, to see if Sonarr was doing anything at all, I made a test script called foo.sh. It does the following:

touch /sonarr-scripts/bar

I pointed Sonarr at it, clicked “Test”, and no bar file appeared. Like before, directly executing the command through the CLI as the nzbdrone user works just fine.

---

So that’s where I’m at – I’m kind of at a loss right now. If you guys have any ideas, I would love to hear them.

[dagoob]

The test button for external scripts just checks that the script exists, it doesn’t execute it, so I’d continue by using your foo.sh with a download (an ‘on grab’ or even just an ‘on rename’ should be enough), but it sounds like you’re going to have the same issue since you tried that step with the main script.

[subzero79]

One of the bugs is sonarr just shows the folder. You have to type the name of the script in the path field.
If you have debug enables you should see detailed action of the script if it has echo output or in case sonarr complains about not finding the script or other error.

Also I think you’re quite behind in version. Back at the time I recall an error because the vars where passed with dots instead of underscores, and that’s not allowed in shell or bash.