https://community.splunk.com/t5/Alerting/unable-to-run-python-scripted-alert/m-p/191674#M12414 <P>this is already the case</P> Fri, 22 Aug 2014 13:35:45 GMT sbsbb 2014-08-22T13:35:45Z https://community.splunk.com/t5/Alerting/unable-to-run-python-scripted-alert/m-p/191672#M12412 <P>I've made a scripted alert in python, and put it in py app directory<BR /> .../splunk/etc/apps/myapp/bin/scripts/scripted_alert.py</P> <P>in .../splunk/var/log/splunk/python.log I see that it has been triggered with the correct path, and parameters :<BR /> 2014-08-22 14:37:01,178 INFO ['.../splunk/etc/apps/myapp/bin/scripts/scripted_alert.py', '1', '| stats c | eval ...</P> <P>When I try to execute it with<BR /> <CODE>.../splunk/bin/splunk cmd python .../splunk/etc/apps/myapp/bin/scripts/scripted_alert.py'</CODE> with all the parameters from the python.log, it is working...</P> <P>It seems that splunk is not taking the python interpreter ?<BR /> But in my file header I have</P> <PRE><CODE>#!.../splunk/bin/python # -*- coding: utf-8 -*- </CODE></PRE> <P>(... is a substitution / I'm using Splunk 5.0.5)</P> Fri, 22 Aug 2014 12:50:21 GMT https://community.splunk.com/t5/Alerting/unable-to-run-python-scripted-alert/m-p/191672#M12412 sbsbb 2014-08-22T12:50:21Z https://community.splunk.com/t5/Alerting/unable-to-run-python-scripted-alert/m-p/191673#M12413 <P>Most likely your hash bang is off. I believe in this case the full path should work better. if that is a typical Splunk unix install try:</P> <BLOCKQUOTE> <P>#!/opt/splunk/bin/python</P> </BLOCKQUOTE> Fri, 22 Aug 2014 12:57:47 GMT https://community.splunk.com/t5/Alerting/unable-to-run-python-scripted-alert/m-p/191673#M12413 starcher 2014-08-22T12:57:47Z https://community.splunk.com/t5/Alerting/unable-to-run-python-scripted-alert/m-p/191674#M12414 <P>this is already the case</P> Fri, 22 Aug 2014 13:35:45 GMT https://community.splunk.com/t5/Alerting/unable-to-run-python-scripted-alert/m-p/191674#M12414 sbsbb 2014-08-22T13:35:45Z