What exactly does the test button do on a custom script? It was coming back as success even though Sonarr couldn’t run the script (through normal events) with an “Object reference not set to an instance of an object.” in the trace logs. The error has mysteriously gone away on it’s own since I left it last night but I was just curious why it said success during the test?
From what I understand it just tests the existence of the file, it doesn’t check execution bit.
Actually my original issue is back again after I restarted Sonarr. There is no information in the trace logs other than “Unable to send OnGrab notification to: Pushbullet (custom): Object reference not set to an instance of an object”
Path: /usr/bin/python
Arguments: /volume1/scripts/pushbullet_cs.py
Sonarr Version: 2.0.0.4146
Mono Version: 4.2.2 (Stable 4.2.2.30/996df3c Thu Mar 17 10:54:57 CET 2016)
Running on Synology NAS using the SynoCommunity Python 2.7.
The script was running previous to the restart of Sonarr so I haven’t changed anything in the configuration. Any ideas?
No idea, looks like error from mono. I use BASH and I just place the path no arguments, shebang is suppose to take care from there. Don’t know if you can do that with python.
You’ll have to wait for one of the developers take a look at trace logs
Post them to hastebin and we can take a look.
I can’t seem to reproduce this now. I’ve restarted Sonarr several times and it seems to work fine. I wonder if it has something to do with my Python install(s) on my Synology. I somehow ended up with multiple versions of Python 2.7 installed at different locations.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.