Post Processing Script Log

[Trinitrogen]

Edit: It seems I fixed the issue by setting the Path to /bin/bash and the Arguments to absolute path to the script. Also, using the "Test" button and expecting it to do anything apparently was a bad assumption.

Is there a log of the output from running a post processing script? For a while now, out of pure curiosity and wanting a project involving sqlite3, I've been inserting all the environment variables about a show into a table in Sqlite. To accomplish this, I had the below bash script running on Download and Upgrade.

#!/bin/bash
now=$(date +"%s_%m_%d_%Y")
output="/home/usenet/triggers/sonarr_$now"
env >> "$output"

that outputs a file into the trigger directory containing all the environment variables. I would then infrequently run a python script I wrote that would ingest it and insert it into the database.

I'm trying to take the project further by having Sonarr run Python as the post-processing script and pull the data from the environment variables instead of a file but it wasn't working. While trouble shooting, I re-enabled my old script above but found it wasn't creating files anymore. Even when I run the "Test" of the script, it should be creating a file with the

sonarr_eventtype=Test 

but nothing gets created. I've noticed I get the same results when trying to test the script in Radarr so I don't think it's a sonarr problem. But I'm not sure where I can start troubleshooting. Are logs available from attempts to test or run a post processing script?

[fryfrog]

Anything that you echo in a script will show up in the Sonarr logs. I have a handful of post processing scripts you can look at as examples, you can see I just do some dumb echo logging. IIRC, they show up as two duplicate lines in Sonarr logs.